rsvp-to (“we”, “us”) provides event RSVP pages at rsvp-to.com/<your-event>. This policy explains what we store, who we share it with, and — importantly — when event pages and their data are automatically suspended and deleted after the event.
Your page stays live right up to your event, then winds down automatically:
This keeps your guests’ personal details from living on our servers indefinitely once they’re no longer needed. If you need your page to stay live longer, just contact us before it’s removed.
From the host (the couple / organiser): your name, email, event details, page content and colours you set, and billing information. Payment card details are handled by Stripe — we never see or store your full card number.
About guests: only what the host provides or a guest submits when replying — typically name, and any of: email, phone, attendance, party size, meal choice and dietary notes. The host is the owner of this guest information; we process it on their behalf to run their event.
Automatically: basic technical logs (e.g. that an invite link was opened) to run the service and show hosts reply activity. We don’t sell data or run third-party advertising trackers.
We use a small number of trusted processors, only to run the service:
We don’t sell your data or share it for advertising.
Guest data is retained only for the life of the event, per the schedule above (suspended 1 week after the event, deleted 1 month after). We keep encrypted backups so we can recover from failure; backup copies of a deleted event are purged on a rolling basis (within about 90 days). Basic billing records may be kept longer where required by law.
Data is served over HTTPS and stored on Cloudflare’s infrastructure. Admin access to an event requires email-verified sign-in. Payment secrets never reach the browser.
Questions, exports, or deletion requests: [email protected].