Security
Education software security at Inclusion Studio: how learner support records are protected, what is built so far and what still needs independent testing.
Trust centre
What Inclusion Studio does to protect learner information, where data is processed, how AI is used and what we have not yet completed, stated plainly.
Inclusion Studio is pre-pilot and uses synthetic data only. This trust centre explains our security and privacy design, where data will be processed, how AI is used and what assurance work must be finished before any real learner data is used.
Education software security at Inclusion Studio: how learner support records are protected, what is built so far and what still needs independent testing.
Data protection for learner support software: who is controller and processor, how learner data is minimised and protected, and what work is not done yet.
Where is learner data stored? The main database is in London, UK. Sign-in, hosting, files, AI, email and telemetry may run elsewhere. Mapped layer by layer.
Our AI principles in education: how Inclusion Studio uses AI, what AI will never do with learner records, and what must be decided before real data reaches AI.
The Inclusion Studio accessibility statement: how accessible this website is, the WCAG 2.2 AA standard we work to, how to report a problem and updates.
Inclusion Studio subprocessors: the providers we intend to use for learner support data, what each would do, where it runs, and its contract status.
How to report a security vulnerability in Inclusion Studio's website or published code, what we ask of you, how we will respond and our safe harbour commitment.
Inclusion Studio is not a safeguarding case management system. How safeguarding concerns and occupational health records stay separate, and what staff should do.
The independent checks, assessments and tests Inclusion Studio must complete before any real learner data is used, stated as gates rather than dates or promises.
Learner support records can include disability, health and other sensitive information. We think you should be able to see exactly what we do, and exactly what we have not done yet. We do not make compliance or certification claims we cannot evidence. If your procurement requires a specific standard, talk to us early.
It can be, but only if security and data protection are designed in and then independently checked, and you should ask any supplier for evidence of both. For Inclusion Studio, the design is in place and the checking is not yet done. Our security page describes server-side permissions by organisation, relationship and field, private document storage and separated environments. None of this has been independently tested yet, and we say so.
The primary application database is hosted in London (Neon, AWS eu-west-2). Supporting services such as sign-in, hosting and file storage may process data elsewhere, including the United States. Our page on where data is processed goes service by service, and the draft subprocessors list shows which providers are chosen and which are not.
Real learner data will not be used until every gate on our assurance roadmap is passed. Those gates include independent security and privacy review, verified tenant isolation and file protection, a DPIA and contract assessment, and tested restores. We do not give dates for these or promise certifications.
Our data protection page sets out the expected controller and processor roles, the design choices and the gaps. If you are preparing a DPIA, our guide to DPIAs for learner support software and the DPIA screening checklist are useful whichever supplier you assess. The data protection officers page summarises what a DPO will want to see.
AI is optional, labelled and reviewed by a person before anything is saved, and it never diagnoses, refuses support or makes decisions. Read the AI principles for the full list. Inclusion Studio is also not a safeguarding system: concerns go through your designated safeguarding lead, as set out in safeguarding boundaries.
Report security issues privately under our responsible disclosure policy, and accessibility problems through the accessibility statement. Both routes go through our contact page.
No. The prototype uses fictional learners and the production application in development uses synthetic data only. Real learner data will not be used until the gates on our assurance roadmap are passed.
The primary application database is hosted in London (Neon, AWS eu-west-2). Some supporting services, such as sign-in, hosting and file storage, may process data elsewhere, and each will be documented and assessed before real learner data is used.
Not yet. We do not hold Cyber Essentials, ISO 27001 or SOC 2, and we do not promise dates for them. Tell us early if your procurement requires a specific standard.
We expect the provider to be the controller and Inclusion Studio to act as its processor, under a contract agreed before any real data is used.
AI is optional and human-reviewed. AI is never trained on case records. Gemini on Google Cloud Vertex AI is the selected provider, tested with synthetic data only, and no real learner data has been sent to any AI provider.
We are working with a small number of England FE colleges and apprenticeship providers first. Tell us about your learner support and we will be in touch.