Privacy Policy

“We” / “us”— The Vow Day, the operator of this service. Contact: info@seatedinloves.com.

“Couple” / “Operator”— the people who created the wedding on The Vow Day and sent you the RSVP link. They decide what questions to ask, who can help plan, and what to do with your answers. Under data protection law, the couple is the data controller for their guest list. We are the data processor acting on their behalf.

“Guest”— you, if you’re responding to an invitation.

From guests (submitted through the RSVP form):

• Your name and any plus-one names you add.
• Your email address and/or phone number — only when the couple asks for them, and only if required or if you choose to provide them.
• Your attendance status (accepting / declining) for each event.
• Your answers to any custom questions the couple added (e.g. meal preference, dietary notes, song requests). Some of these may describe health or religious information — see Section 6.

From couples / operators:

• Your account email, and either a password hash (email + password sign-up) or an OAuth identifier (Google / Apple sign-in).
• Your wedding details, guest list, seating arrangement, and settings.
• The admin-only AI assistant receives your seating data when you send a chat message — see Section 5.

Automatic / technical data on every visit:

• Basic request telemetry (route, timestamps, session identifier) stored on our server for product diagnostics.
• If the site is configured with a Google Analytics ID, anonymised pageview data is sent to Google (current build: analytics loads only when that ID is set).

• To run the service — storing RSVPs, tying guests to seats, sending the couple a notification when you submit, and emailing you a confirmation with a calendar invite if you provided an email.
• To let the couple (and anyone they've invited to help plan) see and act on your answers within the app.
• To provide the AI chat assistant, when the couple or a helper opens it.
• To fix bugs and prevent abuse. We don’t profile guests, we don’t sell data, and we don’t run ads.

If you’re in the UK or EU: the couple relies primarily on legitimate interests (organising their wedding) and, where they ask a sensitive question, on your explicit consent. You can withdraw consent at any time by asking the couple or emailing us at info@seatedinloves.com — we’ll remove your data unless we’re legally required to keep it.

• Anthropic(AI assistant). When the couple or a collaborator uses the chat feature, the current seating state and any files they attach are sent to Anthropic’s API. Anthropic is under commercial API terms (no training on your data; 30-day retention at their end).
• Email provider (SMTP). Used to send RSVP confirmations, reminders, and account emails (verification, password reset).
• Meta / WhatsApp Business. Used only when the couple sends a broadcast to guests; your phone number and the message body are shared with Meta to deliver the message.
• Google Maps / Places. Used when the couple types a venue address into the event editor. No guest information is sent.
• Google Analytics. Optional. When enabled, standard GA4 telemetry (pageview URL, IP, GA cookies) is sent to Google. If you are in the EU/UK, we aim not to set analytics cookies without your consent.

We do not share data with advertisers, data brokers, or social-media platforms.

Couples sometimes add questions like “Any dietary restrictions or allergies?” or “Meal preference (Halal / Kosher / Vegetarian)”. Your answers may reveal health or religious information. Under UK/EU law these are “special category” data and processing them normally needs your explicit consent.

If you don’t want to share that information with the couple and their planners, leave the field blank (when optional) or skip the question and contact the couple directly.

Guest RSVP data is kept for as long as the couple keeps their wedding in the app, plus a short grace period for backups. The couple can delete their wedding at any time, which removes all guest data. You can also ask us to delete your entry (Section 9).

Server-side telemetry is trimmed automatically on a rolling basis.

We store data on our own servers with standard filesystem permissions. Connections are HTTPS. Auth uses short-lived sessions; RSVP magic-links are single-purpose tokens. No system is perfectly secure — if we learn of a breach that affects you, we’ll notify the couple and, where the law requires, the supervisory authority and affected guests.

You can ask to see, correct, or deleteyour information. The fastest route is to contact the couple who sent you the link (they have direct controls in the app). If you can’t reach them, email us at info@seatedinloves.com with the wedding name and your name, and we’ll help.

If you’re in the UK or EU, you also have the right to lodge a complaint with your local data protection authority.

The service isn’t directed at children. If a guest under the age of consent appears on a guest list, the couple is responsible for obtaining consent from a parent or guardian before entering the child’s details.

We’ll update this page when the product changes in ways that affect your privacy. The “Last updated” date at the top tells you when.

Questions? Email info@seatedinloves.com.