What We Do With Your Data

You are putting other people's names, dietary needs and family arrangements into a website. It is fair to want to know what happens to them.

This page is the plain-English version. The Privacy Policy is the binding document and it wins if the two ever disagree; this one is here so you do not have to read six hundred lines of it to answer an ordinary question.

What we store about a guest

Only what you type. A guest needs a name and nothing else.

Everything else is optional, and it is there because seating needs it: an email if you want to send them their table, dietary notes and a meal choice for the caterer, an address if you are tracking who to thank, a language, a job in the wedding party, an employer if you are keeping colleagues together, and private notes for you.

We never ask for a date of birth. Where age matters, for a children's table or a high-chair count, we store an age band and nothing finer. That is a deliberate limit in the database, not a setting: there is no date-of-birth column to fill in.

We do not ask for phone numbers, and we never see card details. Payments go straight to Stripe.

Whose side a guest is on is your words, not ours

If you split the room into two halves, the halves are labelled with whatever you called them. Import a spreadsheet that says "Partner A" and it stays "Partner A". Type your own names and it uses those.

Who can see what

Private notes stay private. A guest's private notes never appear in any export, any printed sheet, any share link or any email. That is enforced by a test that checks every route that sends data out of the app, not by everyone remembering.

A share link shows the plan, not the file. When you send a link, whoever opens it sees where people are sitting. It does not carry your private notes.

We do not sell anything, and there is no advertising. Nobody buys a list from us because we do not have one to sell.

How long things are kept

Your wedding is yours. We do not automatically delete your guest list after the day, and that is on purpose: your plan becomes a keepsake you can still open and download afterwards, and deleting the guests would delete the plan. If you want it gone, you say so, and that is covered below.

The plumbing is a different matter, and it clears itself out on a schedule:

• sign-in links and similar one-time tokens: 7 days
• login sessions: 30 days
• background job records: 90 days
• delivery records for outgoing webhooks: 90 days
• records of notifications we sent: 180 days
• daily counts with no names in them: 400 days

Taking your data out

There is a button. Account settings has an export that downloads everything we hold for your account as a JSON file. No email, no ticket, no waiting.

Keep your own copy

An export is a copy of your data in our shape. A copy you can read on the day is a different thing, and it is worth having both.

• Print the floor plan. The seating plan as a drawing, on paper, in the bag with the place cards. It works when the venue's wifi does not.
• Download the guest list. The deliverables page exports the guest list and the caterer sheet as CSV files, which open in any spreadsheet.
• Export everything from account settings. The JSON above is the complete record, and it is worth taking once the plan is final.

None of this depends on us being reachable. That is the point of it.

Deleting a guest, or a household

You can delete any guest or any household yourself, at any time, from the guest list. That is immediate and it is the control most people actually want: someone was added twice, or a household dropped out, or a name went in that should not have.

Deleting your account

Also a button, in settings, behind a typed confirmation so it cannot happen by accident.

Deleting your account signs you out and disables it straight away. After 30 days we permanently delete your sign-in details.

What happens to your weddings depends on whether anyone else is in the workspace.

• If you are the only person in it, your weddings go with your account: the guest lists, the households, the tables and the seating plans are all deleted.
• If anyone else has joined - your partner, or a planner's colleague - your weddings stay where they are. They belong to the workspace rather than to your login, and one person leaving should not take the other's work with them.

You can also delete a single wedding yourself at any time, from the bottom of its documents page. That takes the guests, the tables and the plans in it too, and there is no undo.

If you want a copy before you go, export it first. If you want the guest data gone, delete the guests or the households, which you can do yourself.

If something here is not enough

The Privacy Policy has the formal detail, including the legal bases we rely on, who processes data on our behalf, and how to complain. The subprocessors page lists the companies involved.