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. We count page views as daily totals without cookies, and a wedding website’s map only loads from Google if a guest taps to show it.

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.

A planning team can also share a public inquiry form. What a couple sends through it (their names, contact details, and the date, size and budget of their event) goes to everyone on that team, by email too, and the team decides what happens to it from there.

A team can track its working time. Each entry records when someone worked, on which wedding or task, and an optional note. The person sees their own time; the team’s owner and the people they make timesheet managers see everyone’s, along with what that time cost the team. Entries stay with the team, under the name they were saved with, after someone leaves it, and your own entries are in your data export.

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. It is shown to the people who run that wedding, emailed to them when a guest RSVPs, and shared with a caterer only through a link they choose to send. It is never shown back on the wedding website: finding your invitation there only needs a name, so it tells you an answer is on file without showing it. Your personal RSVP link shows what you saved. Free-text boxes elsewhere in the app (notes, comments, answers to custom questions) can hold whatever is typed into them, so please be thoughtful about what goes there.

A planner can share a booking link. Anyone with it sees the times the planner is open, and nothing else: not what’s booked, or that anything is. Booking asks for your name, email, a wedding date if you have one, and an optional note. The planner you book with sees them, Google invites you to the meeting, and we email you a confirmation with a link that cancels it. Your booking isn’t added to the planner’s client list unless they add it, or you booked from a link they sent about your inquiry.

On a team, what each appointment is (titles, clients, notes) is seen by the person whose calendar it’s on and the team’s owner, and by teammates only when that person shares it, or the team’s owner or an admin turns on details for the whole team (each person’s settings then say so). Everyone else on the team sees when someone is busy or free, so they can find a time to meet.

These services receive information to run the product, and only for that:

• Supabase stores the database, sign-ins and uploaded files, and sends sign-in codes.
• Vercel hosts the website and app.
• Resend sends our other emails: invitations, reminders, receipts and notifications.
• Stripe takes payments for Pro, and for planners’ invoices into the planner’s own Stripe account.
• Anthropic runs the planning assistant included with Pro. When you use it, your question and the wedding details it needs go to Anthropic to answer. If you connect your own AI key instead, the same goes to the provider you chose, under their terms.
• Google suggests city names as you type a location, and shows a wedding website’s map once a guest taps to see it. When Google isn’t set up, city suggestions come from OpenStreetMap (via Photon).
• Google Calendar and Meet, only if you connect your own Google account: appointments you add go on your calendar (with a Meet link when you want one), Google emails the people you invite (people on the wedding, or an inquiry’s address when you choose to invite it), and moving or changing one here changes it there. We read your calendar’s events to show you when you’re busy and to bring back appointments you moved or cancelled in Google; your other events are only shown to you, never stored. When you offer a booking link or meet with teammates, we also use when you’re busy (never what) to keep those times off your link and to show teammates you’re busy then; bookings go on your calendar with a Meet link, and Google invites the person who booked. We read when each Meet call started and ended, to log the time. We use your Google data for nothing else, keep only your Google account’s email and an encrypted key to your calendar, and forget both when you disconnect. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
• Expo, and the push services of Apple, Google and your browser, deliver notifications to devices where you turned them on.
• Twilio would send text messages; text reminders are not switched on yet, and guests will be asked before any are sent.

The assistant only sees what it needs to answer you: the wedding’s name, date and venue, its checklist, timeline and vendors, guest names and groups when you ask it to seat or invite people, and a floor-plan image when you import one. It never acts on its own; changes it suggests wait for you to confirm.

Account emails (RSVP alerts, reminders, digests and the like) can each be turned off in your account’s notification settings; every one links there. A failed subscription payment is the exception: we always tell you. Guests can stop invitations, RSVP reminders and save-the-dates from the link at the bottom of each one; they still get a confirmation when they RSVP themselves.

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. Unlocking a password-protected wedding website sets a cookie that remembers it for 30 days. Your browser also stores a few display preferences, such as light or dark mode and how lists are laid out. There are no advertising or analytics cookies and no third-party trackers, which is why you have not been asked to accept anything.

This site counts page views and access requests as daily totals per page, with no cookie and no network address. 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 cleared out after about 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. Share links and document links can be revoked at any time; a guest’s personal RSVP link stops working when that guest is removed from the list.

Your wedding data stays until you delete it. Abuse-prevention counters are cleared out about a day after the time window they count. 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. If you ask for access or write to us through the contact form, we keep your email address (encrypted) and message until you ask us to delete them or close your account.

You can download a copy of what we hold (your profile, your weddings and everything in them, your business records and links to every uploaded file), 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 and files.

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 through the Contact link at the bottom of this site’s pages. We reply by email. There is no separate email address yet.