Make an invite

Legal

Privacy policy

Last updated 20 October 2026.

This privacy notice covers Inviteroo (formerly Gatheroo and RSVP Sorted): what we collect, why, who sees it, how long we keep it and your rights.

Inviteroo is run by its two founders, Louis and Steven. It decides how the information below is used, which makes it the controller under UK data protection law. For questions, requests about your information or complaints, email hello@rsvpsorted.com.

What we collect

  • Hosts: your email address or UK mobile number, and the party details you enter: the occasion, the title, the name of the person it’s for (and their age, for a birthday), any second name or occasion details such as a due date or a memorial’s years, the date, times, place and address, your note to guests and the name you show guests. When you save an invite, or first buy credits, we record that you confirmed you’re 18 or over, and when you save an invite, whether you’d like marketing emails. While you’re signed in we keep a record of the sign-in, with the IP address and browser it came from.
  • Songs and designs: if you make a song, the name as it should be sung, the words of the song and the music file; if you ask for a custom design, the description you write and the picture. For both, when you asked and the wording you agreed to.
  • The person the party is for: if you tell us about the person the party is for, we keep what you said with the invite, use it to make the song, designs and video, and delete it when you delete the invite.
  • Party videos: if you make a party video, the photos you add of the people in it, each person’s first name and whether they’re a child, what you ask the video to show, and the finished video. For each photo we keep a record of who agreed to it being used: that you ticked to confirm it, whether you are the person, their parent or guardian, or have their or their parent’s say-so, the exact words, when, and a fingerprint of the photo that can’t be turned back into it.
  • Payments: if you buy credits, what you bought, the price, when you paid, the wording you agreed to before paying, your credit balance and any refund. Card details go straight to Stripe, our payment provider, and never reach us.
  • Guests: the name, children’s names, answer, numbers, whether a grown-up is staying and the note you type when replying. Guests don’t make an account. Anything you write in the note is shared with the host, and only the host, so the note box asks you to leave out health or medical details.
  • Parties booked at a venue: when you tap Make your invites on a venue’s booking page, the venue sends us the first name and age of the person the party is for, the occasion, date, times, room, package, number of places and booking reference, your first name, and the email address and mobile number you booked with. We keep the email address and mobile number only in scrambled form (a hash) with a masked hint such as a***@example.com, to check it’s you who saves the invite.
  • Venue staff: the work email address and role of each person who uses a venue’s dashboard, and a record of their sign-ins as for hosts.
  • Venue enquiries: the name, venue, work email address, phone number, booking system, number of parties and message you send from our venues page. It comes to us as an email and isn’t stored anywhere else, and we email the address you gave to say it arrived.
  • Everyone: short-lived security records, keyed by a scrambled form of your IP address, to stop spam and abuse. Counts of steps such as “invite saved” or “reply sent”, stored against the invite but not against any person, and how many times an invite was opened, counting each visitor once a day by a scrambled form of their IP address and browser that changes every day. On our website we count which kind of page was opened and how often Make your invite is tapped, in the same way and without cookies; if your browser sends Global Privacy Control or Do Not Track, the website counts nothing. When someone taps a gift idea, we record which one, on which invite and when, but not who.

Why we use it

  • To make and run a host’s invites, songs and designs, take payment and send the emails or texts that go with them, such as sign-in codes, reminders and receipts (contract with the host).
  • To show a host the replies to their invite, including the names of guests and children, and to let a guest change their reply (legitimate interests: the host’s and the guest’s in organising the party).
  • To put the name and age of the person the party is for on the invite and in a song (legitimate interests: the host’s in making the invite they asked for).
  • To make a party video from the photos a host adds, with their invite’s song, for the people in it whose agreement the host confirms they have (contract with the host; for the people in the photos, legitimate interests: the host’s in making the video they asked for, on that agreement).
  • To keep a record of that agreement and to deal with reports about a video (legitimate interests, and to show we acted lawfully).
  • To start an invite from a venue booking when you ask us to, and to check the booker is the one who saves it (steps you asked for before making an invite with us).
  • To keep the service safe from spam, fraud and abuse, and to deal with reports about invites (legitimate interests).
  • To see where people get stuck making or answering invites, and to show venues how many invites, replies and gift idea taps their parties produce, from counts that name nobody (legitimate interests).
  • To answer venue enquiries and support emails (legitimate interests).
  • To send hosts occasional party ideas and offers by email, only if they opted in (consent, which you can withdraw at any time).
  • To keep sales records for tax and to answer requests about your information (legal obligation).

