Last updated: 29 October 2026 Change notification: we will notify schools at least 30 days before adding or replacing a sub-processor that processes pupil personal data.
The following sub-processors are engaged to deliver the OMNIA Inclusion service. All are bound by a Data Processing Agreement equivalent to or stronger than the one we offer schools.
Infrastructure
| Sub-processor | Service | Data category | Location | Transfer basis |
|---|---|---|---|---|
| Supabase Inc. (via Lovable Cloud) | Database hosting, object storage, authentication | All School Data | EEA — AWS eu-west-1, Ireland | UK adequacy regulation for the EEA. No IDTA or SCCs required. |
| Lovable (platform provider; contracting entity per Lovable's DPA of 17 November 2025) | Application hosting platform and development environment; operates Lovable Cloud | All School Data (via Supabase) | Data stored in the EEA: AWS eu-west-1, Ireland | Lovable DPA in place. Any transfer outside the UK/EEA is made under the EU SCCs and the UK Addendum (Lovable DPA s.8). |
| Cloudflare, Inc. | Edge compute (Workers), CDN, DDoS protection | Request bodies in-memory only; no persistence at the edge | Globally distributed; EU edge nodes preferred for EU visitors | UK IDTA / EU SCCs in Cloudflare DPA |
AI
AI requests are made from OMNIA's server, never from the browser. Before a request leaves OMNIA it passes through our PII scrubber, which replaces the pupil's names (full name and each part, as written or in capitals), staff names where known, UPN, ULN and NI numbers, street addresses and postcodes, and masks email addresses, phone numbers and the year in dates. The scrubber is best-effort defence-in-depth: free text can still carry identifying detail it doesn't recognise.
| Sub-processor | Service | Data category | Location | Notes |
|---|---|---|---|---|
| Lovable (AI Gateway) | Two narrow uses only: the in-app support assistant (search over OMNIA's own help pages), and a superadmin tool that reads public web pages for the signposting directory. Also the standby route if OMNIA switches the London service off in an emergency. | Support questions after the PII scrubber; public web text. No pupil records. | Not stated in Lovable's DPA; transfers outside the UK/EEA under the EU SCCs and UK Addendum (Lovable DPA s.8) | Lovable's DPA (s.10.1): customer personal data is not used for training. |
| Google Cloud (Vertex AI) | OMNIA's main AI provider: plan and SMART target drafting, assessment summaries, specialist report summaries and Q&A answers, meeting-note extraction, quick adaptations, translation for parents, and Document Q&A search indexing. Also the voice transcription fallback, used only when the staff member's device can't transcribe a recording and the school allows it. | Text after the PII scrubber. Voice recordings (audio can't be scrubbed) only for the fallback. | London, UK (europe-west2 regional endpoint), under OMNIA's own Google Cloud agreement | Gemini models. Google doesn't use Vertex AI customer data for training. Schools can switch the voice fallback off in AI settings. |
| OpenAI, L.L.C. (embeddings, via the Lovable AI Gateway) | Search over OMNIA's own help pages for the support assistant | Support questions after the PII scrubber. No pupil records. | Outside the UK/EEA (OpenAI, via Lovable) | We do not opt in to model training. |
| School-managed AI provider (Bring Your Own Key, opt-in) | When a school connects its own Anthropic, Azure OpenAI, OpenAI or Google Gemini account, that school's AI traffic goes to its own account instead of OMNIA's London service. The school is the controller of that provider relationship. | As above, after the PII scrubber | The school's chosen provider and region (e.g. Azure UAE North or UK South) | Document Q&A search indexing still uses OMNIA-managed AI (above) when the school uses Anthropic or Google Gemini. Voice transcription runs on the device; a school with its own Gemini key uses that key for the server fallback. A provider error never falls back to OMNIA's account. API keys are AES-256-GCM encrypted at rest. |
| Sub-processor | Service | Data category | Location |
|---|---|---|---|
| Microsoft Corporation (Microsoft Graph) | Sending parent-voice and notification emails from the school's own M365 tenant where enabled | Recipient email + body | The school's M365 region |
| Lovable (managed email) | Service emails sent from notify.omnia-inclusion.com (e.g. sign-in links, invitations, plan notifications) | Recipient email + body | As for Lovable above |
| Resend (via the Lovable connector gateway) | Invoices and quotes, governor report sharing (aggregate figures only, no pupil data), website contact enquiries and Health Check action plans | Recipient email + body; no pupil personal data | United States |
School-controlled MIS integrations (opt-in, per school)
| Sub-processor | Service | Data category | Location | Notes |
|---|---|---|---|---|
| Go4Schools Ltd. | School MIS — source of UPN, name, DOB, year group, attainment grades, baseline grades and SEND attributes for pupils at the connecting school | Pupil identifiers and assessment data | UK | Read-only pull initiated by OMNIA using a per-school API key generated and revocable by the school's Go4Schools admin. Schools that do not connect Go4Schools send no data to this sub-processor. We do not write back to Go4Schools. |
School-controlled integrations (opt-in, per school)
| Sub-processor | Service | Data category | Location | Notes |
|---|---|---|---|---|
| Wonde Ltd | MIS sync: pupils, staff, classes and attendance from the school's MIS, authorised by the school in Wonde | Pupil and staff identifiers, class membership, attendance | Per Wonde's DPA (Wonde Ltd is a UK company) | Read-only. The school grants and revokes access in Wonde. |
| Google LLC (Google Workspace: Drive, Calendar) | Publishing plans and documents to the school's own Google Drive; review meetings to Google Calendar | Documents and events the school chooses to publish | The school's Google Workspace | Uses the school's own Google account, connected and disconnected by the school. |
| Microsoft Corporation (SharePoint, Entra ID) | Publishing plans to the school's SharePoint; sign-in with Entra ID | Documents the school chooses to publish; sign-in identity | The school's Microsoft 365 tenant | Uses the school's own Microsoft tenant. |
Operational / support tools (no pupil data)
| Sub-processor | Service | Data category | Location |
|---|---|---|---|
| Stripe, Inc. | Billing (when we begin charging) | Billing contact + payment metadata only | Globally; UK/EU data centres for EU customers |
| Cloudflare Email Routing | Inbound email to *@omnia-inclusion.com | Email metadata + body | Globally distributed |
| Firecrawl | Fetching public web pages for the research library and legislation watch | Public URLs and public page content only; no school data | United States |
We do not engage any sub-processor in a country without adequacy or equivalent UK / EU Standard Contractual Clauses in place.
New data categories — June 2026
The following data categories were added in the June 2026 build sprint. They are processed by the sub-processors listed above within their existing scope.
Available Interventions Register: School-specific intervention programme data including staff names recorded as trained to deliver specific programmes. Stored in Supabase (Lovable Cloud). Programme names and delivery formats (not staff names) are included in AI plan generation context sent to Google Gemini on Vertex AI in London (UK).
Assessment platform import data: Scores and progress data imported from Lexia Core5, Nessy, Sparx Maths, DoodleLearning, TTRS, Emile, and other platforms. Stored in Supabase. Lexia Core5 exports which contain demographic fields (date of birth, gender, race) have those fields stripped server-side immediately on import — they are never stored or passed to any sub-processor.
Change log
- 29 October 2026 (later): voice transcription moved onto the staff member's own device. Google Cloud Vertex AI (London) added as the optional server fallback; recordings no longer go through the Lovable AI Gateway.
- 29 October 2026: corrected the AI section. Earlier versions named Anthropic as the provider for plan generation and said Google Gemini received search queries only. In fact Google Gemini is OMNIA's main AI provider and OpenAI is used for document search indexing only; Anthropic is used only when a school connects its own Anthropic account. Added Wonde, Google Workspace, Microsoft SharePoint/Entra ID and Firecrawl, which were in use but not listed. No new processing was introduced by this correction.
Questions
Email privacy@omnia-inclusion.com.
