Last updated 12 August 2026

Cookie Policy

A cookie is a small piece of text a site asks your browser to store and send back on your next request. This is every cookie codeset sets. There are two.

The cookies

Cookie	What it does	How long
`codeset_session`	Keeps you signed in. HttpOnly, so page scripts cannot read it.	7 days, or until you sign out
`codeset_workspace_ide_…`	Authorises the browser editor to reach the sandbox running your code. One per project; the trailing number is the project id.	2 hours

Why there is no banner

Consent is required for storage that is not strictly necessary to provide the service you asked for: that is what ePrivacy requires, and in Portugal what Lei 41/2004 art. 5 says. Both cookies above are strictly necessary: one keeps you signed in, the other connects the editor to the sandbox running your code. Without them you could not use codeset at all.

We run no advertising and no third-party tracking. Our page-view statistics come from Plausible, which is cookieless: it stores nothing on your device and gives you no identifier that follows you between sites or sessions. Consent under ePrivacy is about what gets stored on or read from your device, and nothing we do there is optional, so you are not asked.

If that ever changes, a banner arrives with it, and nothing non-essential gets set before you have agreed to it.

Third parties

Two services run on their own pages, under their own policies:

Google Sign-In. Signing in loads Google's sign-in library, and Google may set its own cookies as part of authenticating you. That is covered by Google's privacy policy.
Stripe Checkout. Payment happens on Stripe's own hosted page. Any cookies there are Stripe's, under Stripe's privacy policy. We never see your card details.

Plausible loads a script on our pages to count visits, but sets no cookie and reads nothing from your browser's storage, which is why it is not in the table above. What it collects is described in the Privacy Policy.

Your workspace preview runs on a separate hostname from the rest of the site, specifically so that code you are working on cannot read your session cookie.

Controlling cookies

Your browser can block or clear cookies. Blocking ours means you cannot stay signed in, so the signed-in parts of codeset will not work. Signing out clears your session cookie, and deleting your account removes the server-side session with it.

Questions about any of this: hello@codeset.ai. See also the Privacy Policy.

Adapted from Legalmattic by Automattic, used under CC BY-SA 4.0. This page is likewise available under CC BY-SA 4.0.