1. Short version
condei.app sets no cookies at all — not ours, not anyone else's. The only thing it stores in your browser is a single flag, held in sessionStorage, that stops the launch animation from playing twice in the same browser tab. It is not sent to any server, it is gone when you close the tab, and nothing else on this website reads or writes anything to your device. We show no cookie banner, because nothing here needs your consent to operate — see section 4 for why.
This is the complete inventory. There is nothing else to disclose.
2. Everything this website stores on your device
| Name | Kind | Set by | Purpose | Lifetime | Sent to a server? |
|---|---|---|---|---|---|
condei.launched | sessionStorage | assets/site.js, and inline in the page <head> of / | Marks that you have already seen the pen-to-logo launch animation in this browser tab, so it does not replay if you navigate within the site and come back. Purely visual; nothing is recorded about you. | Until you close the tab or end the browsing session. Not shared between tabs, and not restored if you reopen the site later. | Never. It is read only by the page itself, in your own browser. |
Nothing else — no cookie, no localStorage, no IndexedDB, no cache API storage, no fingerprinting, no pixel — is set by any page on condei.app, including the invite page, the delete-account page, the Sign in with Apple hand-off page, or the /app/* pages. We checked every script this website loads (assets/site.js, assets/invite.js, assets/auth-apple.js) to write this table, and we will update it the day that changes.
The one exception to "no network requests." The invitation page (/app/invite) calls api.condei.app to look up the invitation you were sent. That is an ordinary network request to our own server, covered by the Privacy Policy, not a cookie or browser storage — no cookie is set as part of it, and the invitation token lives only in a JavaScript variable in that page, never written to storage (see the Privacy Policy and README.md's description of /app/invite).
There is no analytics on this website. No Google Analytics, no Plausible, no server-side page-view pixel, nothing. We do not know how many people visit condei.app, which pages they looked at, or where they came from.
3. Fonts, and everything else that loads
The typefaces (Fraunces, Karla) are self-hosted .woff2 files served from condei.app itself — not Google Fonts' own servers — so loading a page never tells Google, or anyone else, that you visited. The wordmark is inline SVG. Nothing on this site is fetched from a third-party domain. See Credits & licences for the fonts' own open licence.
4. Why no consent banner
UK law (the Privacy and Electronic Communications Regulations 2003, "PECR", regulation 6, as amended by the Data (Use and Access) Act 2025 with effect from 5 February 2026) requires consent before storing or reading information on a visitor's device, with listed exceptions. condei.launched falls within an exception on two independent grounds:
- Adapting the appearance of the service to the user. The 2025 amendment added a specific, consent-free purpose for storage used only to adapt how a service looks or behaves for the person using it in that visit — exactly what this flag does: it adapts the page so the animation you have already seen does not play again. It carries none of the conditions attached to the separate statistics exception (no opt-out mechanism is required for this purpose).
- Strictly necessary to provide the service you asked for, in the narrower, pre-2025 sense the Information Commissioner's Office has long recognised: remembering something for the length of one visit, in order to avoid repeating something you have just done, with no tracking, profiling or cross-session memory involved.
Either ground is enough on its own. The flag is first-party, session-only, carries no identifier that could be linked to you, is never transmitted anywhere, and does nothing beyond skipping an optional, skippable animation. That is about as low-risk as browser storage gets, and it is not the kind of "non-essential" tracking the consent requirement exists to catch.
Because no consent is legally required, we have not built a banner. Building one anyway would add a second interaction most visitors do not need, for a flag that does nothing but skip an animation.
5. If this ever changes
If condei.app ever adds analytics, advertising, embedded third-party content, or any storage that goes beyond adapting your immediate visit — a real cookie, a tracking pixel, a persistent identifier — this page will say so first, and a consent banner will be built before that code ships, not after.
6. Questions
Email support@condei.app. See also the Privacy Policy, which covers what our apps and servers collect once you have an account — a separate subject from this page, which is only about your browser when you visit this website.