Cookie policy

1. This website

The marketing site you are reading sets no cookies. There is no analytics script, no advertising pixel, no session recording and no third-party tag. Fonts and assets are served from the same origin rather than a third-party network.

It stores one thing, and only if you ask it to: the light or dark choice from the switch in this footer, kept in your browser's local storage under `pulseup-theme`. It is not a cookie, it is never sent to us or to anyone else, and until you use the switch nothing is written at all. If you chose earlier, under the older `sama-theme` key, that choice is carried over once and the old key is then removed. Clearing site data removes it and the site returns to dark.

2. The product

• Session cookie — essential. Set when you sign in, marked HttpOnly, restricted to same-site requests, and marked Secure when the deployment is behind HTTPS. It holds an opaque identifier, never your credentials. Deleted when you sign out; expires according to the session lifetime your deployment configures.
• Cookie domain — where a deployment uses one workspace per subdomain, the session cookie may be issued for the parent domain so a single sign-in spans them. This is a deployment setting.
• Theme preference — stored in your browser's local storage, not sent to the server, so the interface does not flash the wrong colour scheme before it loads.

3. What we do not use

• No analytics or product-telemetry cookies
• No advertising or retargeting cookies
• No social-media embeds that set cookies
• No cross-site tracking of any kind

4. Managing cookies

You can clear or block cookies in your browser. Blocking the session cookie will prevent you from staying signed in to the product, because it is the mechanism by which a signed-in session exists.

5. Error tracking

Where a deployment enables error tracking, a crash report may be sent to the configured error-tracking service. This uses no cookie, and the feature is off unless the deployment's operator switches it on.