We do not use cookies

No cookies at all

MetaOpus sets no cookies. Not analytics cookies, not advertising cookies, not "strictly necessary" session cookies. There is no cookie banner on this site because there is nothing a banner could ask you about.

This is a statement about the software, not an intention. A cookie is data the browser attaches to every request it makes to us; the platform never asks for one and never reads one.

What we do store, in your browser

Signing in to the application writes a small number of values to localStorage. That is browser storage, and it differs from a cookie in the way that matters: it is never transmitted automatically. It is read by the application's own code, on your device, and sent only when that code deliberately sends it.

• metaopus.token — your session token, which is what keeps you signed in.
• metaopus.refresh — renews the session so you are not signed out mid-task.
• metaopus.user — your name and email, so the interface can greet you without asking the server again.
• metaopus.access — the permissions your role carries, so the interface can hide what you cannot use. The server checks them again on every request regardless; this copy is for the screen, never for the decision.
• metaopus.tenant — which organisation you are currently looking at.
• metaopus.theme — light or dark.
• metaopus.bench.insights, metaopus.submissions.insights, metaopus.audit.charts — whether you had those panels open last time.

None of it is advertising data, none of it is shared, and none of it describes anything you did beyond the preferences above.

Clearing it

Signing out removes the session values. Clearing site data for this domain in your browser's settings removes all of them. The application will ask you to sign in again; nothing else is lost, because none of this is where your work is kept.

Third parties

The public site loads no analytics, no tag manager, no advertising pixel and no social embed. If we enable Cloudflare Turnstile on the contact form to stop automated submissions, it is chosen specifically because it sets no cookies and does not profile the visitor; it sees the request that submits the form and nothing else.

If this changes

If MetaOpus ever adds something that does set a cookie — product analytics, a support widget, an embedded video — this page changes first, and a consent mechanism arrives with it. We would rather publish a short honest page now than a long one describing arrangements we do not have.