Cookies and storage

Cookies are small files a website keeps in your browser; local storage is similar but isn’t sent to any server. Here we explain what Berse stores in your browser and what happens on the sites you publish with Berse. It is part of the privacy policy.

Almost everything we store is strictly necessary for Berse to work or to remember something you chose, and doesn’t need your permission. The only exception is berse_ft: it’s only used if you accept it in the cookie notice, shown on Berse’s public pages (not inside the app while signed in).

sb-*-auth-token (cookie): keeps you signed in. It is httpOnly, so no script on the page can read it. It is removed when you sign out and after 400 days at most.

berse_locale (cookie): remembers the language you chose. One year.

berse_section_bg (cookie): remembers which page of your project you were on (Studio, Pulse, Launch or Integrations) so closing the project settings takes you back to it. 30 days.

berse_consent (cookie): stores your choice in the cookie notice so we don’t ask again. Six months; after that we ask again.

berse_ft (first-party cookie, 90 days): remembers where you came from on your first visit (utm campaign tags, the site that sent you and the page you landed on). If you sign up, we save it to your account to know what brings people to us and to suggest the answer to “how did you find Berse?”. It isn’t shared with anyone.

If you don’t accept it, Berse works exactly the same. If your browser sends the Global Privacy Control signal, we treat it as a refusal.

berse.cortex.model and berse.cortex.agentModel keep the last Cortex model you picked (for editable sites and for sites made by Cortex); berse:first-steps:… keeps each site’s first-steps guide progress and whether you closed it; berse:credits-notice:… keeps the credit notices you already closed this period; berse:code-chat remembers whether you folded Cortex’s chat in Code.

It never leaves your browser and only remembers what you did in the interface, so it is necessary and doesn’t ask for permission. You can clear it in your browser settings.

You can change your choice at any time from “Cookie preferences”, at the bottom of Berse’s public pages and the legal pages. If you withdraw permission, we delete berse_ft from your browser; if you’ve already signed up, you can ask us to delete where you came from from your account. You can also delete or block cookies in your browser, but if you block the necessary ones you won’t be able to sign in.

We don’t use advertising, social media or third-party tracking cookies, or pixels, and we don’t sell data. To detect errors we use Sentry, which doesn’t set cookies in your browser and is configured not to store your IP address.

When you pay for a plan or manage your subscription, you do it on Stripe’s pages. Stripe uses its own cookies there, needed for payment and fraud prevention, under its cookie policy.

While you edit in Studio, images from external libraries (Unsplash, Pexels, Picsum) and maps in your designs load from those services, which receive your IP address like any web request.

On the sites you publish, Pulse, Berse’s measurement, doesn’t use cookies. It only keeps in the visitor’s local storage (berse:pulse) the first and last day of visit, on how many days they came and where the first visit came from, without an identifier and for at most 13 months, to know how many come back; if the browser sends Global Privacy Control, it keeps nothing. If your site sells with a cart, it keeps the cart in the visitor’s local storage (berse:cart) and, during checkout, temporary markers in session storage (berse:checkout and berse:paid); they are needed for the purchase the visitor asks for.

Third-party fonts, maps and images your site uses (Google Fonts, Bunny Fonts, Google Maps, Unsplash, Pexels or Picsum) load from those services, which receive the visitor’s IP address, and Google Maps may set its own cookies. Berse doesn’t add a cookie notice to your sites: as the controller of your site, it’s up to you to inform your visitors and, where your law requires it, ask for their permission.

If you have questions about cookies or local storage, write to us at legal@berse.ai.