privacy · in plain language

What we store, and what we do not.

You are inviting four hundred people by name and by number. You should know where that list sits, who can reach it, and when it goes. So it is written here in sentences you only have to read once.

Read the terms →

what the diary holds

What is in it, and what for.

Everything below is put there by you, or by a guest answering. Nothing arrives from another source.

What

What for

Your guest’s name, and the language they read in: Their invitation opens with their own name, in their own language.
A phone number or an email address, if you enter one: So you can send them their own link from your own phone. We send nothing ourselves.
The household, the family branch and the number of plus-ones: So one answer covers the whole family and the list counts people rather than invitations.
The answer per celebration, with a dietary note if they leave one: That is the guest list. Without it there is nothing to count.
A birth year, if you keep one: For your own grouping. It never leaves this diary — it is on no guest page and in nothing that travels outward.
Your own days, suppliers and amounts: The day plan and the budget. Your wedding team never sees the amounts.
When an invitation was opened, and how many times: So you know who still needs a phone call. What that does and does not include is below.
The email address and password of your own account: To let you in. Your guests have no account, and so no password.

What never goes in

No advertising identifier, no profile at an ad network, and no list handed to a third party.
No location for anybody, and no fingerprint of the device or the browser.
No card or bank details. Paying happens on Mollie’s page; we see the reference, the amount and the date, never your card or account.
No gift money running through us: the platform does not touch that money at all.

where it sits

In Frankfurt, inside the EU.

The database and the files sit with Supabase in Frankfurt. The diary itself runs on Vercel, and so does the site you are reading now.

Payments run through Mollie B.V. in Amsterdam, which is its own controller for them. Of a payment we keep the reference, the amount, the date and the invoice number — for seven years, because tax law asks for it.

Until you say yes to being measured, these pages fetch no font, no script and no image from a third party. Say yes and exactly one script loads — Google Analytics — and nothing else. There is nobody in the middle watching without your knowing.

whose it is

The list is yours.
We keep it for you.

You decide what happens to your guest list: who goes in, who gets a link, what comes out. We carry that out and do nothing else with it.

In the language of the law: the couple is the data controller for their guests’ details, and we are the processor. What that means in practice — what we may and may not use the details for, and what happens when you stop — is written into the terms, in the same plain language as here.

We do not email your guests, do not call them, and sell them to nobody. Not to the venue, not to the photographer, not to anyone else on your wedding team.

The agreement, written out →

what we measure

Verbatim

This, yes.
That, no.

We record when a link was opened, how many times, roughly what kind of device, and the language chosen.

Not where anyone is, not a fingerprint, not an advertising ID. And none of those numbers reaches an ad network, because there is not one on this site.

Every guest page carries a line telling your guests exactly this. They should read it from us, not have to take it on trust from you.

what your guests see

A link travels further than you think.

Nothing is public until you publish: Until you publish the invitation, nothing exists for the outside world. No page, no preview, no search result.
Guest pages do not ask to be found: They carry noindex and nofollow. A search engine has nothing to index here, and is told so.
The share card names only you and the date: Never the guest. Links get forwarded around family groups, and the preview that appears must give nobody away.
The four digits before answering: To answer, your guest confirms the last four digits of their own mobile number. Their device remembers that for 60 days; five wrong tries locks it for fifteen minutes. Guests with no number on file pass straight through.

when it goes

A guest list should not sit there forever.

A wedding is an occasion, not a subscription. Your guests’ details have no business lying around years after the last dance.

90 days after the wedding

Your guests’ details are deleted. Before that you export whatever you want to keep: the list, the answers, the day plan, the amounts.

Deleting your account

For thirty days you can undo it — for the day you do it by accident. After that it is gone, and we cannot bring it back either.

Sooner, if you want

You do not have to wait for the 90 days. One guest, one celebration or the whole wedding: what you delete is deleted.

Honestly about what this is: it is a policy and a job set to carry it out. It is not years of operating history we can point at — the first real wedding has not happened yet. We would rather write that down than let it sound like a track record.

One bar, with one question.

This site sets no advertising cookie, runs no pixel and does no retargeting. The bar you see asks one thing: may we measure how the site is used? Say no and we load nothing, and we will not ask again for a year.
Say yes and we use Google Analytics: which pages are visited, from what kind of device and which country, and which buttons are clicked. Google processes that in the United States under the EU-US Data Privacy Framework and does not store your IP address. We never see who you are — only that someone was here.
What does exist: what is needed to keep you signed in to your own diary, and your guest’s device remembering for 60 days that they have already confirmed themselves.
There is no chat widget, no heatmap and no ad tag on this site. The moment one appeared, “your list stays yours” would stop being true, and that sentence is worth more than the measurement.
Separately, we measure two things without asking: page views with Vercel Web Analytics, and how quickly the pages load for you with Vercel Speed Insights. Both without a cookie, without an advertising ID, without a profile across sites, and both scripts are served from our own domain — which is why we ask nothing for them. None of the three runs on your guests’ pages or inside your diary.
Changed your mind? The button below brings the question back so you can choose again.

having something removed

See it, correct it, delete it.

Most of it you do yourself, inside your own diary: every guest can be edited, exported and deleted. If a guest asks, you can point them at you or do it for them. Whatever you cannot find there, ask us — a person answers, no ticket queue.

Who builds this, and why →