We do not set any.

No analytics cookies, no advertising cookies, no session cookie. That is why you have never seen a consent banner here, and it is not an oversight.

What we do store

Three things, all in your browser’s local storage rather than in a cookie, which means none of them is attached to a request or sent to a server. They exist so the product works when you are not signed in.

cue_auth

Your email, name and the two tokens that keep you signed in.

Why: So a reload does not sign you out.
Written: Only after you sign in.
Kept: Until you sign out, or you clear site data.

cue_local_codes

The codes you pressed Save on: type, contents, shape and colour.

Why: So the library at /codes survives closing the tab, without an account.
Written: Only when you save a code.
Kept: Until you remove them, or you clear site data.

cue_builder_draft

Whatever is currently in the builder on the front page.

Why: So a reload does not throw away the code you were making.
Written: As soon as you use the builder.
Kept: Overwritten as you type. Never leaves the browser.

Third parties

The free pages may carry contextual advertising, chosen on what the page is about rather than on who is reading it. It sets no cookies and reads no browser storage. The ad server does receive the requesting IP address and the page address, because it cannot answer a request without them.

Clearing it

Signing out removes cue_auth. Removing a saved code removes it from cue_local_codes. To remove everything, clear site data for this domain in your browser settings, or open the developer console and run localStorage.clear(). Nothing is kept anywhere else, so there is nothing to ask us to delete.