Privacy Policy

This policy explains what information qiz collects, why, and what you can do about it. The short version: we collect what's needed to run your sessions, we don't sell it, we don't show ads, and we don't use third-party analytics or tracking.

1. If you answer questions (participants)

• Your answers, the time you sent them, and a random participant ID. The ID lets us limit how many answers each person gives. It isn't linked to your name or email.
• Cookie lp_pid holds that random ID (up to one year). If your browser blocks it, the ID is kept in your browser's local storage instead (lp.pid).
• We don't ask participants for names or emails. Please don't put personal information in your answers.
• The presenter decides what happens with answers: they may show them to the audience, and they can export them. The presenter is responsible for their own use of the answers they collect.

2. If you create sessions (presenters)

• Email address, if you start a session with one. We use it to send you your presenter and audience links, and to connect those sessions to your account if you later sign in with the same email.
• Account details from sign-in, if you sign in with Google (or Microsoft, when available): your name, email address, profile picture link, and the provider's account ID. We never receive your password.
• Your sessions: titles, questions, settings, and activity such as answer counts and peak number of participants.
• Cookies: qiz_sess keeps you signed in (30 days; we store only a scrambled version of it); qiz_in just tells our pages you're signed in; qiz_oauth protects the sign-in step (10 minutes).
• Local storage in your browser remembers the presenter access for sessions you've opened (lp.admin.*) and the email you last used.
• Payments (when paid plans are available) are handled by Stripe. We receive your plan, payment status and renewal date, but never your full card number.

3. Technical information

Like any website, our hosting provider (Cloudflare) processes your IP address and basic request information to deliver pages and protect the service. We use IP addresses briefly to limit how fast sessions can be created and to block abuse. We keep a record of when we email an address, for up to 24 hours, so no inbox gets flooded. We don't build profiles of visitors.

4. How we use information

To run qiz: show questions and live results, enforce answer limits, send session links, keep you signed in, attach sessions to your account, process payments, prevent abuse, fix problems and understand overall usage (for example, how many sessions are created). We rely on providing the service you asked for, our legitimate interest in running and protecting it, and, where needed, your consent.

We don't sell or rent personal information, we don't share it for advertising, and we don't use it to train AI models.

5. Who else handles it

• Cloudflare — hosting, storage and databases, and sending our emails.
• Google and Microsoft — only if you choose to sign in with them.
• Stripe — payments, when paid plans are available.

We may also disclose information if the law requires it, to protect people's safety or our rights, or as part of a sale or transfer of qiz (in which case this policy keeps applying to your information).

6. How long we keep it

Sessions and their answers are kept until the presenter clears them or asks us to delete them; we may add automatic deletion of long-inactive sessions and will update this policy if we do. Account information is kept while your account exists. Sign-in sessions expire after 30 days. Payment records are kept as long as tax and accounting laws require.

7. Your choices and rights

You can ask us to see, correct, export or delete your information by emailing hello@qiz.io from the address on your account. Presenters can also clear a question's answers themselves. Participants: because answers aren't tied to your identity, tell us the session code, roughly when you answered and what you wrote, and we'll do our best — or ask the presenter. Depending on where you live (for example in the EU, UK or California), you may have further rights, including to object to or restrict some uses and to complain to your local data protection authority. We won't treat you differently for using these rights.

8. Security

All traffic is encrypted (HTTPS). Sign-in tokens are stored only in scrambled form, and presenter links use long random keys. No system is perfectly secure, so keep presenter links private and tell us at hello@qiz.io if you find a problem.

9. Children

Accounts are for people 16 and over. Participants can be younger — for example in a classroom — and don't give us their name or email. Teachers and other presenters working with children are responsible for any consent their school or local law requires, and should remind students not to enter personal information. If you believe a child has given us personal information, contact us and we'll delete it.

10. Where information is processed

qiz runs on Cloudflare's global network, so information may be processed in the United States and other countries. Where required, we rely on appropriate safeguards for these transfers.

11. Changes

We'll update the date at the top when this policy changes, and give notice on the site or by email for material changes.

12. Contact

Email hello@qiz.io with any privacy question or request.