OMNIAInclusion
HomeFeaturesConnectionsEvidence basePricingInsightsFree ToolsAboutFAQContactSign in
All documents
Ask a question
OMNIA INCLUSION LTD

Privacy Policy

Version 1.5Updated 13 November 2026Live
OMNIA Inclusion

Last updated: 11 November 2026 Version: 1.3 (founding-schools draft; solicitor review pending before first paying contract)

Plain-English summary (not legally binding — the sections below are.)

  • Who we are: OMNIA Inclusion Ltd, a UK company building a SEND platform for schools.
  • What we collect: pupil + staff data the school chooses to put in OMNIA; technical logs; account contacts.
  • Why: to deliver the service the school has commissioned.
  • Our role: processor for pupil data (the school is controller); controller only for our own account contacts.
  • Where the data lives: EEA (Ireland, AWS eu-west-1). See sub-processors.
  • How long we keep it: see retention schedule.
  • Your rights: access, correction, deletion, portability, objection. Email privacy@omnia-inclusion.com — 30-day SLA.

1. Who we are

OMNIA Inclusion Ltd ("OMNIA", "we", "us") is a SEND-platform provider registered in England & Wales (company no. 17228173). Our registered contact for privacy matters is:

  • Privacy Lead: Chris Pressdee-Rudd (founder and Director)
  • Email: privacy@omnia-inclusion.com
  • Post: OMNIA Inclusion Ltd, 169 High Street, Marske-by-the-Sea, Redcar & Cleveland, TS11 7LN, United Kingdom (registered office)
  • ICO registration: no. 00014144622 (UK Information Commissioner's Office)

Other contacts:

  • dpo@omnia-inclusion.com — data-subject rights (access, rectification, erasure, portability)
  • security@omnia-inclusion.com — vulnerability disclosure / security researchers (see also /.well-known/security.txt)
  • complaints@omnia-inclusion.com — formal complaints about how we've handled your data or service
  • legal@omnia-inclusion.com — legal notices, contract queries, regulatory correspondence
  • omnia.abuse@omnia-inclusion.com — misuse, spam complaints, takedown requests

If we cannot resolve a complaint to your satisfaction, you have the right to escalate to the UK Information Commissioner's Office at https://ico.org.uk/make-a-complaint/.

We are not required under UK GDPR Art. 37 to appoint a Data Protection Officer; the founder acts as the named Privacy Lead and is the first point of contact for all data-protection enquiries.

2. Our role under UK GDPR

In almost all cases OMNIA acts as a data processor on behalf of the school, who is the data controller for pupil, parent and staff personal data they enter into the platform. The school determines what is recorded and why; we process it on their documented instructions, set out in the Data Processing Agreement (DPA) signed at onboarding.

We act as a data controller only for:

  • our own marketing list (people who register interest on this website)
  • our own staff and contractors
  • prospect / customer contact information for billing and support
  • how the platform is used: which pages and sections school staff open, counted per staff member and day, so we know what to improve. Nothing about pupils is recorded (every pupil's page counts as the same page), and a school can switch this off.
  • enquiries sent through this website's contact form: your name, email, school, role and message, your answer to the optional "How did you hear about OMNIA?" question, and how you arrived at the site (the tags on the link you followed, the website you came from and the first page you visited). The arrival details are held only in your browser's memory until you send the form; nothing is stored on your device for this.
  • trial copies: if you ask for a trial copy at /try, your name, work email, school, role, which example school you chose, your answer to "How did you hear about OMNIA?" and how you arrived. We create a sign-in account for your email and a private copy of an example school holding made-up pupils only. You must not enter real pupil, parent or staff data into a trial copy. We count the AI drafts the copy uses, to cap them.

3. What personal data we process (as processor, on behalf of schools)

  • Pupil identity: name, date of birth, year group, photo (optional), UPN, ULN, gender, language, SEND category, EHCP status

  • Pupil records: inclusion plans, PEEPs, access arrangements, parental consent, voice responses, intervention notes, assessment scores

  • Pupil-linked staff: keyworker, class teacher, SENCo allocations

  • Staff identity: name, work email, job title, role within the school

  • Parent contact: name, email, phone (only when entered for parent-voice or comms)

  • Audit logs: who read, exported or shared what, when

  • Available Interventions Register: your school's list of intervention programmes and the staff trained to deliver each programme. Used to filter AI plan suggestions to reflect your school's actual delivery capacity.

  • Assessment platform import data: scores and progress data imported from Lexia Core5, Nessy, Sparx Maths, DoodleLearning, TTRS, Emile, and other platforms as imported by your school. Lexia exports which contain demographic fields (date of birth, gender, race) have those fields stripped server-side immediately on import — they are never stored.

  • Allergies and medical needs, entered by the school's medical lead, SENCo or admin: known allergens; whether a pupil carries adrenaline, where it is kept and when it expires; Allergy and Asthma Action Plan dates and who issued them; whether a healthcare plan exists, who holds it and when it was last reviewed; the instructions staff follow in an emergency; parents' consent for the school's spare adrenaline to be used; and other medical conditions. Full healthcare plans stay in the school's own records.

  • Medical and dietary records from the school's MIS, copied through Wonde only when the school turns this on, so the medical lead can check them.

  • Behaviour incidents and achievements from the school's MIS, copied through Wonde only when the school turns this on: the type, date and time, outcome, location, comment, the pupil's role and the member of staff who recorded it. Only admins, SENCos and inclusion leads can see them. When staff start a behaviour support plan, OMNIA can suggest answers to the assessment questions (how often, where, when in the day) from these records and the school's own incident log. Staff check and edit the suggestions; only the answers they confirm are used to draft the plan with AI. The records themselves, their comments and staff names are not sent to AI.

  • Behaviour events and positive events from Go4Schools, for schools that connect it with their own Go4Schools key: the type, date and time, subject, action taken and comment. They are shown alongside MIS behaviour on the pupil's profile, with an incident recorded in both counted once, and are used the same way for behaviour support plan suggestions. They are not sent to AI.

  • A combined week-by-week view of a pupil's attendance, behaviour, results, support and key events (such as a suspension or a plan review), built from the records above. Only admins, SENCos and inclusion leads can see it. It states what changed and when; it does not score pupils or predict anything. To build it, attendance marks are copied from the MIS from the start of the school year. When writing a plan or behaviour support plan, a lead can tick individual counted lines from this view (for example "After lunch: 7 of 10 incidents with a time recorded") to inform the AI-assisted draft. Only the ticked lines are sent, checked by OMNIA against its own count; names, comments and the records themselves are not.

  • Reports of medical incidents and near misses (for pupils, staff or visitors), recorded by school staff, and what the school did afterwards.

  • Allergy safety records for the whole school: staff allergy-awareness training dates, spare adrenaline pens and inhalers, and the school's allergy policy details.

Medical and allergy information is shown only to the people who need it: staff who teach a pupil see the pupil's allergens, where their adrenaline is kept and what to do in an emergency; other conditions and the full record are seen only by the medical lead, SENCo and admin. None of it is sent to AI services.

We avoid collecting special-category data beyond what is operationally necessary for SEND planning (e.g. health and disability information that the school already lawfully holds for safeguarding and inclusion).

4. What personal data we process as controller

  • Marketing-list: name, email, school, role, free-text message
  • Billing: invoicing contact name, email, school billing address
  • Support: contents of any email or in-app message you send us

5. Lawful basis

ProcessingBasis
Pupil and staff data (on behalf of school)School's basis under UK GDPR Art. 6(1)(e) public task, with Art. 9(2)(g) substantial public interest for special-category data
Marketing listConsent (Art. 6(1)(a)) — you opt in on this website
Billing / contract adminContract performance (Art. 6(1)(b))
Platform usage counts (pages and sections staff open)Legitimate interest (Art. 6(1)(f)): improving the service; schools can switch it off
Website enquiries, including how you heard about us and how you arrivedLegitimate interest (Art. 6(1)(f)): replying to you and knowing which ways of reaching schools work
Trial copies: your account and request detailsSteps at your request before a contract (Art. 6(1)(b)): giving you the trial you asked for; legitimate interest (Art. 6(1)(f)) for one follow-up
Service security and abuse-prevention logsLegitimate interest (Art. 6(1)(f))

6. Where data is stored

All personal data processed by OMNIA is stored within the European Economic Area (EEA) on Supabase infrastructure at AWS eu-west-1 (Ireland). Transfers from the United Kingdom to Ireland are covered by the UK Government's adequacy regulations for the EEA. No additional safeguards or Standard Contractual Clauses are required for this transfer.

For schools in the UAE: the Republic of Ireland is on the UAE Data Office's accepted list for cross-border transfers. No additional safeguards are required for UAE school data stored in Ireland.

OMNIA does not store personal data in any country outside the EEA.

Operational detail:

  • Database and storage: AWS eu-west-1 (Ireland), via Lovable Cloud (Supabase). Encrypted at rest (AES-256) and in transit (TLS 1.2+).
  • Application runtime: Cloudflare Workers (edge). No pupil data is persisted at the edge; request bodies pass through in memory only.
  • AI calls (standard mode): Google Gemini on Vertex AI in London (UK, europe-west2), under OMNIA's own Google Cloud agreement. This covers plan and target drafting, summaries, translation and document search indexing. Text is passed through OMNIA's server-side PII scrubber first (pupil and staff names, UPN/ULN, NI numbers, addresses, postcodes, emails, phone numbers, dates); it is best-effort. Anthropic is used only when a school connects its own Anthropic account (BYOK). The only AI traffic still routed outside the UK/EEA is the in-app support assistant, which searches OMNIA's help pages and holds no pupil records. See /legal/sub-processors.
  • Voice transcription: recordings are transcribed on the staff member's own device, so the audio doesn't leave it. If a device can't, and the school allows it, Google Cloud Vertex AI transcribes the recording in London (UK), or the school's own Gemini account does if it has one. Schools can switch that fallback off.
  • AI calls (BYOK mode, opt-in for any school): routed to the school's own Anthropic, Azure OpenAI, OpenAI or Google Gemini account in the school's chosen region (document search indexing stays on OMNIA-managed AI where the school's provider can't do it) (e.g. UAE North, UK South). That region may be outside the UK and EEA — the school chooses and accepts that residency decision under its own DPA with the provider. The school's API key is AES-256-GCM encrypted at rest and never returned to the browser.
  • Specialist Support Prompts: read only data the school has already documented in OMNIA; surface professionally-framed prompts to qualified staff; never visible to parents or pupils; never make clinical claims; every accept / reject logged in the audit trail.
  • Email: transactional email is sent via the school's own Microsoft 365 tenant where the Microsoft Graph integration is enabled, or via our transactional provider.

7. How long we keep it

For pupil data we follow the school's retention instructions; our default retention rules are documented at /legal/retention. Headline:

  • Pupil record: on roll + 7 years
  • Plan share-link views: 180 days
  • Audit log: 730 days
  • Marketing list: until you unsubscribe, or 24 months of inactivity
  • Trial copy and the account made for it: deleted when the 30-day trial ends; your request details (name, email, school, role, how you heard about us) kept for 24 months so we know you have had a trial
  • Available Interventions Register: duration of subscription + 90 days

8. Your rights

If you are a data subject whose data is held in OMNIA on behalf of a school, please contact your school first — they are the controller. We will support the school in fulfilling any rights request (access, rectification, erasure, restriction, portability, objection). The platform includes a Download data pack and Erase pupil record action for SENCo / admin users.

For data we hold as controller (marketing, billing), email privacy@omnia-inclusion.com.

You have the right to complain to the UK Information Commissioner's Office (https://ico.org.uk) at any time.

9. Security

A summary of our technical and organisational measures is at /legal/security. Highlights: Row-Level Security per school, mandatory MFA for admin roles, hashed PINs for public links, tamper-evident audit log, secret rotation policy, and a published DPIA.

10. Cookies

We use only essential cookies — see /legal/cookies.

11. Changes to this policy

We will email schools at least 14 days before any material change to this policy. The current version and changelog live at this URL.


Version history

VersionDateChange
1.018 May 2026Initial publication.
1.11 June 2026Added BYOK (Anthropic / Azure OpenAI) AI routing and region disclosure; added Specialist Support Prompts disclosure.
1.229 October 2026Corrected the AI provider description: Google Gemini is the main AI provider and OpenAI is used for document search indexing only; Anthropic only via a school's own key. Clarified scrubbing coverage (voice audio can't be scrubbed).
1.311 November 2026Section 3: added allergies and medical needs, MIS medical and dietary records (via Wonde, when the school turns it on), medical incident reports and school allergy safety records, who can see them, and that none of it is sent to AI.
1.412 November 2026Section 3: added behaviour incidents and achievements from the school's MIS (via Wonde, when the school turns it on), who can see them, and how recorded incidents can suggest behaviour support plan answers that staff confirm before any AI drafting; the records themselves are not sent to AI. Added behaviour and positive events from Go4Schools, used the same way, and the combined week-by-week view for leads, with counted lines a lead ticks used in AI-assisted plan drafts. Section 2 and 5: website enquiries, including how you heard about us and how you arrived, and platform usage counts.
1.513 November 2026Sections 2, 5 and 7: trial copies. What we keep when you ask for one, the lawful basis, that a trial copy holds example data only, and that the copy and its account are deleted when the 30 days end.
This document is published by OMNIA Inclusion Ltd and is subject to change. For the current version visit omnia-inclusion.com/legal/privacy.
OMNIA Inclusion Ltd
Company no. 17228173 · ICO: 00014144622
omnia-inclusion.com · hello@omnia-inclusion.com
© 2026

OMNIA

Every SEND decision, grounded in evidence.

Product

  • Features
  • Pricing & ROI
  • Get started
  • Trust & Security
  • Insights

For your school

  • England (EHCP)
  • Wales (ALN)
  • Scotland (ASN)
  • Northern Ireland (SEN)
  • Ireland (NCSE)
  • UAE (ADEK)
  • Dubai schools (KHDA)
  • Qatar (MOEHE)
  • Australia (NDIS)
  • New Zealand (ORS)
  • United States (IDEA/504)
  • IB World Schools
  • Multi-Academy Trusts

Guides & comparisons

  • All guides
  • Provision mapping guide
  • SEN support plan vs pupil passport
  • SEND management software
  • Provision Map comparison & migration guide

About OMNIA

  • About
  • Evidence base
  • Founding schools
  • Frameworks & acknowledgements
  • FAQ
  • Legal
  • Accessibility
  • hello@omnia-inclusion.com

© 2026 OMNIA Inclusion Ltd · Registered in England & Wales · Company no. 17228173 · ICO registration no. 00014144622