Skip to main content

Privacy notice

Version 2026-11-draft · last updated

This is a draft. FreeRSVP isn't open to real events yet.

FreeRSVP (freersvp.app) lets a host create an invitation, share one link, and collect replies. This notice explains what personal data FreeRSVP handles, why, who else touches it, how long we keep it, and what you can do about it. It covers everyone: hosts, guests, and people a host lists as expected guests.

The short version:

1. Who is responsible for your data

The data controller is [to be added before launch: legal entity name], [to be added before launch: address], [to be added before launch: country]. "We" and "us" in this notice mean them.

For privacy questions or to use your rights, write to [to be added before launch: privacy email]. We don't have a data protection officer; we aren't required to have one.

When a private person uses FreeRSVP to invite friends and family, the data protection rules generally don't apply to that person (GDPR Recital 18). They do apply to us, because we provide the service, so we take responsibility for how FreeRSVP handles everyone's data.

2. What we collect and why

If you host an event
WhatWhyLegal basis
Your name and email addressTo send your 6-digit code and private manage link, to email you about new replies (you can switch these off), and to show guests who invited them ("Only Freja sees your reply").Contract: providing the service you asked for (GDPR Art. 6(1)(b))
Event details: title, date, time, time zone, place, reply-by date, your message, your settingsTo show the invitation to your guests. The place may be your home address: guests with the link can see it.Contract (Art. 6(1)(b))
Cover photo (optional)Shown on the invitation and in link previews. We re-save it, which removes hidden data such as GPS location. Anyone with the link can see it, so only use a photo everyone in it is happy to share.Contract (Art. 6(1)(b))
Replies you add by hand (name, answer, number of people, food note, note)To keep your headcount complete, e.g. for a guest who phoned you.Contract (Art. 6(1)(b))
Your guest list, if you add one: names and optional phone numbersTo show you who hasn't replied and to build a WhatsApp or SMS link that you send from your own phone. We never message the people on the list.Contract (Art. 6(1)(b)) for you; legitimate interest (Art. 6(1)(f)) for the people on the list, see section 4
If you reply as a guest
WhatWhyLegal basis
Your name, your answer (Yes, No, or Maybe if the host allows it), how many of youSo the host knows who is coming.Legitimate interest (Art. 6(1)(f)): yours and the host's interest in the reply you chose to send
Your note to the host (optional)Delivered to the host on their page.Legitimate interest (Art. 6(1)(f))
Food and allergy answers (optional)So the host can plan the food. See section 3.Your explicit consent (Art. 9(2)(a))
Your email addressOnly so you can change your answer later from another device: we email you a 6-digit code. It also stops someone else from overwriting your reply. We store only a scrambled fingerprint of it (a keyed hash), which can't be turned back into your address and works for this one event only. Your readable address is used only at the moment we send you a code (unless you ask for change emails, see the next row).Legitimate interest (Art. 6(1)(f)): letting you, and only you, change your reply
Your email address, if you tick 'Email me if the date, time or place changes'To email you if the host changes the date, time or place (at most one email an hour), with a link to your reply. We store it encrypted; only our server can read it, and only to send these emails. We delete it when you untick the box, change your answer from Yes, remove your reply, or 90 days after the event.Your consent (Art. 6(1)(a)). You can withdraw it at any time by unticking the box.
Whether your reply came after the reply-by date, and your previous answer if you changed itShown to the host ("Late", "was Coming").Legitimate interest (Art. 6(1)(f))
Everyone who visits
WhatWhyLegal basis
Your IP addressOur hosting provider needs it to deliver pages. To stop abuse we keep a scrambled fingerprint of it, never the address itself, for at most 24 hours.Legitimate interest (Art. 6(1)(f)): security and preventing spam
Small files in your browser (cookies and local storage)See section 9.Strictly necessary for the service

We don't use analytics, advertising or tracking tools, and we make no automated decisions about you, including profiling (GDPR Art. 22).

3. Food and allergy answers

Allergies and some diets can say something about your health, which the law treats as a special category of data (GDPR Art. 9). So:

If you write food needs for someone else in your party (for example "Nut allergy: Sofie"), please only do so if they, or their parent for a child, are fine with the host knowing.

4. People on a host's guest list

A host may paste a list of people they invited, with optional phone numbers, so they can see who hasn't replied yet. We didn't get these details from you, so here is what you should know (GDPR Art. 14): the source is the host; we store your name and, if the host added it, your phone number; we use them only to show the host who hasn't replied and to build a WhatsApp or SMS link the host taps on their own phone. We never contact you. Nobody else sees the list: guests never see who else is invited. It is deleted with the event, or when the host edits the list. Our legal basis is legitimate interest (Art. 6(1)(f)): the host's interest in organising their own event, which affects you very little. You can object or ask for deletion at [to be added before launch: privacy email]; because we can't search by name across events, tell us the invitation link.

