Privacy

We store what you type in, so we can show it back to you and to the people you share it with. We do not sell it, and we do not track you around the internet — there are no advertising or analytics trackers on this site at all.

When you create an account we hold your name, email address and, if you give one, a phone number. If you subscribe, payment is handled by Stripe — card details go to them and are never stored by us.

Most of the people in a wedding plan never sign up here. When you add guests — by typing them in or importing a spreadsheet — you are giving us names, and often email addresses, postal addresses and phone numbers, for people who have not agreed to anything with us.

For that information you are the one deciding what is collected and why; we hold and process it on your behalf, and only to run the features you use. If you plan weddings professionally, the same applies between you and your clients.

RSVP forms can collect dietary requirements. Answers like “coeliac”, “diabetic”, “kosher” or “halal” can reveal someone’s health or religious beliefs, which is information the law treats as sensitive and protects more strictly.

We collect it only because a caterer needs it, we show it only to the people who run that wedding, and we never use it for anything else. Free-text boxes elsewhere in the app — notes, comments, answers to your own custom questions — can hold whatever is typed into them, so please be thoughtful about what goes there.

Venues moving from another platform can send us exported floor plans to rebuild. We use those files for one thing: recreating the room geometry — shapes, dimensions, doors, tables — as layout templates. If an export happens to contain guest lists or event details, we do not read them into our system. The files themselves are deleted once the rebuild is done, or after 60 days if it never is; the contact details from the request are kept so we can reply.

We set a cookie to keep you signed in, and store your light/dark preference in your browser. That is all. There are no advertising cookies, no analytics cookies and no third-party trackers, which is why you have not been asked to accept anything.

Wedding websites count page views as a daily total per site. No visitor identifier is stored — we use the network address only to avoid counting the same person twice, and it is scrambled before it is written down and deleted within a day.

Only people you invite to a wedding can see it. Share links, RSVP links and document links work like keys: anyone holding the link has the access it grants, which is what makes them easy to send to a caterer or a relative. You can revoke any of them at any time.

Your wedding data stays until you delete it. Abuse-prevention counters are deleted within a day. When someone signs a contract we keep a record of the signing, including the network address it came from, for as long as the document exists — that is what makes the signature evidence of anything.

You can take a copy of everything we hold, or close your account for good, from the “Your data” section of your account page — no email to us needed. Deleting shows you first which weddings go with you and which stay: one you share with someone who can still manage it keeps going without you, and one nobody else can reach is deleted along with its guest list.

You can ask what we hold about you, ask for a copy, or ask us to delete it. If you are a guest rather than an account holder, the couple or planner who added you decides what happens to their wedding’s records — but tell us and we will help you reach them.

A full technical inventory of every field the product stores is kept alongside the code, and we would rather share it than paraphrase it.

Questions about any of this, or a request about your information, can go to the address on our home page.