1. Who we are
The data controller is PRETTY INVITES S.R.L. (“Pretty Invites”, “we”). For any question about your data, email hello@pretty-invites.com or use our personal data request form.
- Company name: PRETTY INVITES S.R.L.
- Registered office: Str. Grigore Ionescu nr. 90, bl. T8A, sc. A, ground floor, ap. 2, Sector 2, Bucharest, Romania
- Tax ID (CUI): 54463462
- Trade Register no.: J2026023943005
- EUID: ROONRC.J2026023943005
- Share capital: 500 RON
- VAT: Not registered for VAT in Romania (no VAT is charged)
- E-mail: hello@pretty-invites.com
2. In short
- Pretty Invites is a web app for digital invitations: hosts create the invitation, send each guest household a personal link, collect RSVPs and plan seating and budget.
- We use data only to run the service, take payment, send the emails you expect and, only with your consent, for analytics and marketing.
- We don't sell personal data. We don't use data received from Google for advertising or to train AI models.
- Data is mainly stored in the European Union (our database is in Ireland).
- Guest data and album photos are deleted automatically 90 days after the event; allergies, 7 days after the event.
3. What data we process and why
| Purpose | Data | Legal basis (GDPR art. 6) | How long |
|---|---|---|---|
| Your account | Name, email address, profile picture (if you sign in with Google), technical account identifiers. | Performance of a contract (b). | While you have an account; deleted within 30 days of asking us to close it. |
| Events and invitations | Event details (names, date, venues, schedule, your story), the texts and photos you upload, seating plan and budget. | Performance of a contract (b). | While you have an account or until you delete the event. |
| Guest list and RSVPs | Guest names, their household or group, phone and email (optional), their RSVP answer, each person's age group (adult, child or baby, never a date of birth), menu choices and other preferences the host asks for, their message, their table, the guest's photo (if added). | For the host: performance of a contract (b). Towards guests: the host's legitimate interest in organising their event (f). | While the host keeps the event in their account, and at most 90 days after the event date (see below). |
| Guest allergies | Allergies or dietary restrictions the guest writes for each person when replying, and when they gave consent. | The guest's explicit consent (Art. 9(2)(a) GDPR), given by ticking the box next to the field. | 7 days after the event date. |
| Event photo album | Photos uploaded by guests and, optionally, the name of whoever sent them. | The guest's consent (a), given by ticking the box before sending. | 90 days after the event date, unless the host deletes them sooner. |
| Payments | Name, email, amount, products bought, payment status and Stripe identifiers. We never see full card details. | Performance of a contract (b) and our legal duty to keep accounting records (c). | As long as accounting law requires (usually 5 to 10 years). |
| Service emails | Email address and message content: invitations sent by the host, RSVP confirmations, notifications, account and payment emails. | Performance of a contract (b). | While you have an account. |
| AI features | The photos, descriptions and texts you submit to generate the invitation design, texts, images or the invitation film (Invitație-film); if you import a guest list with AI, the text or image of that list. Requests go through the Vercel AI Gateway to Google's Gemini models (Vertex AI, then Google AI Studio) or, for the invitation film, ByteDance (Seedream, Seedance). | Performance of a contract (b). | Results stay in your account as long as you keep them. The AI providers don't use the data to train their models. The gateway keeps no prompts; the model providers may keep them for a limited period under their own terms (for example, for abuse monitoring). |
| Waitlist | Email address, language and the page you signed up from. | Consent (a). | Until you unsubscribe or ask us to delete it. |
| Personal data requests | Name, email, request type and message. | Legal obligation to respond (c). | 3 years after we reply, so we can show how the request was handled. |
| Proof of your cookie choice | A random identifier, your choice, the policy version, country, date and a salted cryptographic hash of your IP address, never the IP address itself. | Legal obligation to be able to demonstrate consent (c, GDPR art. 7(1)). | 3 years. |
| Security and abuse prevention | IP address and technical request data, used for rate limiting and in our hosting providers' technical logs. | Legitimate interest in protecting the service (f). | Rate-limit counters are deleted within a day; technical logs after the provider's set period (usually days to weeks). |
| Analytics and marketing | Pages visited, device, traffic source, cookie identifiers (Google Analytics, Meta Pixel and TikTok Pixel, via Google Tag Manager), and the fact that you created an account or started a payment. Vercel's statistics are anonymous and cookieless. | Consent (a) where the law requires it; otherwise legitimate interest (f), and you can opt out in “Cookie settings”. | Google Analytics cookies expire after at most 2 years; Meta's after 90 days; TikTok's after at most 13 months. |
Guest data
Hosts add their guests' names and, optionally, phone numbers or email addresses so they can send personal invitation links. The host decides which details to add and which questions the RSVP form asks; we process them to make the invitation work. Guests' RSVP answers (attendance, menu choices, accommodation or transport if asked, and their message) are visible only to the event's hosts and co-hosts. For each person the form only asks for an age group (adult, child or baby) so the venue can prepare the right portions; we never ask for a date of birth. Allergies are health data: we only accept them if the guest ticks the box agreeing that they are used only to prepare the meal, we record when they agreed, and we delete them automatically 7 days after the event. Consent can be withdrawn at any time by clearing the allergies from the same link or by writing to us. Please don't add other health or sensitive data. If you are a guest and want your data changed or deleted, you can ask the host, or us.
How long we keep guest data
90 days after the event date we automatically delete guests' personal data: names become “Invitat” (guest), and phone numbers, email addresses, notes, allergies, RSVP messages and the photos in the event album are deleted. We keep only figures without names (how many people came, how many menus) so the host can still look back at the event. 14 days before, the host gets an email so they can download the photos and lists. The host can delete the data sooner at any time.
Photos
Guest photos (a profile picture added by the host, or by the guest when replying) are stored so that anyone with the direct link to the image can open it; we don't publish them anywhere else. If the host turns on the event's photo album, guests can upload photos through the album link (or the QR code on the tables) or from their personal invitation, in which case the photo is credited to their household. Before sending, the guest agrees that the photos will be seen by the hosts and, depending on the album's settings, by guests who have the album link; without that consent the photo is not accepted. The host sees every photo and can hide or delete it; the others are visible to anyone with the album link. We remove location data and other metadata (EXIF) from photos before saving them. We don't use face recognition and don't analyse faces in photos automatically. Album photos are deleted 90 days after the event. For the invitation film, the photos the host picks are sent to the AI providers in section 5 to generate the film.
Sending on WhatsApp
When a host sends an invitation on WhatsApp, the app opens the host's own WhatsApp with the message already written (a wa.me link). The message is sent from the host's WhatsApp account; we don't send WhatsApp messages and receive no data from WhatsApp. WhatsApp (Meta) processes the message under its own terms.
4. Google user data (Sign in with Google)
You can create a Pretty Invites account with Sign in with Google. When you do, we request only the basic scopes openid, email and profile, and receive your name, email address and profile picture from Google.
- How we use it: only to create and sign you in to your account, show your name and picture in the app, and send you account and event emails you ask for (for example, receipts and RSVP notifications).
- What we don't do: we do not access your Gmail, contacts, calendar, Drive or any other Google data; we do not sell Google user data, use it for advertising, or use it to train AI models.
- Sharing: Google user data is shared only with the service providers listed in section 5 that operate the app on our behalf (for example, Supabase, which runs our authentication and database), and only as needed to provide the service.
- Storage and security: stored in our database in the EU region, encrypted in transit (TLS) and at rest, with access restricted to your account through row-level security.
- Retention and deletion: kept while your account exists. To delete your account and its data, use our data request form or email hello@pretty-invites.com from the address you signed in with; we delete it within 30 days. You can also revoke Pretty Invites' access at any time at myaccount.google.com/permissions.
Pretty Invites' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5. Who we share data with
We use these providers, who process data only on our behalf under data processing agreements:
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, file storage, authentication, the functions that send emails | EU (Ireland) |
| Vercel | Website hosting and anonymous traffic and speed statistics | Global (server network); US company |
| Stripe | Payments and refunds | EU and US |
| Vercel AI Gateway | Routing AI feature requests to the model providers below; keeps no prompts | Global (server network); US company |
| Google (via Vercel AI Gateway) | AI features: Gemini models, through Vertex AI and, as a fallback, Google AI Studio (generating the design, texts and images, guest-list import) | EU and US |
| ByteDance (via Vercel AI Gateway) | The invitation film: stills and clips generated with the Seedream and Seedance models | Outside the EU |
| Sign in with Google, maps and venue search (Google Maps Platform), analytics (Google Analytics, Google Tag Manager) | EU and US | |
| Sentry | Reporting the site's technical errors (no cookies; no account data, invitation content or IP address) | US |
| Our email (SMTP) provider | Email delivery | — |
Only with your marketing consent, Meta (Facebook, Instagram) and TikTok receive, through their pixels, the cookie identifiers and events above, so we can measure ads. For this collection we are joint controllers with them; what they do with the data afterwards is up to them, under their own privacy policies. The data may leave the EU.
For AI features, every request sent through the Vercel AI Gateway excludes providers that train their models on the data they receive, so no AI provider uses your data to train its models. The gateway itself keeps no prompts. We have not turned on zero data retention with the providers: Google and ByteDance may keep requests for a limited period under their own terms (for example, for abuse monitoring).
An event's hosts and co-hosts see the guest data for that event. We disclose data to authorities only when the law requires us to.
6. Transfers outside the EU
Some providers are US companies or may access data from outside the European Economic Area. Those transfers rely on the EU-US Data Privacy Framework adequacy decision, for certified companies, or on the European Commission's standard contractual clauses. For the invitation film, ByteDance processes data outside the EU, relying on the standard contractual clauses in our agreement with Vercel and in Vercel's terms with its sub-processors.
7. Your rights
You have the right to:
- know what data we hold about you and get a copy (access);
- have wrong data corrected (rectification);
- have your data deleted (erasure);
- restrict processing;
- receive your data in a structured format to take elsewhere (portability);
- object to processing based on legitimate interest;
- withdraw consent at any time, without affecting what happened before (for example in “Cookie settings” in the page footer).
We don't make decisions based solely on automated processing that have legal effects on you. To exercise your rights, use our data request form or email hello@pretty-invites.com. We reply within one month and may ask you to confirm the email address is yours.
You can also complain to the Romanian data protection authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal), B-dul G-ral. Gheorghe Magheru 28-30, sector 1, Bucharest, www.dataprotection.ro, or to the authority where you live.
8. Security
Data is encrypted in transit (HTTPS/TLS) and at rest. Access to an event's data is limited to its hosts through database security rules, and admin keys stay on our servers. If a personal data breach could affect you, we will tell you and ANSPDCP as the law requires.
9. Children
You can't create an account if you are under 16. Hosts may add children to their guest list (usually just a name), on their own responsibility.
10. Changes
We may update this policy. When changes are significant, we will let you know on the site or by email. Current version: 2026-10-14.1. See also our Cookie policy and Terms and conditions.