No banner, because there is nothing to consent to.

1. What we set

Only cookies that are strictly necessary to deliver the service you asked for. The public pages of this site — including the one you are reading — set no cookie at all. Cookies appear once you sign in.

• sb-<project>-auth-token

  Holds your signed-in session. Without it, every page load would send you back to the login form.

  Set by

  First party, set by our authentication provider

  Duration

  Session, refreshed while you browse; removed on sign-out

• sb-<project>-auth-token.0, .1, …

  The same session token, split across numbered cookies when it exceeds the size a single cookie can hold.

  Set by

  First party, set by our authentication provider

  Duration

  Same as above

<project> stands for the identifier of our database project, which is why the exact name you see in your browser is longer than the one printed here.

2. What we do not set

• No analytics. No Google Analytics, no Plausible, no Vercel Analytics, no product-analytics SDK. klaspr currently has no measurement of how its pages are used.
• No advertising or retargeting pixels. Nothing is shared with an ad network.
• No session recording or heatmaps.
• No third-party font requests. Typefaces are downloaded when the site is built and served from our own domain, so loading a page sends no request to a font provider.

You can verify all of this from your browser’s network panel rather than taking our word for it, which is the point of stating it precisely.

3. Why there is no consent banner

European rules on cookies require consent before storing anything on your device — except where the storage is strictly necessary to provide a service you explicitly requested. A cookie that keeps you signed in after you chose to sign in falls squarely within that exemption.

Since klaspr sets nothing outside that exemption, a banner would ask you to consent to nothing, and train you to dismiss a question that carries no information. If that ever stops being true, a banner will appear before the tracker does — not after.

4. Controlling cookies

Every browser lets you view, block and delete cookies. Blocking ours has one consequence, and it is total: authentication stops working and you cannot use the signed-in part of klaspr. The public pages continue to work normally.

Signing out removes the session cookies immediately.

5. Changes

Product analytics is on klaspr’s roadmap and is not built. If any tool is added that stores or reads something on your device beyond the strictly necessary, this page will be updated and consent will be requested first. Questions: [privacy contact email]