Cookies
Cookie Policy
One cookie, on the part of the site your guests never see. Wedding websites set none at all.
Last updated 10 September 2026
Wedding websites set no cookies
The website your guests open sets nothing on their device — no cookie, no analytics, no advertising or tracking pixel, and nothing that follows them to another site. A guest can read the page, reply, leave a message and upload a photograph without a single cookie being written.
The one cookie we do set
When the provider signs in to run the studio, we set one cookie that keeps them signed in. It holds a session identifier and nothing else — no name, no email address, nothing about any guest. It is what security law calls strictly necessary: without it, signing in does not work at all.
There is no consent banner, because nothing here can be refused. A banner exists to ask about cookies you can decline and still use the site — advertising, embeds, analytics that follows you from one site to the next. We run none of those. What we do run, this cookie and the check on our inquiry form below, is strictly necessary: refusing it would mean not signing in and not sending the form.
What a browser fetches from elsewhere
A wedding website loads its lettering from Google Fonts, its photographs from Cloudflare, and — on a page showing a venue map — that map from Google Maps. Those requests do not set cookies on the wedding site — any cookie Google Maps keeps is on Google’s own domain, under Google’s privacy policy — but to send the files each of them sees the visitor’s IP address and browser, as happens on any site that loads a font, a photo or a map. Our privacy policy says the same thing beside everything else we hold.
Our own inquiry form is the one exception. It carries Cloudflare Turnstile, which checks that a person rather than a machine is writing to us, and Cloudflare’s check may keep its own short-lived token in your browser to remember that you passed it. It is there to protect our inbox, it cannot be refused and still leave you able to send the form, and it runs nowhere near a wedding website.
Counting visits to our own pages
Our own pages — the ones describing what we make, not the wedding websites — count how many people read them, so we know whether the money we spend on advertising was worth spending. The count is made without a cookie and without writing anything to your device, and it records the page and where the visit came from rather than anything about you. It runs nowhere near a wedding website. There is nothing here to accept or refuse, which is why there is still no banner asking you to.
If this ever changes
If we add anything that sets a cookie you could refuse — analytics, an advertising pixel, an embedded video or feed — we will say so on this page, date the change, and ask for your consent before it runs. We will not add one quietly.