The school stays in control
The school decides when the service is used and remains responsible for the lawful use of pupil information.
Privacy policy & school trust.
This page is for teachers, school leaders, data-protection teams, pupils and families. It explains what the service does, who remains responsible and the safeguards used before a school workspace is activated.
Closed beta · Fictional work only · School review pending
The current closed beta
Fictional testing is enabled. Real pupil work is not authorised.
The pupil-data policy and processing schedule below remain for school review. A completed DPIA, suitable school agreement and separate activation review are still required before a real-data pilot.
The pupil-data policy and processing schedule below remain for school review. A completed DPIA, suitable school agreement and separate activation review are still required before a real-data pilot.
Account and workspace information
Peter Oakley, trading as Marking Moose, operates this limited test while company formation is awaiting confirmation. Only explicitly approved Google accounts may sign in; public registration and new waitlist collection are closed.
Google sign-in provides an account identifier, email address and display name. The service records school membership, invitations, session records, fictional classes, teacher-selected assessment material, marks, feedback and reports so authorised testers can use the assessment workflow. Usage records support operating limits and cost monitoring.
Where information is held and who can see it
The beta uses an isolated PostgreSQL database on Google Cloud SQL and application hosting on Cloud Run, both configured in London (europe-west2). This is not a promise that all processing stays in the UK: Google sign-in, Drive and Gemini have separate service terms and processing arrangements.
Teachers use their own dashboards. School administrators can view activity counts and manage access, but their activity overview does not display pupil papers, marks or feedback. AI token and cost monitoring is restricted to the explicitly authorised service operator.
Files and AI
Use entirely fictional assessments for this beta—not real pupil papers with names removed. Google Drive access is used for files deliberately selected by the teacher. Gemini receives assessment content and approved marking instructions. The current marking route requests store: false; this is not a guarantee of zero provider logging or retention. The provider's contractual retention and processing evidence must be reviewed separately for the pupil-data pilot.
Retention and questions
A marking allowance's end date stops further marking; it does not automatically delete stored classes or reports. Test-record cleanup, backup expiry and the final retention schedule must be confirmed before the real-data pilot. Do not upload personal pupil information while that review is pending.
For account, access, deletion or privacy questions, use the request form below or contact privacy@markingmoose.co.uk. The school-facing pupil-data notice below is not a substitute for the final school agreement or approval.
Beta information updated: 8 October 2026. The school-review sections below were last revised on 30 August 2026 and still need final approval.
WAITLIST PRIVACY NOTICE
When you ask to hear from Marking Moose
Notice version: marking-moose-waitlist-2026-08-29. This section applies to prospective teachers and school staff who complete the public waitlist form. It is separate from the school-controlled pupil-data processing explained below.
Who is responsible and why we use the details
Peter Oakley, trading as Marking Moose, is the controller for waitlist information. MARKING MOOSE LTD incorporation is in progress; the company number and confirmed registered office will be added only after Companies House has completed the registration. The verified product domains are markingmoose.co.uk and markingmoose.com.
We use the email address and preferences you submit to manage the waitlist, understand demand and send the launch or pilot messages you expressly requested. Consent is our intended lawful basis for those optional marketing emails. You may withdraw it at any time without affecting earlier lawful processing.
What we collect
Your work email is required. Name, role, subject, school, organisation scope and pilot interest are optional or preference fields. We also retain the consent wording version, time, source and contact status as evidence of your choice. A short-lived, one-way identifier derived from the network address is used in memory to limit automated submissions; the raw address is not added to the waitlist record.
Sharing, location and retention
Waitlist records are stored in the service's Google Cloud database and are available only to authorised operators. We do not sell the list or share it with schools or AI marking providers. Before any separate email-delivery provider is used, this notice and the subprocessor record must be updated and the provider's contract, security, location and transfer arrangements reviewed.
Waitlist details are kept until the launch decision or for no longer than 12 months after the last relevant interaction. An unsubscribed contact is suppressed from marketing immediately; a minimal suppression record may be kept where necessary to honour that choice. Earlier deletion requests are completed unless information must be retained for a legal reason.
Your choices and rights
Every marketing message will provide a clear way to unsubscribe. You can use the form below or email privacy@markingmoose.co.uk to withdraw consent or ask for access, correction, restriction, objection, portability or deletion where applicable. We will verify requests where needed and normally respond within one month. You may complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint.
No pupil work is involved in joining the waitlist.
A waitlist entry does not create a teacher account, authorise a school workspace, call an AI model or take a payment.
A waitlist entry does not create a teacher account, authorise a school workspace, call an AI model or take a payment.
AT A GLANCE
The important points first
Teachers decide the final mark
AI suggestions are checked against teacher-approved rules. Teachers can review exceptions and change marks before finalising.
Names are separated
Direct pupil names and the private re-identification link are not deliberately sent to the marking model.
Schools approve access
Real pupil work remains locked until an authorised school representative and the service operator complete the approval process.
PRIVACY
What information is used—and why
For an approved future pupil-data pilot, the school is the data controller and Marking Moose acts on the school's instructions to support assessment marking, feedback and class-level teaching insights. That pilot has not been activated.
Information the service may process
- teacher-selected question papers, mark schemes and pupil answers;
- a pseudonymous learner reference and encrypted link to the teacher's original file;
- marks, evidence, feedback, teacher changes and generated reports; and
- teacher account details and limited security and product audit information.
The service is not designed to collect additional pupil profiles, medical records or behaviour records. Teachers should select only the assessment information needed for marking.
HOW AI HELPS
Support for professional judgement—not a replacement
Before marking, the question paper and mark scheme are matched and locked. For each answer, the marking provider receives the relevant question, the teacher-approved rule and the minimum answer content needed to suggest a mark.
The service records evidence and explanations beside marking decisions. Lower-confidence or conflicting decisions can be surfaced for teacher review.
The teacher makes the final decision.
The service is not intended to make solely automated decisions with legal or similarly significant effects. A teacher can review and alter the result before it is finalised.
The service is not intended to make solely automated decisions with legal or similarly significant effects. A teacher can review and alter the result before it is finalised.
SECURITY
How school information is protected
School separationAccess to classes, assessments and reports is checked against the signed-in teacher's active school membership.
Private identifiersFilename links, safeguarding excerpts and teacher review notes are encrypted before database storage.
Minimum model contentDirect names, teacher email addresses and the re-identification mapping are not deliberately included in marking requests.
Controlled reportsGenerated reports use private, authorised download routes rather than public file links.
No online service can promise zero risk. Schools receive a named incident route, and suspected loss, unauthorised access or incorrect disclosure is assessed and managed under the agreed incident process.
SERVICE PROVIDERS
Who helps operate the service
These provider groups support the fictional beta. Their pupil-data processing arrangements are subject to the school agreement and activation review; the beta does not establish approval for real pupil work.
| Provider | What it provides | Information involved |
|---|---|---|
| Google Cloud Platform | Application hosting, database, private report storage and secrets management | Application records and generated reports needed to operate the authorised school workspace. |
| Google Identity and Drive APIs | Teacher sign-in and access to files deliberately selected by the teacher | Teacher identity and the specific Drive files the teacher chooses. |
| Google Gemini API | Primary assessment marking | Pseudonymised answer content, the relevant question and the locked teacher-approved marking rule. |
A proposed provider is not treated as an active school-data subprocessor until its contractual, location, retention and security checks have been completed.
RETENTION & DELETION
Information is not kept indefinitely
Before activation, the school agreement records how long assessment records, reports, logs and recoverable backups are needed. The school can request an export and authorised deletion in line with that agreement.
- Assessment work and reports are retained only for the agreed service or pilot period.
- Security and application logs are kept for a limited operational period and should not contain pupil answers.
- Recoverable backup copies expire after the agreed recovery window.
- Safeguarding-related excerpts follow the shorter process explained below.
SAFEGUARDING
A possible concern is held for a human—not interpreted as a mark
The service may surface words that could indicate a safeguarding concern. That work is held away from ordinary AI marking and shown to an authorised teacher so the school's established safeguarding procedure can be followed.
This is an alerting aid, not a safeguarding monitoring system.
It cannot guarantee that every concern will be detected and does not decide whether text is a disclosure or safeguarding incident. School staff remain responsible for professional judgement, recording and action.
It cannot guarantee that every concern will be detected and does not decide whether text is a disclosure or safeguarding incident. School staff remain responsible for professional judgement, recording and action.
Once necessary information has been transferred to the school's established safeguarding record, the service removes the temporary excerpt in line with the agreed schedule. The school does not need to publish the name of its designated safeguarding lead on this website.
PUPILS, FAMILIES & TEACHERS
Questions, corrections and information rights
Pupils and families should contact their school if they want to understand how assessment work was used, question a mark, or exercise an applicable information right. The school can ask Marking Moose to help with access, correction, restriction, export or deletion.
Participating teachers can email support@markingmoose.co.uk about their account, or privacy@markingmoose.co.uk to report a suspected security or privacy issue. Each approved pilot agreement includes the relevant school and supplier contacts.
FOR SCHOOL REVIEW
What is agreed before real pupil work is enabled
The school confirms
- authorisation and its lawful basis;
- appropriate pupil, family and staff privacy information;
- which teachers and assessments are approved;
- retention and deletion requirements; and
- its safeguarding and incident contacts.
Marking Moose confirms
- documented processing instructions and confidentiality;
- security and school-access controls;
- the approved service-provider list;
- assistance with rights, incidents and deletion; and
- the separate activation review has been completed.
The signed school agreement and completed processing schedule control an approved real-pupil pilot. Reading this public page alone does not activate a school workspace.