Cookie Policy

Creo only stores what it needs to work, like keeping you signed in. We don’t use advertising cookies, and we don’t currently use analytics or tracking tools, so there is nothing optional for you to accept or refuse.

Cookies set when you sign in:

• creo_access_token — proves you’re signed in. Lasts 15 minutes and is renewed while you use Creo. Not readable by page scripts.
• creo_refresh_token — lets us renew your sign-in without asking for a new code. Lasts up to 30 days. Not readable by page scripts, and only sent to our sign-in endpoints.
• creo_session_hint — a simple flag, with no personal information, that tells the page whether to try renewing your sign-in. Lasts up to 30 days.

Other things stored on your device:

• Push notifications: if you turn on browser notifications, we keep a notification token in your browser’s local storage, and Google’s Firebase service may store technical data in your browser so notifications can reach you. Turning notifications off in Creo’s settings removes the token.
• Google sign-in: if you choose “Continue with Google”, Google’s pop-up may set its own cookies on google.com.

When you pay, you’re sent to a page run by our payment partner. That page is theirs, and they may set their own cookies to process and secure the payment. See their policies for details.

You can delete or block cookies in your browser settings, but Creo won’t be able to keep you signed in without them. You can turn push notifications off in Creo’s Notification settings or in your browser’s site settings.

If we add analytics or any other optional cookies in future, we’ll update this page and ask for your choice first. More about what we do with personal information is in our Privacy Policy.

Questions about cookies? Email support@creobase.app.