Cookies

Schemahaus uses as little browser storage as it can. There is no advertising, no tracking across sites, and no third-party analytics.

What is set, and why

A session cookie, once you sign in. It is what keeps you signed in. It is httpOnly, so scripts cannot read it, and marked SameSite so it is not sent from other sites. Signing out removes it.

A cross-site request forgery token, set alongside the session, so that a form submitted from somewhere else cannot act as you.

One entry in local storage recording that you dismissed the cookie notice, so it does not reappear on every page. It contains a timestamp and nothing else.

That is the complete list. None of it is used to build a profile of you, and none of it is shared with anybody.

Why there is no "reject" button

The banner on the marketing pages is a notice, not a consent gate, because there is nothing here to consent to: everything above is strictly necessary to provide a service you asked for, which is the exception the ePrivacy rules are built around. A banner offering a choice that changes nothing would be theatre, and one that blocked the page to collect a click for a session cookie would be worse.

If we ever add analytics or anything that follows you between sites, this page and that banner both have to change, and the banner will need a reject that genuinely rejects.

Turning them off anyway

Your browser can block or delete cookies for this site. If you block the session cookie you will not be able to stay signed in, because that cookie is the mechanism.

Inside the dashboard

The dashboard sets no notice of its own. You are already signed in there, so the only storage in play is the session, and repeating the notice on every screen of a tool you use all day teaches people to dismiss notices without reading them.