@JackVaughan: It would be better, in my opinion, if we had the option of adding markdown to the Agreement Text, so we could show the external links to our privacy policy within our burb, rather than as independent links as in your screenshot above.
I also think the external links should sit below the Agreement Text and checkbox, and not directly below the email field.
The Agreement Text and Checkbox should sit directly under the email field.
That would immediately make this iteration look a lot less clunky.
Hey @JackVaughan
We know the user agreement checkbox is required for European apps, or even US apps with Europeans users. This checkbox is only available as part of the PRO features. That means that, being considered GDPR and its impact, a free Glide apps will not be GDPR compliant as long as it will allow some features collecting personal data (favorites, public with email,…). So the free plan can’t be used by European app makers, or even makers from other countries / continents targeting European users.
So I think @Krivo 's feedback is : can you provide a clear picture of the free et pro plans in terms of GDPR compliance? Exemple :
free plan :
favorites : no GDPR compliant
public with email apps : no GDPR compliant
…
So that European app makers will be able to use Glide to make free or pro apps, but they’ll know what they can, or can’t, do to respect GDPR requirements. Example : do not use the “favorites” feature.
@JackVaughan Christophe summed it up quite clearly. As a app developer targetting european users the developer would like to know which features can be used and which can’t. The list with non-useable features due to GDPR would be fairly long (when being on a free tier plan). And actually as you have enabled “Send feedback” feature (and it cannot be disabled in free tier plan) - the list with non-useable features due to GDPR will be the full feature set. You cannot do a fully GDPR compliant app when the app is actually able to pick up user data - and that is possible with “Send feedback”. Here Glide should as minimum put in a choice whether to show the functionality or not.
@mark As @Christophe_HK also mentioned. IP adress is a personal information and not all apps are really GDPR compliant.
I have put a section of the privacy policy of Pixaloop - a popular app for manipulating images - in:
IP Address. When you access the Services or make purchases through the Services (such as a
subscription to the e-learning courses), we may collect your IP address. This data may convey to
us information about how you use the Services, and allow us to properly bill you and enable
localization features. Some features may not function properly if use or availability of your IP
address is disabled.
The privacy policy that can be found on your site Privacy Policy | Glide also describes that you log IP address and more.
It would be fantastic if you put yourself in the role as an app developer and thought about how the app developer would write a privacy policy. Doing that I expect that you would recognize that you would need information from the software supplier (i.e. Glide) on how Glide is handling personal information. The privacy policy could be used as a template for every app developer. This would be such a huge help - truly.
The app developer would then also add how he process personal data beyond the processing that Glide inherently does. This could include transformation of images stored in Cloudinary, sharing name/e-mail etc with a company that is sponsoring a competition via the app etc.
Apart from it being quite tacky, the main problem in offering GDPR as a Pro ‘feature’ is that you are exposing the fact that the free version is not GDPR compliant.
It won’t be long before the no-code movement comes under legal scrutiny and as a service provider it is Glide’s duty to ensure its users have the basic tools to operate their apps legally.
I suspect you’re already losing users to your free plan because it is not GDPR compliant, so the chances of converting them to Pro users is somewhat diminished.
I understand. In the short term, I will see if we can put something in the docs about this. But we are of course thinking seriously about how we make it easier/clearer for app developers to be compliant. This is a big item on our current 6 month plan, so we are actively working on it.
@JackVaughan please let us know when you have added something to the documentation.
Could you also try to make “Send feedback” an developer changable option. As of right now public (non-pro) apps cannot be made GDPR compliant because the user can input (personal) data via “Send feedback” - so please - add an option to deselect the “Send feedback” functionality .
It is an amazing feature! Anyway I notice there is a bug on it whenever I’m using the black font, the tickbox won’t appear like what happen using the white font.
@JackVaughan to expand further on the points @Krivo makes: Public apps are GDPR non-compliant when a user uses any form on our site.
Whilst they are prompted to sign up when saving to favourites, they are not requested to sign up when they try to fill in any form, not just the send feedback form.
Whatever logic you have instigated to force sign up when saving to favourites should also be applied for any instance a user is asked to submit personal data.
@garrison the problem with “send feedback “ is that you cannot disable it.
With favorites and forms you as a developer can decide not to use favorites and forms.
Jack, can we please get the option to only allow the “sign in with google” option.
It is confusing for my users, because it says please enter your email, and so they do the pin option every time instead of logging in with google. The main users of my app are children at school on shared devices. So it’s simpler and faster to use google sign in rather than switching to email (which they can barely sign into… they’re little lol) and switching back.
I’ve asked about this a few times with no response. Can you please give me some feedback on this request? Thank you so much!!
Of course, it’s a totally valid point. Sorry we haven’t responded.
We get lots of requests and we do our best to implement them. However, I can’t see this in our feature requests app, so I suggest you add it so other users can upvote it. We monitor the popularity of features in there very carefully.
I know it’s not the answer you were looking for but documenting our features/plans in terms of what is or is not GDPR compliant is not something we can do right now as it gets into the realm of giving legal advice. If you or other users are concerned about GDPR then you need to seek legal advice in your local area.
@JackVaughan I think that you should tell that a Glide app is not GDPR compliant if the app includes favorites, user-specific data and form data (where personal data is obtained). You are marketing Glide as a tool to create apps which obtain and store personal data - and that isn’t, in my understanding, possible if you want to comply with GDPR. Such a message should be easy to communicate.
We’re all concerned by GDPR. Today we simply can’t use Glide if we want to keep in sync with law. Some features can’t be disabled by default (favorites,…) and we don’t have the possibility to implement workaround by our own.
For internal or family app, it’s probably not a problem, for other purpose and business apps, it’s a bit more problematic. GDPR is not a problem for European makers and users only, any provider must comply with the requirements, even if from the US.
I really enjoyed using Glide, but now it’s used as a gadget because I don’t plan to create a business with only one client, me and my own data. My regret is that a company who has raised few millions don’t take care à bit more about this GDPR issue and don’t have lawyers to get explained what is GDPR, what to do or what to propose.
A bit more flexibility on the login component (make it a component!) could help, but it’s not for tomorrow and I didn’t succeeded in hacking this part using css or any other method
I hope for all Glide apps makers and template sellers it will be better soon. Else there are other solutions such as Adalo or Appgyver who are very powerful and provide ways to keep as much as possible in sync with GDPR reqs.
