@JackVaughan: Thank you, I appreciate you taking the time to chip in on this and whilst it’s heartening to know that Glide is on the case, I have to make some decisions right now as our plans have come to a bit of a standstill.
It’s now hard to muster up any excitement about the new features you’re shipping regularly.
GDPR is indeed a large topic and aside from the issue of data retention/deletion, the showstopper is actually an easy problem to resolve: a checkbox for users to give their active consent before we can collect any of their data.
As it stands, the only way forward with our plans is to forgo the basic ‘Add to Favourites’ functionality, and remove all forms, and possibly need to disable the feature that allows users to show current location, plus also let go of our Google Analytics integration.
We would also certainly not be able to integrate payments with Stripe.
Of all these though, having to wave goodbye to the Favourites feature would render our app next to useless.
And if that wasn’t bad enough, we’re now looking to move our projects back to WordPress, which is something we were excited about letting go of!
You mention that we ‘can put together an onboarding experience with Glide (using tab visibility, forms etc).’ but it would be really helpful if you could give us some guidance on how to utilise these methods to gather user consent from the start?
I’m less worried about users having issues with privacy and GDPR, than I am about competitors looking to ‘grass us up’ (good ol’ English vernacular). We’d pretty much be a lame duck for such vindictiveness.