Cookie Policy

1. Signing you in

When you sign in, Clerk — the service that handles our logins, and one of the named providers — sets a session cookie. It is what keeps you signed in between pages; without it every click would return you to the login screen. It is strictly necessary in the ordinary meaning of the term, and there is no version of the application that works without it.

2. Holding a workspace you have not signed up for

If you press “Start free” or open the sandbox without an account, we set one cookie holding a random token. That token is the ONLY thing connecting your browser to the temporary workspace you are using — without it, the work you do in that workspace becomes unreachable to you the moment you close the tab.

It carries no name, no email and nothing about you; only the token is stored, and only as a hash. The workspace behind it erases itself after 168 hours (or 24 for the seeded demo), which is set out on the privacy page alongside every other retention window.

This is the one cookie we set ourselves, so it is the one we can describe exactly rather than in outline:

• Name: sv_guest, set on this domain only.
• Contains: a random token, and nothing else. Not an identifier for you, not an email, not a workspace name.
• Lifetime: the same 168 hours as the workspace it unlocks, so the cookie cannot outlive the thing it points at.
• Flags: HttpOnly, so no script on the page can read it; SameSite=Lax, so it is not sent from another site; and Secure in production, so it never travels over plain HTTP.

Delete it and the workspace becomes unreachable — not deleted, but with nothing left that can find it, which for a trial workspace amounts to the same thing. Creating an account converts it into a normal workspace and the cookie stops mattering.

3. Turning them off

Every browser can block or delete cookies for a single site, usually behind a padlock icon in the address bar, and everything here obeys that.

What that does depends on which one you block. Blocking the analytics cookie costs you nothing — nothing on this site checks whether it loaded. Blocking the session cookie means you cannot stay signed in; blocking the sandbox one means “Start free” gets you a workspace you cannot return to. Neither is us penalising you: they are the mechanism, not a gate in front of it.

We do not read a Do Not Track or Global Privacy Control signal, and we would rather say so than imply a control we have not built. Nothing here is a sale or a share of personal information in the sense those signals are aimed at, so there is nothing for one to switch off; the setting to reach for is your browser’s own cookie control, which we do obey.

4. Counting page views

We use PostHog to see which pages get read and where people give up. It runs in its cookieless mode: it sets no cookie and writes nothing to local or session storage. The work of not counting one visit as two happens on PostHog’s servers instead of by leaving an identifier on your machine. It is on the subprocessors list with everything else that receives data, and what it gets is stated there: which pages are used and which actions are taken — never the contents of a document.

What it is configured NOT to do is the part worth stating: no session recording, no automatic capture of everything you click, no surveys, and no dead-click tracking. It is deliberately proxied through our own domain rather than loaded from a third-party host — which is PostHog’s own documented deployment for a site that would rather not have another origin in its content-security policy, not a way around anything.

This is the one family you can remove without breaking the product. Any browser setting or extension that blocks it is fine by us; nothing on this site checks whether analytics loaded.

The honest trade: because nothing is kept on your device, we cannot tell that today’s reader is the same person who was here last week. We took that over asking you to approve something first.

5. Why you have not seen a consent banner

Because there is nothing here to consent to. The rule that makes a banner necessary is about storing something on your device that the service you asked for does not need — and analytics is the usual reason a site has to ask. So rather than ask, we stopped storing. Our analytics runs in a mode where it sets no cookie and writes nothing to local or session storage; a visit is counted on the server without leaving an identifier behind on your machine.

Beyond that: we run no advertising, share nothing with an ad network, set no cookie that identifies you on another company’s website, and do not sell or share personal information as those terms are used in US state privacy law.

Showing a banner anyway would be theatre: it would ask you to approve something that is not happening, and it would train you to click through the next one.

6. If this changes

If we ever add an advertising or cross-site tracking cookie, the paragraph above stops being true, and a consent mechanism stops being a design choice and becomes a requirement. This page would change first.

Questions, or a request about your own data: privacy@sealinn.com. What we hold and for how long is on the privacy page; every company that receives any of it is named on subprocessors.