Hey bubble community.
i have a simple web app where 2 kinds of users can communicate with each other.
How can you set up that when a user don´t want to be part of this app anymore he can close his account and he won´t be able to log in then.
Kind regards
Marc
Best to use some backend workflows for this…
The simple way is to just delete the User once the user decides to close their account. Then they wont be able to log in. Job done.
But, depending on your use case, you may not want to actually delete the user, but rather just ‘de-activate’ them so they can no longer use your app (so you can keep their user data as a record, or reactivate their account at a later date should they wish to do so).
In that case just have a yes/no field on the User datatype to define whether a user is active or not, and use conditionals in your app so only active users can login and access features. (you’ll need to be careful with things like GDPR and data-protection here - i.e. depending on your terms of service and privacy/data protection policies etc. if a user requests to close their account they may expect that their data is also deleted - so make sure you have a clear policy set out to avoid any legal issues).
If the user has created data and/or uploaded files then again you may, or may not, want to remove all connected data and files for the user from your database.
In that case you’ll need to do all of that first, before deleting the user. It will depend how you’ve got your database set up as to exactly how to do it, but you’ll need to run some backend workflows, either recursively, or using the ‘Schedule Backend Workflow on a list of things’ function, to delete all the associated data for the user, before deleting the User data entry itself.
Hey, Thank you very much, that´s exactly what i need to do!!
The question is where do you usually tell the user that you will keep storing their data, that it is GDPR confirm?. Is that even possible that you will continue to collect data from the users?
Kind regards
Marc
Well, I’m not a lawyer or an expert on GDPR or dataprotection, so it’s best to check with a professional in the field…
But make sure you have all that kind of thing laid out clearly in all your legal documentation (privacy polices, dataprotection policies etc), explaining that user data may be kept for a definite, or indefinite, amount of time, even if accounts are closed etc. (generally you shouldn’t keep personal user data longer than you need it - so the specifics will depend on your app and what it’s for).
Also, it’s probably an idea to have a link to those policies as part of the process for closing accounts, perhaps with a checkbox to request their data is removed as part of the account closure process.
As I said, it’s always best to check these things with a legal expert, but generally as long as you have clearly worded policies that comply with regulations, and you give users simple ways to request their stored data is removed you should be fine.
This topic was automatically closed after 70 days. New replies are no longer allowed.