Who sees it

Anyone the host gives the invite link to can see the invite, including the place and address, so only share it with people you’d invite. Only the host sees guests’ names, children’s names and notes; guests never see each other’s names, only how many are coming. If a party was booked at a venue, the venue’s staff see the invite’s title, date, times and status, the name the host shows guests, the number of places and how many have replied, but never guests’ names, notes or replies. We never sell your information, and the shops behind gift ideas never receive your name or your reply.

These providers handle information for us, only on our instructions, under contracts that require them to protect it:

  • Vercel, for hosting and file storage. Our servers run in London; Vercel is a US company and may handle data in the United States.
  • Neon, for our database, which is kept in London. Neon’s parent company, Databricks, is in the United States.
  • Resend, for emails. Resend stores email records in the United States.
  • Stripe, for payments, when you buy credits, in the United States and elsewhere.
  • Twilio, for sign-in codes by text, when you sign in with your phone, in the United States.
  • MusicGPT, for making personalised songs, when you make one. It receives the words of the song, including the name and age, and keeps the finished song on its servers for up to 90 days; we keep our own copy.
  • Anthropic, for writing the words of each song with its Claude language model, when you make one. It receives what we know about the party, including the name as it should be sung and the age, and any notes you add for the song, in the United States.
  • Anthropic, for writing the scene of each party video with Claude, from what the host asks the video to show and what we know about the party (never anyone’s name), in the United States.
  • Anthropic, for reading what you tell us when you make an invite by chatting, and what you tell us about the person it’s for, with Claude, to pick out the party’s details and suggest first ideas for the song, designs and video, in the United States. If you talk instead of typing, your own browser turns your speech into words: we receive only the words, never the sound.
  • fal.ai, for listening to each finished song with OpenAI’s Whisper model, run on fal’s own servers in the United States, to check it was sung before you get it. We ask fal not to keep the request.
  • fal.ai, for making party videos when a host makes one: with Kling 3.0, a model run by Kuaishou, when the host adds photos, after redrawing each photo as an animated-style portrait with Google’s Nano Banana image model; or with Wan 3.0, a model run by Alibaba, when the host adds no photos and describes everyone in words instead. fal also checks the photos and the finished video for anything unsuitable. It receives any photos and the description of the video (never anyone’s name), in the United States, and Kling handles photos in Singapore. We ask fal not to keep the request and to delete the finished video from its servers within an hour; we keep our own copy, and delete the photos and the portraits made from them as soon as the video is made.
  • fal.ai, for drawing custom designs with Recraft’s V4.1 model, when you ask for one. It receives your description and the invite’s occasion and colours, in the United States. We never add anyone’s name ourselves, though your description may contain one if you write it in. We ask fal not to keep the request and to delete the finished design from its servers within an hour; we keep our own copy of the design until the invite is deleted.
  • OpenAI, once we switch it on, will take over from fal checking that each finished song was sung (with its Whisper model), checking party video photos and stills, redrawing photos as portraits and drawing custom designs (with its GPT Image model), in the United States. OpenAI doesn’t train its models on what we send and keeps nothing from the checks; it keeps a portrait or design request, a photo included, for up to 30 days to check for abuse before deleting it.
  • Kling AI, run by Kuaishou, once we switch it on, will take over from fal making party videos, with its Kling 3.0 model on its own servers in Singapore. It will receive any photos, the portraits made from them and the description of the video (never anyone’s name), and keeps the finished video for up to 30 days before deleting it; we keep our own copy.
  • Sentry, for error reports, with names, email addresses and other personal details removed before they’re sent, in Germany.

