The Cordially Invited· Privacy

Privacy notice

Last updated July 27, 2026 · Private beta

The short version

We collect what’s needed to host a wedding site and gather RSVPs — nothing is sold, and nothing is used for advertising. Couples own their guest lists; we process guest information only on the couple’s behalf. Wedding sites are private by default: they are excluded from search engines and can be protected with a site password.

What we collect from couples

Your email address for sign-in (we use magic links, so there is no password to store), the content of your wedding site (names, date, location, stories, photos, schedule, travel, registry, and FAQ entries), your chosen design and identity settings, and your guest list. If you request beta access, we also keep the request itself: your name and email, your partner’s name, your wedding date and location, and the short description you wrote.

What we collect from guests

Whatever the couple adds to their roster (typically names, household groupings, and sometimes an email address), plus what a guest submits when responding: attendance, meal choice, and any dietary, accessibility, travel, or lodging notes. The couple is the owner of this information; The Cordially Invitedstores and processes it on the couple’s behalf. If you’re a guest and want your information removed, ask the couple — they can remove you from their list, which deletes your response. The full lifecycle is described in our retention policy.

How we use it

To run the service: rendering the wedding site, matching guests to their invitation when they RSVP, showing the couple their responses, and sending the emails the service requires — sign-in links, and invitations or updates the couple explicitly sends. We also process technical logs and use bot protection to keep RSVP and sign-in safe. On our public marketing pages, we use Google Tag Manager to measure visits and understand which parts of the site are useful. We do not run analytics on couple dashboards, wedding websites, or RSVP flows. We do not use this data for third-party advertising, and we never sell or rent personal information.

Cookies

The service uses a session cookie when a couple signs in, a secure cookie that lets a household return to edit its RSVP, and a cookie that remembers a site-password unlock. Analytics configured through Google Tag Manager may also use cookies on our public marketing pages. There are no advertising cookies on wedding websites or RSVP flows.

Who processes data for us

We run on a small set of infrastructure providers acting on our instructions: Supabase (database, authentication, and file storage), Vercel (hosting), Resend (email delivery), Cloudflare Turnstile (bot protection), Sentry (error monitoring), and Stripe (payment processing, once paid plans are live — Stripe receives payment details directly; we never see card numbers). Data is processed in the United States.

Privacy of wedding sites

Published wedding sites are excluded from search-engine indexing during the beta, whether or not a site password is set. Guests reach a site through its direct link, an invitation, or a QR code. Couples can additionally require a site password.

Your choices and rights

Couples can export their guests’ responses at any time, correct any content themselves, and delete their wedding from the dashboard. For access, correction, or deletion requests beyond that — or any privacy question — email hello@thecordiallyinvited.com and we’ll respond within 30 days. Depending on where you live, you may have additional legal rights to access, correct, delete, or restrict processing of your information; we honor these for everyone regardless of location.

Children

The service is for adults planning a wedding and is not directed to children under 13. We do not knowingly collect information from children; a couple’s roster may list child guests by name for seating and meals, and that information is handled under the same rules as all guest data.

Changes

If this notice changes in a way that matters, we’ll post the update here and revise the date above. During the beta we’ll also email account holders about significant changes.