Privacy policy
In short
- We collect little. Participants join with a nickname, no account and no email. Presenters sign in with Google or an email link.
- We have no advertising, no analytics and no tracking, so no cookie banner. Section 8 lists everything we store in your browser.
- We play two roles. For account, website and billing data, we are the controller. For what happens in a room, the organiser (school, company or trainer) is the controller and limequiz is its processor. Section 3 explains what that means for you.
- Our servers are in the EU. AI is the exception: Anthropic processes it in the United States. From participants it only receives the text of sticky notes a presenter groups by idea, without saying who wrote them.
- You can access, correct, delete and move your data, and complain to the Spanish data protection authority (AEPD). Section 10 says how.
1. Who is responsible
For the data described in section 2, the controller is:
The self-employed person who runs limequiz, in Spain
Privacy contact: hello@limequiz.com (we give our full name, tax ID and postal address to anyone who asks)
We do not need a data protection officer. Write to the address above for anything about your data.
2. Data we handle as controller
| Why | What | Legal basis (GDPR art. 6) | How long |
|---|---|---|---|
| Your account (sign-in, profile, workspace, language) | Email, name, profile picture (as Google gives it, if you use Google), language, how you plan to use limequiz, workspace and membership | Contract: providing limequiz to you (6.1.b) | While your account exists. We delete it at once when you delete your account. Backups roll over within 30 days. |
| Your quizzes and content | Quizzes, questions, images and files you create or upload, sessions you run | Contract (6.1.b) | Until you delete them or your account |
| AI: generating quizzes and improving a question | The topic, notes or PDF you send, or a question you ask it to improve, and what comes back. We do not keep the source material. We keep the quiz, plus counts (model, tokens, number of questions). | Contract: you asked for the feature (6.1.b) | The quiz stays with your content. Anthropic deletes inputs and outputs after at most 30 days (longer only for content it flags as breaking its usage policy). |
| Plan limits and usage | How many rooms, AI generations and API requests each workspace uses | Contract (6.1.b) | While the account exists |
| Billing (paid plans, once available) | From Paddle: your email, country, plan and subscription status, payment events. We never see your card details. | Contract and legal obligation (6.1.b, 6.1.c) | As tax and accounting law requires, generally 6 years (Spanish Commercial Code, article 30) |
| Security and abuse prevention | A keyed, hashed form of your network address to limit joins, sign-in emails and guesses at room codes (the address itself is not stored by us), a hashed form of the email address you sign in with to limit sign-in emails, and technical logs kept by our hosting and database providers | Legitimate interest in keeping the service safe (6.1.f) | About one day for rate-limit keys. Provider logs are kept by the provider for 30 days at most. |
| Support and contact | What you send us, and our reply | Legitimate interest, and contract if you are a customer (6.1.f, 6.1.b) | 24 months after the conversation ends |
| Proof of terms | The date your account was created, which shows which version of the Terms you accepted | Contract and defending legal claims (6.1.b, 6.1.f) | While your account exists |
| Reports of content | The report, and the reporter's name and email when given | Legal obligation under the Digital Services Act (6.1.c) | 12 months after our decision |
| Emails we send | Sign-in emails, invitations to join a school's team, and notices about your account or these terms. We send no marketing emails unless you ask for them. | Contract (6.1.b) | Not stored beyond delivery, apart from the provider's short logs |
We do not sell personal data. We do not use it for advertising, and we make no automated decisions about you that have legal or similarly significant effects.
You need to give an email address to have an account, because we cannot sign you in or contact you without one. Everything else is optional or comes from what you do in limequiz.
Google Sign-In. If you sign in with Google, Google is an independent controller of your Google account and tells you how it uses that data. We receive your email, name and profile picture from Google.
3. Rooms: the organiser decides, limequiz processes
When a presenter runs a room, the organiser (the school, company, trainer or other body they act for) decides why and how participants' data is used. The organiser is the controller. limequiz is the processor: we handle that data only on the organiser's instructions and under the data processing agreement. A teacher acts for their school.
What we hold about a participant. The name they typed, their buddy (a look generated from their name, which they can change), their answers and free-text responses, when they joined and were last seen, and a random code that stops the same join being counted twice. We do not collect participants' emails, phone numbers or accounts, and our database does not store their network address. Our hosting and database providers' short-lived technical logs do contain it, as with any website.
What we do with it. We store it to run the room, show results to the presenter (and on the projector when the presenter chooses), and delete it later. We do not use it for our own purposes: no advertising, no profiling, no tracking across rooms, no AI training. We do not put participants' answers in emails, and only one kind goes to our AI provider, Anthropic: sticky notes, when the presenter has «Group by idea when shown» on (the default). Then the notes' text goes, without saying who wrote them, so Anthropic can sort the notes by idea and mark hurtful ones, which «Automatic moderation of answers and words» hides. The presenter can turn the grouping off on each block. If a presenter connects their own AI assistant to limequiz (through the MCP server), the assistant receives the results they ask it for, such as names and scores, under the presenter's control. Our own use is limited to counting anonymous totals, such as how many rooms were run.
Who can see a room. What a room shows on the big screen (participants' names and buddies, answers once the presenter reveals them, and the scoreboard) can be seen by anyone who has the room's code, until the room is deleted. Codes are random, rooms are not listed or indexed by search engines, and repeated guesses are blocked. Presenters can hide answers, remove participants or delete the room at any time.
How long. We delete each room automatically 12 months after it was created, with its participants' names and answers, on every plan. Presenters can delete a room sooner at any time. The join screen says so.
Your rights as a participant. Because the organiser is the controller, ask them first: to see, correct or delete your data. If you contact us instead, we pass your request on to the organiser and help them answer it. You may also complain to the AEPD.
A note for organisers. You need a lawful basis, and you must inform participants. A school normally relies on its educational function, and a company on its own legitimate purposes or a contract. limequiz provides a short notice on the join screen, but it does not replace your own information. For pupils, use nicknames or first names only, and do not publish results that identify children.
4. Who receives data
Only the providers we need to run limequiz, listed with their location and safeguards on the sub-processors page: Supabase (database and sign-in), Vercel (hosting), Anthropic (AI: presenters' inputs, and the text of sticky notes grouped by idea), Resend (emails to presenters) and, for paid plans, Paddle. We give data to authorities only when the law requires it.
5. Data outside the EU
- Database and hosting. The database is with Supabase in Frankfurt, Germany (AWS eu-central-1), and our server functions run in Frankfurt (Vercel). Vercel's global network and its account and log systems, and Supabase's support and some backups, can involve the United States.
- AI. Anthropic processes, only in the United States, the topic, notes and PDFs you send, a question you ask it to improve and, when sticky notes are grouped by idea, the text of the notes. Do not put pupils' personal data or other special data into what you send.
- Email. Resend delivers our emails (sign-in emails and team invitations), and it stores email addresses, logs and message content in the United States.
For each of these transfers we rely on the EU's Standard Contractual Clauses, and where the provider is certified, on the EU-US Data Privacy Framework as well. Ask us at hello@limequiz.com for a copy of the safeguards.
6. Children
Presenter accounts are for people 18 or older. Participants are often pupils, but they join a room run by their school or organiser, and we do not offer limequiz to children as account holders. Schools decide whether and how their pupils take part.
7. Security
Access to data is limited by row-level rules in the database, so presenters only see their own workspace. Participants act in a room only with the token their phone got when they joined, and a room's public view is reachable only with its code (section 3). Traffic is encrypted, personal API tokens are stored only as hashes, and the keys that unlock the database stay on our servers. Details are in the security annex of the data processing agreement. We have a procedure for personal data breaches, including telling the AEPD within 72 hours where required and telling organisers without undue delay.
8. Storage and cookies
limequiz uses no advertising, analytics or third-party tracking cookies or scripts. It only stores what it needs to work, which needs no consent under article 22.2 of the Spanish LSSI and article 5(3) of the ePrivacy Directive, because it is strictly necessary for a service you asked for, or a setting you chose. That is why there is no cookie banner.
Cookies
| Name | Who | What it does | How long | Why no consent is needed |
|---|---|---|---|---|
sb-…-auth-token (may be split into numbered parts) |
Presenters, once signed in | Keeps you signed in and refreshes your session | Up to 400 days, or until you sign out | Strictly necessary to provide the sign-in you asked for |
sb-…-auth-token-code-verifier |
Presenters, while signing in | Completes a Google or email sign-in securely | Removed after sign-in | Strictly necessary for sign-in |
lq_next |
Presenters, while signing in | Remembers which page to return to after sign-in | 1 hour at most, removed after sign-in | Strictly necessary for sign-in |
NEXT_LOCALE |
Anyone who chooses a language, and presenters when they sign in | Remembers the language you chose (English or Spanish) | 1 year | A preference you chose. Without it the site follows your browser's language. |
In your browser's storage (localStorage, or sessionStorage if the first is blocked)
| Name | Who | What it does | How long | Why no consent is needed |
|---|---|---|---|---|
live-workshop-participant:<ROOM CODE> |
Participants | A random id, a token, the name and the look you chose for that room, so that if the page reloads you rejoin as yourself | Until you clear your browser data | Strictly necessary to keep you in the room you joined |
live-workshop-join-attempt:<ROOM CODE>:<name> |
Participants, while joining | A random code that stops one join from being counted twice if the network retries | Removed once you have joined | Strictly necessary to join |
live-workshop-asked-name:<ROOM CODE> |
Participants whose name was taken | The name you typed, so the waiting room can say why you got a number after it | Until you join that room again or clear your browser data | Part of joining the room you asked for |
live-workshop-fresh-join:<ROOM CODE> (sessionStorage) |
Participants | The moment you joined, so the waiting room greets you once | Removed by the waiting room, or when you close the tab | Part of joining the room you asked for |
limequiz:draft:<ROOM CODE>:<question> (sessionStorage) |
Participants | An answer you are still writing, so a reload doesn't lose it | Removed when you send it, or when you close the tab | Strictly necessary for the answer you are giving |
limequiz:finale-seen:<ROOM CODE> (sessionStorage) |
Participants | Remembers that you saw the final podium, so it doesn't replay | Until you close the tab | Part of the room you joined |
lq_sign_in |
Presenters, while signing in | The email address you typed and when the email was sent, so a reload after checking your mail returns to the right step | Used for 1 hour. Removed when you sign out or delete your account | Strictly necessary for the sign-in you asked for |
limequiz:import-draft:<workspace> (sessionStorage) |
Presenters | A quiz you are pasting in, until it is created | Removed when the quiz is created, or when you close the tab | Strictly necessary for the import you asked for |
limequiz:sound |
Anyone who changes the sound | Whether sounds are on, quiet or off | Until you clear your browser data | A setting you chose |
limequiz:editor-preview |
Presenters | Whether the preview is open in the quiz editor | Until you clear your browser data | A setting you chose |
You can delete all of these at any time in your browser settings. If you delete the sign-in cookies, you will be signed out. If you delete a room's participant entry, you will have to join that room again.
If we ever add measurement of our own website's audience, it will be limited to anonymous statistics that meet the conditions in the Spanish data protection authority's guidance, and we will describe it here first. We will ask for consent for anything that does not meet them.
9. How long we keep data
The table in section 2 gives the period for each purpose. In short: account data, until you delete your account; participant data, 12 months after the room was created (sooner if the presenter deletes the room); billing records, as tax law requires. When we delete data from live systems, copies in backups disappear within 30 days.
10. Your rights
You can ask us to give you access to your data, correct it, delete it, restrict its use, object to uses based on our legitimate interest, or send it to you in a portable format. Where a use depends on your consent, you can withdraw it at any time. Write to hello@limequiz.com. We may ask you to prove who you are, and we reply within one month, which the law lets us extend by two months for complex requests. It costs nothing.
If you think we are not handling your data properly, you may complain to the Agencia Española de Protección de Datos (AEPD): www.aepd.es, C/ Jorge Juan, 6, 28001 Madrid. If you live in another EU country, you can also complain to your own authority.
11. Changes to this policy
If we change this policy in a way that matters, we tell presenters by email or in the app before it takes effect. The version and date are at the top.