Where a provider handles information outside the UK, it is protected by the UK’s data bridge with the United States (for providers certified to it) or by the UK’s standard data protection clauses in our contract with the provider. Email us for a copy of the safeguard that applies.

Personalised songs, custom designs and party videos are made by AI tools at our providers, from the words and photos we send them. Our design providers don’t use what we send them to train their models. Our music provider, MusicGPT, says it may use what it is sent, made anonymous, to improve its models. We never send any of them anything about guests.

Other organisations

  • Stripe and Twilio: also use payment and phone details for their own fraud prevention and legal duties, under their own privacy notices.
  • Gift ideas: if you tap one, your browser goes to the shop or, if you agree to its cookies first, to Awin, the network that runs many shop links and shares responsibility with us for tracking that tap. They can see the visit and may set their own cookies, under their own privacy notices. We tell them nothing about you or your reply.
  • Messaging apps and maps: when a host shares an invite in an app such as WhatsApp, the app fetches the invite’s preview picture and may keep its own copy, and a map link opens the address in Google Maps.
  • Venues: a venue that hands a booking over to us is responsible for what it sends, under its own privacy notice, and for what it does with the counts it sees.

How long we keep it

  • Invites, replies and everything attached to them, songs, designs and party videos included, are deleted 90 days after the party. Unsaved drafts are deleted after 7 days. A draft your venue started from your booking is kept like any invite, until 90 days after the party.
  • Photos added for a party video are deleted as soon as the video is made or can’t be, and always within a day. The record of who agreed to each photo is kept for two years, so we can answer a complaint about a video that was shared.
  • Your account stays until you delete it from your account page, which deletes your invites, replies, songs, designs and credits straight away. A reply stays until the invite is deleted, unless the guest erases it sooner from its link.
  • Sign-in records, with their IP address and browser, are deleted when you sign out, or once you haven’t used the app for 30 days.
  • Our log of the emails we’ve sent each address, which holds a scrambled form of the address and the invite or order it was about, is deleted after 180 days. Venues’ booking handovers are logged for 30 days.
  • Security records are deleted within two days. Daily visitor counts are deleted within three days. Step counts are deleted after 13 months, and records of gift idea taps after 13 months.
  • Our record of what our staff did with your information, such as a refund or a takedown, is deleted after 2 years.
  • Sales records are kept for 6 years after the end of the financial year of the sale, for tax, without any link to your account once you delete it.
  • Venue enquiries and support emails are kept for two years after we last hear from you.
  • Deleted information can stay in our database provider’s backups and our hosting provider’s logs for up to 30 days before it’s gone. An invite’s link preview picture can stay in our hosting provider’s cache for up to 24 hours after the invite changes or is deleted.

Children

Hosts must be 18 or over, and guests who reply are usually parents. For a child’s party we ask only for the child’s first name and, for a birthday, their age, so they can go on the invite. If a host adds a song, the name and age are sung in it and sent to our music provider to make it, and the host must confirm they are the child’s parent or guardian. A child is only in a party video if the host confirms they are the child’s parent or guardian or have their parent’s or guardian’s say-so; the photo is used only to make that video and deleted straight after, the video is private to the host unless they share a link to it, and anyone in it, or their parent, can report it from that link and we hide it while we check. The age is also used, on our own server, to suggest age-appropriate gift ideas to guests after they reply. We don’t use children’s information for marketing or to build profiles, and we don’t ask children to sign up.

Your rights

You can ask us for a copy of your information, to correct it, to delete it, to limit how we use it, to have it in a format you can take elsewhere, or to object to how we use it, and you can withdraw any consent you’ve given at any time. Some of these you can do yourself, straight away: a host can download everything we hold about their account as one file, or delete the account, from their account page, and stop marketing emails with the link in any of them; a guest can change or erase their reply from the link to it they got when they replied. For anything else, email us and we’ll answer within a month. If you’re unhappy with how we’ve handled your information, please tell us first so we can put it right; you can also complain to the Information Commission, the UK regulator, at ico.org.uk.

If we change this notice, we’ll update the date at the top, and tell hosts by email before a change that affects them.