Terms and data
DRAFT — awaiting legal review
The facts on this page are accurate and read from the application itself. The wording has not yet been reviewed by a lawyer, so for now this is not a legally binding document.
What we keep about you and your venue
Your email address and name, the venue's name and settings, and the team you invite. We do not sell any of it and do not pass it to anyone except those listed below, who help the application run.
What we keep about the guests at your events
What the host and the guests enter in the portal themselves: the guest's name, whether they are a child and the child's age, whether they are coming, whether they need accommodation, and their dish choices. Allergies are kept only with the guest's explicit consent, only the kitchen can see them, and they are deleted the day after the event — that deletion is enforced by the database itself, not by our good intentions.
Where the data sits
Frankfurt, Germany (European Union)
Invitation images are kept in storage in the European Union.
Who else touches the data
Only these, and only for what is stated. Whoever adds another adds them to this list too.
Neon
- What it does
- Database
- Where the data sits
- Frankfurt, Germany (European Union)
- Which data
- All venue data
Resend
- What it does
- Sending email
- Where the data sits
- European Union / USA
- Which data
- Only the email address and the sign-in link
Cloudflare R2
- What it does
- Image storage
- Where the data sits
- European Union
- Which data
- Only the invitation image the host uploads
Anthropic
- What it does
- AI assistance
- Where the data sits
- United States
- Which data
- Only the text you send to the AI yourself: a client inquiry, a pasted e-mail, a guest list, or the list of changes to a work order. Never allergies. Active only while AI assistance is switched on.
Your rights
At any moment you can download all your data as a file and delete the venue or the account — no questions, no waiting. Both live in the app, under "Your data".
How the data is protected
- One venue's data is separated from every other venue in the database itself — not only by the application code.
- Who may do what is set out explicitly per role. Every page and every button checks it, and a check that none was left unguarded runs with every code change.
- Passwords are never stored, only their hash. Every sign-in is verified against the database, so revoked access takes effect immediately.
- Of the links for clients and guests, the database holds only a hash — not even we can read them. A new link invalidates the old one.
- Guest allergies are health data: they require explicit consent, only the kitchen can see them, and they are deleted the day after the event.
- A data export contains only the fields listed explicitly. Passwords and sign-in tokens never leave.
- Deleting a venue deletes all of its rows in the database and all of its images in storage, immediately and irreversibly.
Data processing agreement
If, as a venue, you process your clients' and guests' data through this app, this is the draft processing agreement.
Data processing agreement →Text version: 2026-10-25-2-nacrt