Privacy Policy

InviteMe is the data controller for account data. Insert the registered company name, company number, registered address and, where required, the EU representative and Data Protection Officer.

For guest replies, the invitation owner is the controller and this service acts as a processor on their behalf. That split needs to be reflected in your terms and in a data processing agreement.

Account data: your email address, your name if you provide it, and a hashed password or the identifier from the sign-in provider you chose.

Invitation data: everything you type into the wizard and the editor, plus any photographs you upload.

Guest replies: the name, attendance, party size and any dietary, allergy, menu or message fields your invitation asks for. Guests never create an account.

Technical data: standard server logs and, if analytics are enabled, aggregated page events.

Contract for account and invitation data, legitimate interest for security and abuse prevention, and consent for optional analytics and marketing email. Confirm each basis against your final configuration.

This deployment can use Supabase for database, authentication and file storage, Stripe for payments, Vercel for hosting, and AI providers for design and copy generation. List the processors you actually enable, their locations, and the transfer mechanism for anything outside the EEA.

Event details are sent to the AI provider to generate the design and the wording. Do not enter data you would not want processed by a third party.

Invitations and guest replies are kept while your account exists so you can return to them. Set your own retention period, particularly for guest replies after an event has passed.

Where the GDPR applies you may request access, correction, deletion, restriction, portability and object to processing. Guests should contact the invitation host first, since the host controls their reply.

To exercise a right against this service, email labas@inviteme.lt from the address on the account.

Data is stored with row level security so an account reaches only its own rows. Guest replies are write-only for the public and readable only by the invitation owner. Payment card details are handled entirely by Stripe and never reach this service.