1. Data controller and contact
The controller of personal data in tuned is Zdzisław Bela. For anything about your data, write to host@tunedparty.com. This address is also the point of contact for users and authorities (Art. 11 and 12 of the Digital Services Act, DSA); we answer in Polish and English.
Polls by companies and organisations. When a company or organisation creates a poll, it is the controller of the answers to it and decides what it asks and who sees the results. We store and process those answers on its behalf (as a processor, Art. 28 GDPR). About such a poll you can write to its author or to us. We will pass your request on.
An optician’s glasses try-on. The camera image stays on your phone. When you send the optician “I want these glasses”, we pass on your name, phone or e-mail, notes and the frame you picked. The optician is the controller of that request; we store it on their behalf (Art. 28 GDPR).
Waiting lists. When you join a company’s waiting list for a product (for example a small food maker’s), that company is the controller of your email and your place in the queue. We store them and send the queue emails on its behalf (Art. 28 GDPR). About a waiting list you can write to the company or to us. We will pass your request on. How we process data on the company’s behalf is set out in the data processing agreement.
Event sign-ups. When you sign up for a company’s event (for example a workshop), that company (the organizer) is the controller of your sign-up data. We store it and send the sign-up emails on its behalf (Art. 28 GDPR). Only the company organizes the event and is a party to the contract to take part; we do not take payments for events. About a sign-up you can write to the company or to us. We will pass your request on.
2. What data, why, and on what legal basis
Playing without an account. The name you enter is saved in your browser and shown to the other people in the room; on the server it is kept only for about 2 hours in the list of people in the room (see “Who is in the room”). Answers during the game travel between your devices; what we save from them is described below and in section 3. Legal basis: performance of the service contract (Art. 6(1)(b) GDPR).
Account. Email address: to sign in with a one-time code and identify the account. We send the code through an email provider (Resend). If you choose “Continue with Google”, Google gives us your email address and confirms the sign-in; for this the sign-in page loads Google’s button, which works under Google’s own rules. When you send the code, Cloudflare Turnstile checks that a person, not a script, fills in the form (IP address and browser data, no cookies). Legal basis: performance of the contract (Art. 6(1)(b) GDPR) and, for the Turnstile check, our legitimate interest in preventing abuse (Art. 6(1)(f) GDPR).
Game history (account only). We save a round only when you tap “Save” on the result screen. We save: the date, mode, topic or problem description, questions, your answers, the score and AI comments, and the other person’s name and answers, only with their consent (see section 4). Only you see your history. Legal basis: performance of the contract (Art. 6(1)(b) GDPR).
AI host. In AI modes, player names, the topic, questions and answers are sent to the AI model provider (Anthropic) to generate questions, comments and, in “Solve a problem”, a conclusion. There we also send the problem description you type. It may contain private matters. Don’t include health data or data about other people unless you need to. To pick the next question we use a second model (TypeSafe AI), which gets the candidate questions and answers; before that we replace player names in them with made-up ones and cut out e-mail addresses and phone numbers. Legal basis: performance of the contract (Art. 6(1)(b) GDPR) and, for answers about feelings, relationships and health, your consent (section 3).
Game records. If you agree to it (a separate, optional box in the consent window, section 3), we save how games went: questions, chosen answers, AI comments, the AI’s conclusion in “Solve a problem”, the conversation topic and how the round ended. We save a round only when everyone in the room agreed; otherwise we save nothing from it, and the game works just the same. Before saving, player names are replaced with the markers {A}, {B}, and the text goes through an AI model (Anthropic) that removes other people’s names, company names, places and health data. We don’t save the account, room code, IP address or exact time, just the day. With a round’s end we also save a host key: a random code from the host’s device mixed with the month, new every month, so many rounds by one person count as one in the room order. This is pseudonymisation, not full anonymisation: the automated step can miss something, so we treat these records as personal data and delete them after 24 months. The records are used to develop and analyse the service. Legal basis: your consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR), which you can withdraw (section 8).
Improving the host. From rounds that everyone in the room agreed to save, we also save AI comments without player names (replaced with the markers {A}, {B}), together with the question, the chosen answers, the mode and language, and the number of emoji reactions. Names are replaced automatically, so an inflected form of a name may sometimes stay. We don’t save the room code, topic, account or IP address. The administrator reads the comments and approves as examples for the host only those with no names or other details about people. We keep the approved examples with no time limit and delete the other comments after 24 months. Legal basis: your consent to round saving (Art. 6(1)(a) and Art. 9(2)(a) GDPR).
Question log. We record which questions were played in rooms: the mode, language, time, the question’s source and how many times someone tapped “Weak question” or starred it as the round’s best question. Player names are replaced with {A}, {B}; we don’t record answers, comments, the account, the room code or the IP address. We record the text of a question written live by the AI only when everyone in the room agreed to save rounds. Otherwise only the mode, time and ratings stay. The administrator reads the log to fix weak questions. We keep it for 90 days. Legal basis: legitimate interest in improving the game (Art. 6(1)(f) GDPR), and for the text of AI questions, your consent to saving rounds.
Room ratings. After a round you can rate the room with 1 to 5 stars. We save the room, the number of stars, the language and the time; no name, account, room code or IP address. The room list uses only the totals, which set its order. Basis: legitimate interest in improving the game (Art. 6(1)(f) GDPR).
AI costs. For every AI call in a game we save the model, number of tokens, cost, mode and time and, if the round’s host is signed in, their account. No conversation content is saved here, and cost records are not linked to game records. They are used to control the cost of the service. We keep them for 24 months; after an account is deleted only the numbers stay until then, without a link to it. Legal basis: legitimate interest (Art. 6(1)(f) GDPR).
Usage counters. We count anonymously how many rooms are opened in each mode and how many times someone clicks “Ask for branding” on the page for companies. We also count first visits to the game and returning visits, and how far a first visit got (a room opened, a round started, a round played to the end, or left without opening a room), as daily totals. We also count how many browser tabs saw each game screen (start, room choice, lobby, game, result) and how many of them went on to a later screen. We also count every round played: the room, the number of players, whether it reached the end or was left early, and roughly how long it took (up to 5, 15, 30 or over 30 minutes). We also count problems: a failed attempt to join a room, a page crash (only which part of the service it was, no error details) and a turn where the AI failed. To tell a first visit from a return, the browser keeps a single “already been here” mark (tuned:seen), no identifier and nothing about you. We save only the kind of event, the mode and the day, no account, IP address, file or time. The IP address goes for at most 2 days into a separate counter that stops anyone pumping the numbers, and is never linked to the counters. The numbers show at which step people give up, so we can improve the service. Legal basis: legitimate interest (Art. 6(1)(f) GDPR). The counters are not about any particular person, so we keep them without a time limit.
Room map. When the host opens a room, our server reads an approximate place from the connection: the town and a point rounded to about 10 km, which the hosting provider (Vercel) works out from the IP address. We don’t store the IP address itself. The record holds only the room’s random key, that place and the number of players (no account, names or game content) and is deleted after 2 hours. Only the administrator sees it, to know where the service is used and how busy it is. Legal basis: legitimate interest (Art. 6(1)(f) GDPR).
Maps in polls. The building map in the poll editor and the “Fly over the estate” opening of a poll are drawn from OpenFreeMap tiles (OpenStreetMap data): the browser downloads them straight from their server, which sees your IP address, as any site you download something from does. We send them nothing about you or the poll. With data saving on, the flight shows only the building outlines, without the map. Legal basis: legitimate interest in showing the map (Art. 6(1)(f) GDPR).
Map questions in polls. The map loads only at that question, from the same OpenFreeMap tiles: their server sees your IP address and which part of the map you view. When you search for a place, the name you type and the map’s centre go from your browser to the Photon service (komoot), which also sees your IP address. We do not ask your browser for your location. We save the marked point to about 1 km, never exact. The poll’s author sees dots grouped into larger cells, only when a cell holds at least as many people as the poll’s anonymity threshold, and a cell about 5 km across in the answers file. Legal basis: legitimate interest in asking about a place (Art. 6(1)(f) GDPR).
Opening video of a poll. A company can upload a short clip that guests see without sound at the start of a poll. We keep the file and its first frame in Supabase file storage at a random address until the company changes or removes it; guests download it from there. The company is responsible for what the clip shows.
AI voice. If you turn on reading aloud, the MC’s lines are read by a voice generated by ElevenLabs. These are fixed texts of the game, with no data about players. Everything else is read by the voice built into your browser or phone; some browsers use their provider’s online voices for this. When you turn on “Natural voice” in settings, ElevenLabs also reads questions from the ready-made pool and the radio host’s lines, and on a signed-in account also comments and questions written by AI. These may contain player names; we keep those recordings for 30 days so we don’t generate them again. Legal basis: performance of the contract (Art. 6(1)(b) GDPR).
A song dedication. When you dedicate a radio song to someone, we store with your account the recipients’ first names (up to six) and your words before and after the song. Songs written for specific people are kept in private storage and play only through the gift link. We delete this data together with your account. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Dictation and microphone. When you type by voice, speech recognition is done by your browser: in Chrome the recording goes to Google, in Safari to Apple (or stays on the device), under those companies’ rules. We only get the finished text. In the “Truth or lie?” room the sound never leaves the phone: only the recognised words and numbers describing loudness and pitch go to the game. The microphone turns on only after you allow it in the browser. Legal basis: performance of the contract (Art. 6(1)(b) GDPR).
Pick-up lines. For signed-in players we save only numbers for each round: how many answers, how many hits and the sum of scores, to show stats in the account menu. We don’t save the chosen lines or other players. Only you see them; they go with the account. Choices in this room are also counted in total, without a link to anyone. Legal basis: performance of the contract (Art. 6(1)(b) GDPR).
Polls. To answer a poll you don’t need an account or an email address. To count one vote per person, your browser gets a random identifier in the poll_pid cookie (valid for a year). If you are signed in, we use an identifier linked to your account instead, so your vote counts once on every device. We save the answers, including text answers, and when they were given. If the poll link has a tag (e.g. a batch or a desk), we save it with the vote; we link one person’s votes under different tags only so that the threshold counts people, not tags. The author never sees this link. If the poll has a “Leave a review” button, we count how many people saw and tapped it: one entry per person, with no identifier, time or link to the answers. The poll’s author sees the results in total and the text answers, but only from the threshold the author picks (a number of answers; the author can also turn the threshold off); depending on the settings, participants may see the results too. At the author’s request, AI (Anthropic) writes a summary of the answers. When a poll is published, AI (Anthropic and TypeSafe AI) forecasts the results of its choice questions for the author: it gets the questions and their options, the poll’s goal and the author’s kind of business, never the participants’ answers. Please don’t enter health details in polls, the AI is told never to suggest questions about health or other special-category data (Art. 9 GDPR) and never to repeat such data in a summary. We delete answers automatically after the period the author picks: 30, 90 or 180 days, or with the author’s confirmation 1, 2 or 5 years. Our own polls (e.g. about the game) have no such period: we delete them by hand. We limit the number of votes from one IP address in the server’s memory. Legal basis: for company polls the contract with the author, who is the controller (section 1); for our polls legitimate interest (Art. 6(1)(f) GDPR). If a poll asks for a photo, adding one is optional. We keep the photo in private storage, without the camera’s data (EXIF, GPS location): we redraw it from its pixels only. Only the poll’s author sees it, in the results, through an address valid for 15 minutes; it isn’t in public results, on the projector, in exports or in the AI summary. A photo may show people: add only one you may show the author. We delete it with the answers (same period as above), and one that was never sent after a day.
Waiting lists. When you join a waiting list for a product, you give your email (your name is optional). We also store when you joined, confirmed the address, got offers and bought, and how many offers you missed, because your place depends on them. We send a confirmation link to that address and, when your turn comes, a link to the product in the company’s shop and a code. The company sees the list of people waiting with their emails and can download it. Every queue email has a one-click link to leave. We do not store what you buy in the company’s shop. Legal basis: the consent you give when you join (Art. 6(1)(a) GDPR), which you withdraw by leaving the queue; the company is the controller (section 1).
Event sign-ups. When you sign up for an event, you give your full name, email and phone and choose a slot or option. We also store when you signed up and confirmed the address, and the organizer’s terms you accepted. We send a confirmation link to that address and, once confirmed, a “You have a place” email with the organizer’s note (e.g. how to pay). The organizer sees the list of sign-ups with their data, can download it, mark a payment and remove a sign-up. Every email has a link to cancel: the sign-up is deleted at once. We do not store your IP address with the sign-up. Legal basis: the contract with the organizer to take part in the event (Art. 6(1)(b) GDPR); the company is the controller (section 1).
News about next events. When you sign up you can tick that you want news from the company about its next events (the box is empty by default). We keep this only after you confirm your address with the link in the email: your name, email, language, and when and at which event you agreed. We keep it until you unsubscribe. Every such email has an “Unsubscribe” link that deletes the entry at once. Legal basis: your consent (Art. 6(1)(a) GDPR), which you withdraw by unsubscribing; the company is the controller (section 1).
Events by several companies. The organizer can add co-hosts to an event: the company’s name, logo and an email to which we send its result after the event. The name and logo show on the sign-up page; we do not show the address to guests. When you sign up from the link of one of these companies, we store with the sign-up which company you came from (the first link you opened on this device counts). A co-host gets only numbers: how many people signed up from its link and how many of them came to the organizer for the first time, without names or addresses. A co-host’s data goes when the organizer removes it or deletes the event. Legal basis: the contract to take part in the event (Art. 6(1)(b) GDPR) and the organizer’s legitimate interest in settling a shared event (Art. 6(1)(f) GDPR); the organizer is the controller (section 1).
Schedule. A schedule is sign-ups for one-person slots (e.g. a massage at the office). To take a slot you give only your first name (if you are signed in, we take it from your Tuned account) and pick a time. Anyone with the schedule’s link sees the name next to the time, and so do the company and the provider; the sign-up screen says so under the name field. The provider (e.g. a massage therapist from outside) gets their own link from the company, without an account: they see the schedule with names and can free or move any slot. We recognise your slots by a random key in your browser; the database keeps only its hash, or your account ID when you are signed in. While you view the schedule, other viewers see your initials and the time you are looking at; we do not store this. A freed slot is deleted at once, and all of a schedule’s sign-ups 7 days after its last slot (or after 30 days if the company sets it so). We do not store your IP address with the sign-up. Legal basis: the legitimate interest of the company organising the service for its people (Art. 6(1)(f) GDPR); the company is the controller (section 1).
Contact in a poll. If the author allows it, after the last question you can leave an email or phone number and tick consent to be contacted. We store the contact separately from the answers, without the participant identifier, and delete it after the poll’s period or with the poll. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw by writing to the author or to us.
Live help in a poll. When you click “Help” on a poll screen, you get a code, and the person from Tuned you give it to sees your screen for a while: where you are, the questions and the buttons. They do not see your answers: fields, answer options and what you pick are covered, and so are e-mail addresses and phone numbers. Beside it they see this tab’s recent errors and failed requests, without address parameters. Help ends when you press “Stop”, when you close the tab, and after 15 minutes at the latest. The picture of your screen goes live through Supabase Realtime and we store it nowhere; for that time we keep only the code and the poll’s number, and the limit on tries counts your IP address. We are the controller of this data, also in a company’s poll, and the company gets none of it. Legal basis: your consent (Art. 6(1)(a) GDPR), which you withdraw with “Stop”. Polls of accounts with health data do not have this feature.
Event view. While a person from Tuned has a poll’s event view open, your phone sends this once a minute and nothing more: which step you are on and whether nothing has changed for 3 minutes. No answers, no identifier and no cookies, so phones cannot be told apart. We store none of it, and the hosting provider sees this call like any other, with the IP address. If you click “Help”, from then until it ends this tab’s recent errors go there too, without address parameters, e-mail addresses and phone numbers. Legal basis: our legitimate interest in the poll working during the event (Art. 6(1)(f) GDPR), and your consent for the errors after you click “Help”. Polls of accounts with health data do not have this feature.
Contact on the page for companies. Under the film on /brand you can leave an email or phone number and one line, so we can get back to you. We get them by email and keep them on a client list only the administrator sees. We use them only for this conversation and delete them at your request or when the conversation ends. Legal basis: steps you ask for before a contract (Art. 6(1)(b) GDPR).
Dynamic poll. In a dynamic poll the AI (Anthropic, USA; see section 6) writes each next question from your earlier answers in that poll; you answer by picking one of the ready answers. With an answer you can also add your own words in the “Anything else?” field (optional, up to 200 characters): the AI gets them to fit the next question, and sums them up without quoting in the findings for the poll’s author. Don’t write health data there. We reject such text: we don’t save it or send it to the AI. We save the conversation (the AI’s questions, the answers you picked and your own words) and its outcome, with no name and not linked to an account. If at the end you leave your email and tick the consent, we send you a sign-in link, create an account with a free profile, and the poll’s author gets a summary of the conversation with your address by email. We delete the conversation and the email after the poll’s period picked by the author (as for answers), counted from the start of the conversation, and at the latest with the poll. Legal basis: for the conversation as for polls above; for the email and the account your consent (Art. 6(1)(a) GDPR), which you can withdraw by writing to us.
“Can we guess?” in a dynamic poll. When you pick “I don’t need it” at the end, we offer to guess your answers to 2 or 3 more questions. Only once you agree, an AI model guesses what you will pick. It gets only the questions and the answers you picked in this conversation, without personal data: no name, email, IP address, conversation id or your words from the “Anything else?” field. We save the guess before your answers and keep it with them, like the conversation. If you give an email, we send one mail with the guess to it (through Resend) and don’t save the address. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw by writing to us.
News about Tuned. When you claim the reward you can separately tick that you want emails from us about what’s new in Tuned. It’s optional: the reward doesn’t depend on it. We save the time of the consent with the conversation, and the poll’s author sees it in the email with your address. You can withdraw it at any time by writing to us; after that we send no more news. Legal basis: your consent (Art. 6(1)(a) GDPR).
Brand and organisation. When you apply for a company or organisation, we save its name, website, size, purposes and logo, and then the decision on the application. The owner can invite colleagues: we save their email addresses, display name and role, and send the invitation by email. A company can connect Slack (then summaries of its polls go to the channel it picks, without text answers) and set up email notifications about results. Legal basis: performance of the contract (Art. 6(1)(b) GDPR); for invited people: the company’s and our legitimate interest in running the team (Art. 6(1)(f) GDPR).
Feedback. When you send feedback, we save its text, language, page address, app version and, if you are in a game, the mode and question, and if you are signed in, your account. Feedback is read by the administrator, and an AI model (Anthropic) helps group it. We keep it for 24 months; after an account is deleted it stays without a link to it. Legal basis: legitimate interest in improving the game (Art. 6(1)(f) GDPR). Before we save feedback, we remove from it whatever looks like a password, an e-mail address, or a phone, card or account number. If you tick “Let me know when it’s fixed”, your browser gets a random code in a cookie, and with your feedback we save only its hash and the place in the service (a screen name, not an address); once the fix notice is shown, after “Stop notifying” or after 90 days, the code and the hash are gone. After sending feedback you can vote for the room you are waiting for; we save only the choice (or the room name you type) and the language, without your account, for 24 months. We ask once: the browser saves that it was asked, and when you are signed in, the account saves only “voted” (not the choice), so other devices don’t ask again; the mark goes with the account. Under the room list you can tell us what room is missing (“Can’t find your room?”); it is ordinary feedback, and if you give the optional e-mail, we save it with it and use it only to reply about that room. We keep it with the feedback (24 months); on request we delete it sooner.
Testers. When you sign up for testing, you give your name, email and who you play with. We also save your mission reports and points. Change descriptions prepared from testers’ feedback may go to our code repository (GitHub), without account data. We keep the data until you stop testing or ask us to delete it. Legal basis: your consent (Art. 6(1)(a) GDPR).
Statistics. We use Vercel statistics (Web Analytics and Speed Insights) to know how many people visit the pages, how fast they load and how often rounds start and end. They work without cookies: a visitor is recognised by a hash made from the IP address and browser, which changes every 24 hours. We remove parameters (such as the room code) from addresses. We only see results in total. Legal basis: legitimate interest in developing the service (Art. 6(1)(f) GDPR). You can object to it (section 8) or block statistics in your browser.
Abuse protection. So that scripts can’t run up AI costs or poll votes, we count requests from one IP address: in the server’s memory for a few minutes, and AI limits in the database for up to 2 days. On sign-in and voting, invisible bot protection (Vercel BotID) checks properties of the browser. So that a script can’t download the whole question bank, the routes that serve bank questions count calls per IP address hash (it changes every day) and per random device id in the tbd cookie (sent only to our API); these counters are deleted after a day. When the calls look like a script, we record an event (IP hash, device id, reason and call counts) together with the full IP address, which we delete after 30 days and which only the administrator sees in the admin panel. The email to the administrator holds no IP address: only the country, region and city the hosting (Vercel) works out, and the IP hash. The device and address may be blocked for 24 hours. Legal basis: legitimate interest in keeping the service secure (Art. 6(1)(f) GDPR).
Who is in the room. To keep games safe, while a room is open the server records for each phone in it: the account (if you are signed in), the name shown in the room and a hash of the IP address that changes every day. We don’t store the IP address itself or the room code. This lets us recognise a person when something goes wrong and stop a script that poses as many phones from one connection. We delete the record about 2 hours after the last activity in the room. Legal basis: legitimate interest in keeping games safe (Art. 6(1)(f) GDPR). You can object to this (section 8).
Technical data. Our hosting providers log, among other things, IP addresses and browser information. Legal basis: legitimate interest in keeping the service secure and working (Art. 6(1)(f) GDPR).
3. Answers about feelings, relationships and health: your consent
In conversations (e.g. Date, Serious talk, Solve a problem) answers may be about your feelings, relationships, intimate life or health. These are special categories of data (Art. 9 GDPR), so we ask for your explicit consent. We ask only when a round starts in which the AI host writes the questions, sums up or comments on the answers. Rooms with ready-made questions and comments turned off work without it, and so does entering your name.
The consent window has three separate boxes:
- AI consent: your answers are read by the AI host (Anthropic, USA; see section 6), which uses them to write questions and comments; required to play with the AI. Legal basis: your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR),
- “I am 18 or older”: a statement, required to play with the AI,
- saving rounds without names: optional consent to “Game records” and “Improving the host” (section 2); without it you play just the same.
Your browser remembers your choice and the version of the consent text; when the text changes, we ask again. If you play with an account, we also save each consent with the account, with its version and the date it was given and withdrawn, so we can show what you agreed to.
You can play with the AI host if you are at least 18. Rooms without the AI are for people aged 16 or over; younger people may play them only with the consent of a parent or guardian.
If you pick “I’m under 18” in the consent window, you keep playing in the younger players’ mode: only rooms that play without the AI. This stays in this browser tab and is gone when you close it. We don’t send it to us or save it with an account.
The consents are voluntary, but without the AI consent and the age statement you can’t play in AI rooms, because the host always sees the answers. How to withdraw them: see section 8.
4. The other person’s data in the game
After a round, every player, with or without an account, decides with the “Save” / “Don’t save” buttons whether their name and answers may go into the other person’s history. Without this consent (including when nobody chooses anything) the other person saves only their own answers. Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by writing to host@tunedparty.com. Withdrawal does not affect the lawfulness of processing before it.
Don’t enter information about other people’s health, beliefs or intimate life in your name or in your own game topic.
5. Who we share data with
We use providers that process data on our behalf:
- Supabase: database, sign-in, the connection between players, files (voice recordings, logos); data stored in the European Union (Frankfurt),
- Vercel: hosting, statistics, bot protection,
- Anthropic: the AI model for the host, poll summaries and forecasts, dynamic polls, tidying game records and feedback,
- TypeSafe AI: the model that picks the next question and forecasts poll results,
- ElevenLabs: the AI voice,
- Resend: sending emails (sign-in codes, invitations, poll notifications, waiting list and event sign-up emails),
- Cloudflare (Turnstile): protecting sign-in from bots,
- Google (Workspace): our mailbox, which you write to.
Data also goes to companies that act as separate controllers, under their own rules:
- Google: sign-in with Google and dictation in Chrome,
- Apple: dictation in Safari,
- Slack: only when a company connects its channel; summaries of its polls go there,
- the poll’s author: answers to their poll and contacts left for them,
- the company running a waiting list: the emails and places of the people in its queue,
- the event organizer: the data of people who signed up for its event.
We keep the service’s code on GitHub; player data doesn’t go there. We don’t sell data or share it with advertisers.
6. Transfers outside the EEA
Some providers are based in the USA, so data may leave the European Economic Area. Each such transfer has a basis:
- Vercel, ElevenLabs, Resend, Cloudflare, Automattic, Google, Apple, Slack: a European Commission adequacy decision (EU-US Data Privacy Framework),
- Anthropic: standard contractual clauses approved by the Commission,
- TypeSafe AI: we send this provider no personal data: before sending we replace player names with made-up ones and cut out e-mail addresses and phone numbers, so it gets only the text of questions and answers with nothing showing whom they concern; that is why no standard contractual clauses are needed here,
- Supabase: data stays in the EU; technical support from outside the EEA works under standard contractual clauses.
You can get a copy of the safeguards by writing to host@tunedparty.com.
7. How long we keep data
- account, game history, “Pick-up lines” stats, record of your consents (section 3): until the account is deleted,
- name, settings and game state in the browser: until you clear browser data or close the tab (see section 10),
- game records (only when everyone in the room agreed): 24 months,
- AI comments from those rounds: 24 months; those the administrator approves as examples for the host (without names or details about people): with no time limit,
- question log (no answers or names): 90 days,
- feedback: 24 months,
- voice recordings of comments (accounts with the AI voice): 30 days; recordings of pool questions: until the question changes,
- AI costs: 24 months (the link to the account until it is deleted),
- answers to company polls and contacts left: for the period the author picks: 30, 90 or 180 days, or with the author’s confirmation 1, 2 or 5 years,
- dynamic poll conversations and the emails and consents left in them: for the poll’s period counted from the start of the conversation, at most until the poll is deleted,
- waiting list entries: 30 days after you buy or leave; an unconfirmed entry: 7 days; at most until the product is removed from the queue,
- event sign-ups: 30, 90 or 180 days after the event (the organizer’s choice); an unconfirmed sign-up: 1 day; after cancelling or removal by the organizer: at once,
- “I want these glasses” requests from the try-on: until the optician marks them done, 90 days at most,
- brand, logo and organisation members: until the organisation or the owner’s account is deleted,
- testers’ data: until you stop testing,
- IP addresses for limits: from a few minutes to 2 days; the full IP address in a question bank protection event: 30 days, only in the admin panel (the email about the event doesn’t contain it),
- the list of people in open rooms (account, name, IP address hash): about 2 hours after the last activity,
- technical logs at our providers: from an hour to a few weeks, depending on the provider.
When an account is deleted, we delete its history, stats and brand. What stays: feedback and AI costs without a link to the account, answers to company polls (until their period ends, without a link to the account) and game records and AI comments, which are never linked to an account.
8. Your rights
You have the right to:
- access your data and get a copy,
- have your data corrected,
- have your data deleted (e.g. your account with its game history),
- restrict processing,
- data portability,
- object to processing based on legitimate interest (e.g. statistics),
- lodge a complaint with a data protection authority: in Poland the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warsaw), or the authority in the country where you live.
To use these rights or delete your account, write to host@tunedparty.com from the address the account was created with.
Withdrawing consent. You can withdraw any consent at any time, as easily as you gave it. Signed in, you withdraw the AI consent and the round-saving consent (section 3) on your account page: Settings → Consents, the “Withdraw” button (withdrawing the AI consent also withdraws round saving). Without an account you withdraw them by clearing your browser data; signing out also clears the consents on that device. At the next AI round the game asks again. Game records and comments aren’t linked to you or to an account, so we usually can’t tell which ones are yours: withdrawing stops new records, and earlier ones go away within the periods in section 7. Withdrawal does not affect the lawfulness of processing before it.
9. Do you have to give us data
Giving data is voluntary. You can’t play without a name, and without an email address you can’t create an account or save history.
We don’t make decisions about you based solely on automated processing that would have legal or similarly significant effects on you. AI comments are for entertainment only.
11. Changes to this policy
We will announce important changes to this policy in the service. The rules for using the service are in the Terms of Service.