← Home

Privacy policy

How [Operator name] handles the data this service collects.

For the operator: the sections below describe what the software does, which is accurate as written. The bracketed items — legal entity, jurisdiction, contact address, sub-processor list, retention defaults and any certifications — must be completed and reviewed by counsel before this page is published. Do not present it as a finished policy until then.

What is collected

From teachers. An email address and name, taken from the sign-in provider, plus the quizzes, questions and settings created in the product. If a paid plan is purchased, billing is handled by Paddle; card details never reach this service.

From students. Whatever name a student types when joining a room, their answers, how long each answer took, and — where a teacher has enabled it — a persistent profile holding their score history, XP, badges and streaks.

Automatically. Standard server logs, and error reports via Sentry where the operator has configured it.

No student account is required to take part. Students are identified only by the name they type, which need not be their full name.

Why it is collected

To run the assessment: showing questions, recording answers, scoring them, and reporting results back to the teacher who ran the session. Longitudinal profiles exist so a teacher can see how a student is progressing over time.

Student data is never used for advertising, never sold, and never used to train models.

Who can see it

A student's answers are visible to the teacher who ran the session. Where a quiz is shared with a colleague or an organisation, that sharing covers the quiz content — not the response data from sessions run by someone else.

Word cloud and Live Q&A responses are shown on a shared classroom screen by design. Teachers can require every such response to be approved first, and an automatic filter holds back anything it flags.

How long it is kept

By default, data is kept until deleted. Teachers can set retention windows — for ended sessions and for inactive student profiles — under Privacy & data in their account, after which the data is deleted automatically.

[Operator: state your default retention here if you set one at the organisation level.]

Access, correction and deletion

A student, parent or guardian may request a copy of the data held about that student, or ask for it to be deleted. Teachers can produce both from the Privacy & data page in their account. Requests can also be sent to [privacy contact email].

Deleting a student's record removes their profile, name and progression data. Their answers remain in the affected sessions' aggregate statistics in de-identified form, so that other students' results are not retroactively changed.

Where it is stored

Data is held in a PostgreSQL database with a Redis cache, operated by [Operator: name your hosting provider and region]. Traffic is encrypted in transit.

[Operator: list your sub-processors — hosting, error reporting, email delivery, payments.]

Children

This service is designed for classroom use, which means it will be used by children. It asks students for a display name and nothing else — no email, no date of birth, no contact details.

[Operator: state your position on COPPA (US, under 13), FERPA (US school records), the UK Age Appropriate Design Code, and GDPR Article 8 as applicable to where you operate. If you rely on schools to obtain parental consent, say so here and reflect it in your terms.]

Changes

Material changes to this policy will be announced in the product before they take effect.

Contact

Questions or requests: [privacy contact email].

[Operator: add your legal entity name, registered address, and a data protection officer or EU/UK representative if you need one.]

See also the accessibility statement.