← Back

Cookie Policy

Last updated: 2026-05-13

1. What this page covers

This Cookie Policy explains what cookies and similar technologies (web storage, local storage, session storage, and similar client-side mechanisms) Leivar uses on its websites and Service, what each one does, and how you can control them. This page is incorporated into our Privacy Policy and uses the same terms.

2. What cookies are

A cookie is a small text file stored by your browser when you visit a website. Cookies let the site remember information about your visit, such as your sign-in state or your language preference. Local storage and session storage are similar client-side mechanisms used to keep larger pieces of state (for example a saved draft) on your device.

3. The categories we use today

3.1 Strictly necessary cookies

These are required to operate the Service and cannot be switched off. They do not require consent under the EU ePrivacy Directive or UK PECR because they are necessary for the requested service.

  • Supabase session cookies (names beginning with sb-): authenticate you, refresh your session, and protect against CSRF on state-changing requests. Set by our authentication provider. Duration: session, with a refresh token of up to 30 days unless you sign out.
  • Route trace: a per-request identifier used to correlate server logs for debugging. Not stored as a persistent cookie — passed as a header on the request.

3.2 Functional cookies and local storage

These remember preferences you have set explicitly. Disabling them will not break the Service but may reset preferences each visit.

  • Theme preference (local storage key theme): light / dark / system. Set by next-themes.
  • Studio state(local storage): in-progress editor state so you don't lose work on refresh.
  • Onboarding state (local storage): which steps you have completed.

3.3 Analytics and marketing cookies

We do not currently use any analytics or marketing cookies. We do not run Google Analytics, Plausible, PostHog, Segment, Mixpanel, Hotjar, the Meta pixel, the TikTok pixel, the X pixel, the LinkedIn Insight Tag, or any other third-party analytics or advertising tracker on our website or in the Service.

Even so, our consent banner already includes optional Analytics and Marketing categories — both off by default — so that when a tag is added in the future it can only fire after you opt in. You can change your choice at any time via the Cookie settings link in the site footer. We will also (a) update this page to enumerate the specific tag, (b) honour the Global Privacy Control opt-out preference signal for US-state users as described in our Privacy Policy.

4. Third-party content

Pages on which we embed third-party content (for example the social-platform widgets used inside our Theater preview to render a TikTok, X, or Reddit blockquote) may load scripts from that third party when you view them. Those third parties may set their own cookies under their own privacy policies. We do not control those cookies and cannot read them. The specific third parties involved are: Stripe (when you use the checkout flow), and the social platforms whose embeds you choose to render. We do not embed third-party trackers on the marketing site.

5. How to control cookies

  • Our consent banner appears on your first visit and asks you to accept all, reject all non-essential, or pick categories one by one. You can re-open it at any time via the Cookie settings link in the site footer to change your choice.
  • Your browser settings let you block, delete, or clear cookies. See the help pages for Chrome, Firefox, Safari, and Edge. Blocking strictly necessary cookies will sign you out.
  • Global Privacy Control (GPC): we detect the GPC browser signal and record it as an opt-out of sale/sharing, as described in the Privacy Policy. We currently neither sell nor share personal information nor run trackers, so there is no data flow to limit; the recorded signal will govern any future non-essential processing.
  • Do Not Track (DNT): browsers vary in their DNT implementations and the standard is no longer maintained by the W3C. We treat DNT as advisory and currently rely on GPC and explicit consent (where required) for opt-outs.

6. Changes to this policy

We will update this page when we add, remove, or change the cookies we use. The "Last updated" date at the top reflects the most recent revision.

7. Contact

Cookie questions: kamugishaibrah@gmail.com.

See also: Privacy · Terms · Sub-processors