How to handle cookies and member accounts conventionally with Memberstack while respecting user consent?
How to handle cookies and member accounts the conventional way?
Also is there any Memberstack script that should be subject to user consent? and blocked from running if declined in the consent popup?
Comments
2 comments
Hello!
Memberstack comes with all batteries included. You don’t need to worry about setting up cookies or writing code to remember if someone is logged in. Memberstack does all that automatically. By default, it saves login info using something called localStorage, but if you need to (it's not required), you can switch it to use cookies instead.
If you're worried about users accepting your cookie policy, here's a simple solution:
You can add a checkbox when people sign up that says something like:
"By creating an account, I accept the terms and conditions, cookies and privacy policy."
Most websites include information about cookies and data usage in their terms and privacy policies. That way, you're covered.
Some sites also use a cookie banner on the homepage to let visitors know about tracking or marketing cookies. That’s a more general approach. For example https://finsweet.com/cookie-consent or https://www.cookieconsent.com/
But if users are creating accounts, it's a good idea to make sure they clearly accept your terms and privacy policy during signup.
Thankyou Raquel, yes Im currently trying the new Finsweet component app in Webflow. It shows me a bunch of uncatgorised scripts that I have to choose whether they will be essential, personalized, marketing or analytics.
Please sign in to leave a comment.