Hey @josh and all the team, thanks for pushing GDPR so much (make you stand out from other no-code tools)
However, I have a problem with losing the cookie opt-in after logout. I wonder that nobody else had this issue before (or did I overlook a forum post?) as this seams to be the standard GDPR procedure:
Show new clients the GDPR popover with a checkbox to opt-in to cookies. We also have a second checkbox for accepting the terms of our application. I store it under
Current User's accepted_terms=yes. I also have Country and Language selection which I store in the Current Users object.
Now the user explores the application and then signs up. This turns the anonymous user (“Visitor”) into a permanent database entry (“User”) as far as I understood the object/database handling. Everything fine.
Some users log out after visiting (not everyone wants to stay logged in everywhere forever or they switch the user account). When a user logs out, the Current User gets reset to an empty object and not back to the anonymous user object (“Visitor”).
So I lose everything: Cookie opt-in, Terms agreement, Language, Country selection which is very stupid … I understand that you have to clear the object after logout, but all this info (especially country/language, but also cookie opt-in) is Visitor/Client-related and not User-related. The user wants to log-out, but he does not want to start from zero.
If the Current User object is not made for storing session data, where can I save things like Language selection permanently and log-in-independent? Do you see a workaround? Maybe I can disable the Cookie opt-in in the settings and handle it somehow my own to avoid complete deletion? Maybe there is an interface for Cookies or Localstorage?
Thanks for help! Kind regards, Florian