Privacy
This policy explains what information Examiniser collects — including account data, organisation and classroom data, student accounts, and homework submissions — how it is used to run the site and the Dashboard, and how to contact the site owner about privacy questions.
Examiniser is operated by an independent developer and educational publisher. If you need to contact the site owner about privacy matters, email examiniser@gmail.com. For student personal data created by a teacher or school within an organisation/classroom, that teacher/organisation is the data controller for the student records and Examiniser acts as a data processor on their instructions.
Organisations are shared workspaces where teachers collaborate. When you create an organisation, Examiniser stores its name, a URL-safe slug derived from the name, who created it, and billing linkage (Stripe customer ID).
When you invite or add members, Examiniser stores their Firebase UID, email, display name and photo URL (from Firebase Authentication), their role, and what they are allowed to do (for example manage classrooms, manage students, assign homework, manage billing). Invites store the invited email, requested role, who created the invite, and expiry/usage timestamps.
Your active organisation is remembered locally (localStorage key activeOrgId and the X-Organisation-Id header) and sent with Dashboard API requests so the correct workspace is used. Switching organisations clears student-scoped caches to avoid leaking data between workspaces.
Classrooms live inside an organisation. A classroom record includes its name, stage, badge appearance, creation time and a count of enrolled students. The teacher who creates a classroom controls the roster.
Student accounts are created and managed by teachers within an organisation — not by students self-registering. For each student, Examiniser stores a unique username (lower-cased, unique per organisation; the part before @ is chosen by the teacher and the @org-slug suffix is added automatically), a display name, optional exam board, classroom membership, and a hashed password. Plain-text passwords are never stored.
Students sign in separately from teachers using their username and password. Authentication uses an HttpOnly, Secure cookie (JWT, typically valid for 7 days) set by the API; it is not accessible to JavaScript. The browser also keeps a minimal display copy in sessionStorage (id, username, full_name) for the UI and a localStorage flag (studentSession) plus a per-student last-online date flag.
Teachers are responsible for creating accurate student records, choosing appropriate usernames, securely sharing initial passwords with learners, and only creating student accounts where they have lawful basis to do so — for example, as a school or tutor with parental or institutional consent for children in their care. If you are a school, you confirm you have obtained any required parental consent before creating accounts for children under your local age of digital consent.
When a teacher creates homework, Examiniser stores the classroom, title, selected topics and subtopics, level and configuration (pass percentage, question count, progression, timing, attempts), an optional due date, who created it, and a snapshot of the generated questions (LaTeX, answer, options, marks and metadata) plus a generation seed so the same set can be reproduced.
When a student attempts homework (or Daily / Practice questions), Examiniser stores question attempts (topic index, question index, whether correct, number of attempts, whether skipped, time taken), per-topic results (questions answered, correct answers, passed flag, streak and time remaining), completion status, when it was completed, and total time spent. Results are visible to teachers in the Dashboard via homework results and ranking endpoints.
Rankings and streaks aggregate these results per classroom — for example completion counts, average accuracy, current daily streak, longest streak and last streak date — to help teachers track progress. The Dashboard may also cache homework and daily data in the browser for up to 30 seconds to reduce repeated requests.
Examiniser uses Google Analytics to understand traffic and improve the site experience. This covers marketing and landing pages as well as general product usage; it does not replace the in-product learning analytics described above.
Users may learn more about how Google uses information by visiting Google's privacy documentation.
Examiniser uses cookies and similar technologies to enable authentication, process payments, remember your preferences, and understand site usage. Below is a summary of the cookies and technologies used:
Examiniser processes personal data under the following lawful bases:
Examiniser uses the following third-party services:
Firebase (Google) for teacher authentication, including sign-in with Google and Microsoft accounts.
Neon (PostgreSQL) for storing user accounts, organisations, classrooms, student records, homework and exam paper data.
Stripe for processing organisation subscription and usage-based billing (payment methods, customers and invoices).
AWS Lambda for running the API and backend processing.
Google Analytics for understanding traffic and improving the site experience.
Website hosting, CDN delivery, and other technical infrastructure providers. Those services may process technical data according to their own privacy policies.
No third-party service is given student plain-text passwords — only the hashed form is stored in our database.
Examiniser uses third-party services that may process data in countries outside the UK and European Economic Area (EEA), including the United States. These transfers are governed by appropriate safeguards, including Standard Contractual Clauses (SCCs) approved by the European Commission, or reliance on adequacy decisions where applicable.
The services that involve international data transfers include: Firebase (Google), Neon (PostgreSQL), AWS, Stripe, and Google Analytics. This applies equally to organisation, classroom, student and homework data.
Examiniser is an educational service that is often used with children in schools and tutoring contexts. Student accounts are teacher-managed: learners do not self-register. The teacher, school or organisation that creates a student account is responsible for ensuring it has a lawful basis to provide that child's data (such as parental consent or the school's legal mandate) under its local laws and for informing parents/guardians about how Examiniser processes the data on its behalf.
If you are under the age of 16 (or the age of digital consent in your country), you must obtain parental or guardian consent before using the service or before a teacher creates an account for you. Where a school has created your account, your school acts as the data controller for that record.
We do not knowingly collect personal data from children under 13 without verified parental consent (provided via the responsible teacher/organisation). If you believe a child has been added or has provided data without appropriate consent, please contact us at examiniser@gmail.com so we can delete it. Teachers should delete student records promptly when a learner leaves or consent is withdrawn.
Depending on your jurisdiction, you may have the following rights regarding your personal data:
To exercise any of these rights, contact examiniser@gmail.com or, for student data, contact your teacher/organisation first as the data controller. We will respond within the timeframes required by applicable law.
Examiniser retains personal data only for as long as necessary to fulfil the purposes described in this policy:
When you delete an organisation, classroom (when empty), student account, homework assignment or exam paper, the associated data is permanently erased from the primary store. Due to database redundancy and backups, complete purging across all redundant storage may take up to 6 hours to fully propagate. Billing invoices that have already been issued are retained as legal records.
In the event of a data breach that poses a risk to your rights and freedoms, Examiniser will notify the relevant supervisory authority within 72 hours of becoming aware of the breach, in accordance with applicable law.
If the breach is likely to result in a high risk to your rights and freedoms — including for student accounts managed by schools — we will also notify affected users and, where applicable, the responsible organisation owner/admin without undue delay.
If you are a California resident, the California Consumer Privacy Act (CCPA) grants you the following additional rights:
Examiniser does not sell your personal information — including student, classroom or homework data — so there is no opt-out process needed. If our data-sharing practices change in the future, we will update this policy and provide a clear opt-out mechanism.
This policy may be updated as Examiniser changes — for example when Dashboard, classroom or student features evolve. Material updates will be reflected on this page and, where appropriate, notified to users via email or an in-product notice.
Last updated: 17 September 2026.