EventInvite processes only the data that is needed for invitations, replies, and the technical operation of the product. This page reflects the current product state in plain language.
Account and event data
Login, events, branding, and configuration
Guests and replies
Contact details, RSVP status, and sending context
Technical operations
Hosting, database, email, and optional notifications
For host accounts, EventInvite processes data such as email address, login data, sessions, and optional passkey information.
For events and invitations, EventInvite processes details such as event title, description, location, time, guest lists, message content, and guest replies.
The data is used to let hosts create events, send invitations, collect replies, and follow up with guests who have not answered yet.
Technical logs and delivery-related information may also be used to analyze errors, understand sending status, and keep the product running reliably.
Depending on the features in use, external services can be involved for hosting, database operations, authentication, email delivery, AI generation, SMS, and push notifications.
The current technical setup includes tools such as Vercel, Neon/PostgreSQL, NextAuth, Mailaura, and optional integrations like Anthropic, OpenAI, Twilio, and Web Push.
Event, guest, and reply data remains stored for as long as it is needed for the respective invitation flow or the operation of the host account.
The project already includes targeted cleanup for smoke-test data. Broader deletion and retention rules will be refined further alongside the next host-flow improvements.
If you have questions about stored data or the current privacy setup, please write to andreas@ostheimer.at.
Before a broader public rollout, this page will be extended with the complete legal wording and formal processes.
EventInvite
If you want to organize private invitations more easily, start directly with your next event.