If the host uploads a file, it is read on their device. Only the names, and phone numbers if the host chooses them, are sent to FreeRSVP; the file itself is not.

5. Who can see what

6. Emails we send

We send only these service emails, through our email provider Brevo:

We never send invitations, reminders, newsletters or advertising, and our emails contain no promotion of FreeRSVP. The "Made with FreeRSVP" line appears only on our web pages. Our emails contain no tracking pixels or tracked links.

7. Service providers and where your data is

We use these providers (data processors). Each has signed a data processing agreement with us and may only use the data to provide its service to us.

Service providers
ProviderWhat it doesWhere
Supabase Inc. (USA)DatabaseData stored in the EU: Ireland (eu-west-1).
Vercel Inc. (USA)Hosting: runs the websiteOur server code runs in Dublin, Ireland. Like any website, pages pass through Vercel's worldwide network to reach you.
Brevo (Sendinblue SAS, France)Sends the emails in section 6EU. Brevo keeps a log of each email (address, subject, delivery status) for the shortest period it offers, and we've switched off copies of email contents.

Supabase and Vercel are US companies. Where they or their sub-processors can access data from outside the EU/EEA, the transfer is protected by the EU Standard Contractual Clauses in their agreements and, where the company is certified, the EU-U.S. Data Privacy Framework (GDPR Art. 45–46). You can ask us for a copy of these safeguards.

If you tap "Open map" on an invitation, Google Maps opens with the place's address. That is Google's service under Google's privacy terms; we don't send Google anything until you tap.

8. How long we keep it

How long we keep it
DataDeleted
An event and everything about it: replies, food answers, notes, email fingerprints, guest list, phone numbers, cover photo, the host's name and email90 days after the event's start time, by a daily automatic job (it may run up to a day late). Sooner if the host deletes the event (see section 10).
An event whose host never entered the code24 hours after it was created
A replywhen the guest or the host removes it, at once; otherwise with the event
6-digit codesthey stop working after 10 minutes or 5 wrong tries, and are erased within a day
Links in reply-alert emailsstop working after 30 days
Scrambled IP and email fingerprints used against abusewithin 24 hours
BackupsWe don't keep backups of the database, so deleted data is gone at once.
Brevo's email logssee section 7

If you are a host, download your replies (CSV) before the data is deleted if you want to keep them. Your download is your own copy: you are responsible for it.

9. Cookies and browser storage

We use no tracking, analytics or advertising cookies, so we don't ask for cookie consent. We use only what the service needs (strictly necessary):

Cookies and browser storage
NameTypeWhat it doesHow long
__Host-yvh-<event code>cookie, HttpOnly, Secure, SameSite=LaxKeeps a host signed in to manage their event on this device. Holds a random key, nothing about you.until the event's deletion date, at most 400 days
__Host-yvg-<event code>cookie, HttpOnly, Secure, SameSite=LaxLets a guest see and change their own reply on this device without a code. Holds a random key, nothing about you.until the event's deletion date, at most 400 days; removed if you remove your reply
Create-form draftlocal storage, on your device onlyKeeps a half-finished event form if you close the page. Never sent to us until you press Create. Cleared when the event is created.until cleared
freersvp:draft:<event code>session storage, on your device onlyKeeps your answers while you step through a reply. Cleared when you send, and when you close the tab.the browser tab

A calendar file you download from a reply contains a private link to your reply. Anyone who gets the file can change your reply, so don't share it.

10. Your rights

You have the right to access, correct and delete your data, to restrict or object to how we use it, to data portability, and to withdraw consent at any time (GDPR Art. 15–21). Many of these you can do yourself:

Because we store guest emails as a fingerprint (and, for guests who asked for change emails, encrypted for that one event only), we can't look you up by email across events, and we can't send you a list of every event you replied to.

You can object at any time to processing based on legitimate interest (Art. 21). For a reply, the simplest way is to remove it.

You can complain to a data protection authority. In Denmark that is Datatilsynet (datatilsynet.dk) [OWNER: change if the controller is not in Denmark]; you can also complain in the EU country where you live or work.

11. Children

Hosts must be 18 or older. FreeRSVP is not meant for children under 13, and we don't knowingly collect data from them: if you are under 13, ask a parent or guardian to reply for you, including any food or allergy answers. Hosts may not add phone numbers of anyone under 18 to a guest list (see the Terms). If you think a child under 13 has replied on their own, write to us and we'll delete the reply.

12. Security, and changes to this notice

Everything travels over encrypted connections (HTTPS). The browser never talks to the database directly. Codes, private links and guest emails are stored only as one-way fingerprints; the address of a guest who asks for change emails is stored encrypted, with the key kept outside the database. Only the people running FreeRSVP have access to the systems, and our logs never contain names, emails or codes.

If we change this notice, we'll publish the new version here with a new date. If the change matters for hosts with events already running, we'll tell them by email; that email will be a service message, not marketing.

See also: Terms

FreeRSVP

Free RSVPs for private events. No ads, no app, no account.