The house
Your guest list is
not our mailing list.
To run your event we ask for something genuinely personal — the names, addresses, allergies and children of everyone you care about. This page says exactly what happens to it. The legal detail is in the privacy policy; this is the plain-English version.
- Encrypted at rest
- Never marketed to
- Deleted on a clock
Is my guest list safe with Evorrah?
Your guest data is stored encrypted on Supabase (hosted on AWS in the US), protected by row-level security so one client's event can never read another's, and it is never used to market to your guests — not by us, and not by anyone we work with. It is deleted 12 months after your event date.
01
The one promise that matters.
You are handing a new company several hundred people's names, addresses and phone numbers. The reasonable fear is not that we will be hacked — it is that we will use them.
We do not. Guest details are processed for exactly one purpose: producing your guest list, your personalised pieces, your seating plan and your RSVP tracking. Your guests never receive marketing from Evorrah. They receive what you send them, from your event, and nothing else. We do not sell personal data, and we do not pass guest details to advertisers.
The only messages that ever reach a guest are the ones your event generates — an invitation, a reply link, a reminder you scheduled, a thank-you. Every one of them carries a one-click way out, and an opt-out is kept indefinitely, because forgetting one would mean contacting somebody who asked us not to.
Where each kind of data lives.
| What | Where it is held | Who can reach it |
|---|---|---|
| Guest names, addresses, dietary and access needs | Supabase — encrypted, on AWS in the US | You, in your portal. Your designer, to build the pieces. |
| Card details | Stripe only, under PCI-DSS | Nobody at Evorrah. We never see or store a full card number. |
| Email delivery | Resend | Passes the message through; does not keep your list. |
| Text messages | Twilio | Receives the number and the text in order to deliver it. |
| The site and the API | Vercel | Request metadata as part of normal hosting. |
| Your design brief | Supabase, and Anthropic when the house uses AI assistance on your brief | Your designer. |
02
How long we keep it — and the clock that deletes it.
Nothing is kept indefinitely because it is easier than deleting it. Each kind of data has a window, and it is enforced rather than intended.
Guest and RSVP data — 12 months after your event date, then deleted. Delivered design files — one year after your event, and we email you 30 days before so you can download them or ask us to extend. Client records and briefing data — three years from your last active project, then deleted or anonymised.
You can ask for your data earlier than any of those dates, and we will do it. Write to hello@evorrah.com.
The controls, named.
HTTPS everywhere
Every page and every API call, with no plaintext fallback.
Row Level Security
Enforced in the database itself, not in application code — one event cannot read another's guests even if a query is wrong.
Passwords hashed with scrypt
We cannot read your password. Nobody here can.
Payments never touch our servers
Stripe handles the card. We store a customer ID and whether it succeeded.
Rate limiting on every endpoint
So a guest list cannot be scraped by brute force.
Tokens rotate on password reset
A reset invalidates every existing session.
Reporting a vulnerability. Write to hello@evorrah.com with "security" in the subject line. We will confirm receipt within one business day, and we will not take action against anyone who reports a genuine issue in good faith.
The questions procurement asks.
Where is the data physically stored?
Will you sign a DPA?
Do you use our guest data to train AI?
Can I delete everything immediately after the event?
What happens to my data if Evorrah closes?
Still deciding?
Ask the house anything about how your guests' details are handled — a person replies within one business day.
Talk to the house