I have been trying to set up my cookies privacy policy on my own , looking into the forum’s old topics and I can’t manage to find the answer.
When I get a new visitor on my webapp, this user is obviously logged out.
My cookies pop up appears giving the option of Accepting or Declining.
Supposingly, bubble stores this information (workflow Make a change to current user ==> field cookies with binary yes/ no ) wether the user is logged in or out.
But whenever this unlogged user browses into another page, this pop up comes back again and again.
Any ideas on how to approach this, so my app recognizes whenever an unlogged user as visited a page in the last 7 days?
I’m probably missing a thing here. I would appreciate any advice or past experience in setting this up so I can be GDPR cumpliant in the EU.
Add and additional field (e.g., I use “Cookie Decision Made” = yes/no) to the current user to let the system know whether they declined or accepted the cookies. To show/hide the popup you will have now to validate that field instead of the user … is using cookies operator.
This is just the way I do it, but there’s probably a better solution
Instead of making cookies field consent yes no, I suggest making it text field and set to null, accepted, rejected. So you know it with single database record.
Well technically this is what I described , I have this field “Cookies accepted” = yes/ no, but the system doesn’t Create a new thing nore Make a change to a thing if the user is logged out right?
Thanks for the is using cookies operator. I just read the Bubble manual to understand this operator, but it retrieves only if user has “Opt in for cookies” or “Opt out from cookies” , how can it retrieve the yes / no field we both created?
Thanks for you reply.
I have the same question that in my previous reply, what condition should I put on the pop up on page load? because Bubble is not able to retrieve the data in the field text (null, accepted, declined ) if the user is logged out.
You can edit current user’s details even if they are logged out.
Current user will exist as long as the user keep the tab open (longer if app sets cookies by default), including the field value. You can read more about temporary users here