Cookies

A cookie is a small file a site asks your browser to store and hands back to a server on every request. This site asks for none. It has no server of its own to hand one back to: the pages are static files, and everything they do happens in your browser and talks directly to the database.

What it uses instead is your browser's own local storage, which works differently in one way that matters: it is never sent anywhere. It stays in the browser, is readable only by this site, and travels with no request. The law treats both the same way, and so does this page — the question is what is kept on your device, not what it is called.

All of it. There is no sixth thing, and nothing here is optional in the sense of being something you could switch off and still use what it supports.

Because there is nothing here the law asks you to be given a choice about. The rule — article 11.7a of the Dutch Telecommunicatiewet — covers anything stored on your device, cookie or not, and exempts what is strictly needed to deliver what you asked for.

Three of the four keep a sign-in you started. The fourth remembers a button you pressed yourself, and is a single character long. None is read by anyone else, and none is used to tell one visitor from another.

A banner that asked you to consent to those would be theatre, and it would train you to click through the ones that matter elsewhere. If that ever stops being the honest answer — if anything is added that measures, advertises or embeds — this page changes first and a real choice arrives with it.

No analytics of any kind. Nobody is counting your visit, and there is no dashboard somewhere with a line on it for this page view.

No advertising, no ad network, no conversion pixel, no social buttons, and nothing sold or shared with a data broker. No fingerprinting — no attempt to recognise your browser by its fonts, its screen or its quirks.

No third-party fonts or scripts. The typefaces are served from this site rather than from a font service, so loading a page tells nobody but the servers listed below that you did.

That last one is enforced rather than promised: the site ships a Content Security Policy that permits the page to talk to its own database and nowhere else. A tracker added by accident would not run — the browser would refuse it.

Storage on your device is not the only way a site knows something, and a page about the first that said nothing about the second would be misleading.

The pages are delivered by Cloudflare and the data comes from Supabase, both in the European Union. Both keep ordinary server logs, which include the address your request came from — as every web server has since before cookies existed. They are used to run and secure the service, not to profile anybody.

Cloudflare's own bot protection can set a cookie of its own (`__cf_bm`) if it is switched on for this deployment. It is a security measure belonging to them, it identifies a browser rather than a person, and nothing in this application reads it.

Signing in with Google sends you to Google, and Google and Supabase set their own cookies on their own addresses as part of that. They are theirs, governed by their policies, and this site never sees them. Signing in with an email and password involves none of it.

A link to a song on Spotify, or a venue on a map, is a link. Nothing is embedded, so no third party is contacted until you decide to follow one — and from there you are on their site under their rules.

A guest opening the page a couple published, reading it, and answering their invitation has nothing at all stored in their browser by it. No cookie, no local storage, nothing to clear afterwards. The whole of this page is about the planning software behind that page, which guests never sign in to.

Signing out removes the two sign-in keys immediately. Closing the tab removes the demo one.

Everything listed here is cleared by your browser's own “clear site data” or “clear cookies and site data” control, which every browser has under privacy settings. Nothing breaks: you will be asked to sign in again, and the bar offering another language will offer once more.

Blocking storage for this site altogether is your right and it does have a cost — signing in is what it pays for, and a browser that refuses to keep the token cannot keep you signed in from one page to the next.

The date at the top is when this last changed, and the current version is always the one on this page. Anything that adds to the table above changes this page in the same release rather than afterwards.

Questions, including what is held about you and asking for it to be deleted: hello@ceremonystudio.example. This page is about your device; the privacy notice linked below is about you, and the terms of use cover the rest of the service.