Cookie Policy
Effective date: 2026-11-20
This Cookie Policy lists the cookies and the browser storage that Bublate uses, and why. Our Privacy Policy says how we handle personal data in general.
1. What cookies are
1.1. Cookies. A cookie is a small text file that a website puts in your browser. The website reads it again on your next request, for example to know that you are signed in.
1.2. Local storage. Local storage is a similar store in your browser. Only the website that wrote the data can read it, and the browser does not send it with each request.
2. What we do not use
2.1. No tracking. We use no analytics cookies, no advertising cookies and no social media pixels. The visit counts on our marketing pages, the product events in the app and the error reports use no cookie and no browser storage (see sections 2.8 to 2.10 of the Privacy Policy). No company follows you across websites through Bublate. The only data an ad network gets from us is the ad measurement in section 2.18 of the Privacy Policy, sent from our server, and you can turn it off. We load our fonts from our own server, so reading our pages does not send a request to a font service.
2.2. Marketing pages. The pages of bublate.com outside the app (the home page, pricing, guides, the blog and the dictionaries) set no cookies of our own. If you open an invite or partner link (an address with ?via=), the page keeps its code in memory while you move between pages in the same tab, and stores nothing in your browser.
3. Cookies on the sign-in pages and in the app
Clerk, our sign-in provider, sets the first three cookies when you open the log in or sign up page, or the app under bublate.com/app. They keep you signed in. Without them, you cannot sign in. We set the last one only when you sign up from an invite or partner link.
| Cookie | Set by | Purpose | How long |
|---|---|---|---|
| __session | Clerk, on bublate.com | A short-lived token that shows the app you are signed in. Clerk renews it while you use the app. | 60 seconds, renewed while the app is open |
| __client_uat | Clerk, on bublate.com | The time of your last sign-in or sign-out, so the app knows when to check your session again. It holds a time, not your identity. | Clerk sets the expiry |
| __client | Clerk, on the Clerk sign-in domain of Bublate | Your sign-in session. Scripts on the page cannot read it, and your browser sends it only to Clerk. | Until you sign out or the session ends |
| bublate_via | Bublate, on bublate.com | Only when you opened an invite or partner link and then sign up: the code of that link, so your new account gets the invite credits. It holds the code, not your identity. We remove it when your account is ready. | 1 day at most |
3.1. Names can change. Clerk can add a suffix to these names, or add another cookie for the same purpose. All Clerk cookies are for sign-in and security only. Clerk documents how they work.
4. Security cookies
4.1. Cloudflare. Cloudflare runs our network. If it checks traffic for bots or attacks, it can set the __cf_bm cookie (it expires after 30 minutes without activity) or, after a security check, the cf_clearance cookie. Cloudflare does not use them to follow you from site to site. Cloudflare documents them.
5. Local storage in the app
| Key | Purpose | How long |
|---|---|---|
| bublate:lib-view | Remembers if your library shows a grid or rows. | Until you clear your browser data |
5.1. Browser cache. Your browser also keeps copies of fonts and page images that the app loads, so the editor opens faster. This is the normal browser cache, not a cookie. Clear it in your browser settings.
6. Other websites
6.1. Google, LINE and Kakao sign-in. If you sign in with Google, LINE or Kakao, you go to a page of that service. It sets its own cookies there, under its own policy.
6.2. Checkout. When you buy credits, you pay on a checkout page of Polar, our payment provider. Polar sets its own cookies there, under its own policy.
7. Consent and control
7.1. No consent banner. We use only cookies and storage that the Service needs to work and to stay secure. The law does not require consent for these, so we do not show a consent banner. If we add a cookie that needs consent, we will ask for it first.
7.2. Your browser. You can block or delete cookies in your browser settings. If you block the Clerk cookies, you cannot sign in to the app. The marketing pages work without cookies.
8. Changes and contact
8.1. Changes. We update this policy when we add or remove a cookie. We show the effective date at the top.
8.2. Contact. Questions: privacy@bublate.com.