Compliance and Data Protection built for schools

Ask anything about how we handle your school's data.

Pick a question. We'll show you the answer in plain English, the contract clause that backs it, and where in the data flow it applies. No chasing PDFs, no jargon.

  • UK and EU storage only
  • Zero training on your data
  • SSO via Entra ID / Workspace
  • ICO ZB619200

Last reviewed: · Service Agreement: v2.2 · DPA: v2.0 · View sub-processors

Frequently asked questions about TeachGen AI data protection

Common questions

Answer

Where is my school's data physically stored?

All TeachGen AI customer data is stored in data centres located in the United Kingdom and the European Union only. Specifically: Microsoft Azure UK-South and EU-West, AWS Ireland (eu-west-1), and Google Cloud europe-west regions. International transfers to specific sub-processors are governed by the UK International Data Transfer Agreement, EU Standard Contractual Clauses, or the EU-US Data Privacy Framework, all listed in our Data Processing Addendum, Schedule 2.

UK / EU onlyDPA Clause 1.3

Want the full contractual language? Download the Service Agreement or Data Processing Addendum.

The data journey

Follow a single prompt from teacher to teacher.

Five hops. Each one named, encrypted, and covered by the DPA.

  1. Teacher writes a prompt

    School device - UK

    Encrypted in transit
  2. TLS to TeachGen edge

    Cloudflare edge

    IDTA + SCCs
  3. Names hidden from the AI

    When we ask for pupil names

    12 tools
  4. Inference, never training

    Azure / AWS / GCP - EU

    Enterprise API
  5. Output returned

    Back to teacher

    Logs 30 days
DPO checklist

What you can tick off today.

  • ICO registration verified

    Look up ZB619200 on the public register

  • Service Agreement reviewed

    Linked, downloadable, version-stamped

  • DPA reviewed

    GDPR Article 28 plus sub-processors

  • Transfer mechanisms confirmed

    IDTA / SCCs / DPF in place for restricted transfers

  • Teacher-in-the-loop confirmed

    Aligned with DfE generative-AI guidance for schools

  • Sub-processor list bookmarked

    At least 30 days' written notice on changes

Live register

Every sub-processor we use.

Updated whenever a sub-processor is added or replaced. We give at least 30 days' written notice to customers before any change takes effect. Last verified .

Sub-processor registerView the full live register →Every sub-processor we use, the data they touch, the region they run in, and the transfer safeguard. Version-stamped and updated whenever it changes.