Ortonomi✚ Ortonomi Report · Beta

Supported beta agreement and processing schedule

DRAFT — not ready for signature. The separate Ortonomi provider company and participating academy / trust have not yet been identified. Complete the parties, supplier schedule, retention and recovery arrangements before agreement or activation. Registration does not accept this draft.

1. Parties and scope

Provider: full registered name, company number, registered address and privacy contact to be completed. Controller: academy / trust legal name, address and authorised contact to be completed. Product: Ortonomi Report supported beta for agreed school locations. Proposed term: four weeks from agreed activation, with any extension recorded in writing. Pilot charge: to be agreed; no payment commitment arises from this draft.

2. Use and responsibilities

The beta supplies incident capture, investigation records, action tracking, manual escalation and exports. The controller appoints report-monitoring and incident-response owners, grants access on a need-to-know basis, verifies information and fulfils its reporting duties. The beta is not an emergency channel, automatic notification service, legal decision-maker or guarantee against liability. AI guidance and integrated RIDDOR advice are outside the current shared-workflow beta. Agree a fallback process for downtime.

3. Documented instructions

The provider will process incident information only on the controller's documented instructions for delivering and supporting this service, including any international transfer, unless required by UK law. Where permitted, it will inform the controller before legally required processing and inform the controller if an instruction appears to infringe applicable data-protection law. The provider will not use incident records for advertising or model training.

4. Processing description

Subject matter: school hazard, near-miss and accident records and related investigations and actions. Nature: collection, storage, retrieval, organisation, restricted disclosure to authorised users, export, correction and deletion on instructions. Purpose: incident management and learning. Duration: agreed beta term plus the completed exit and backup-deletion period. Data subjects: pupils, staff, contractors, visitors, reporters, witnesses and account users. Data types: identities / contact details where necessary, circumstances, injury / treatment information, photos, witness statements, findings and actions. Health information is special category data. Criminal-offence data and unrelated sensitive information are outside scope unless separately agreed.

5. Confidentiality and security

The provider will ensure authorised personnel are bound by confidentiality and implement appropriate technical and organisational measures under Article 32. The schedule must describe account and administrator controls, tenant isolation, private file storage, secure transmission, access review, incident handling, backup and tested restoration. Shared incident data is protected by database policies and uploads use restricted access. This draft does not represent a completed security certification or recovery test.

6. Sub-processors and transfers

Obtain the controller's prior specific or general written authorisation for sub-processors. Impose equivalent Article 28 obligations and remain responsible for their compliance. Under general authorisation, notify intended changes with a reasonable opportunity to object. Before agreement, list the exact contracting entities, processing purposes, locations, supplier DPAs and any required transfer safeguards: Supabase (database, authentication and private uploads); Vercel (web hosting); the configured email delivery provider (sign-in messages); and relevant supplier dependencies. CDN requests deliver browser libraries; they do not receive uploaded report contents through the app's extraction flow. Browser speech services are excluded from real-data use in this beta.

7. Rights, breaches and assistance

The provider will take appropriate measures to assist the controller with individual-rights requests and obligations concerning security, personal-data breach notification, DPIAs and prior consultation, taking account of the processing and available information. Notify the controller without undue delay on becoming aware of a personal-data breach, supply known facts and updates, and cooperate in investigation and remediation. Contact and escalation arrangements must be completed before activation.

8. Retention and exit

The controller sets the retention schedule and identifies any legal holds. No automatic purge is implemented. At termination the provider will, at the controller's choice, return or delete the personal data and delete existing copies unless UK law requires storage. Agree export format, completion times, verification, treatment of staged / abandoned uploads and the backup deletion cycle. Backups awaiting expiry must be protected and beyond routine use. Do not insert an unsupported retention period.

9. Evidence and audit

The provider will provide information necessary to demonstrate compliance with Article 28 and allow and contribute to audits and inspections by the controller or its appointed auditor. Maintain the agreed processing instructions, access reviews and security / incident records. Operational incident histories in the current app are not a comprehensive immutable security audit log.

10. Controller responsibilities

The controller determines the lawful basis and any special-category condition, provides appropriate privacy information, assesses any DPIA requirement, sets permissions and minimises the information collected. It retains responsibility for investigations, care, statutory reporting and decisions. The provider must maintain its own applicable obligations; those are not transferred to the school.

11. Acceptance and activation record

Record authorised signatories for both parties, date, agreed document version, processing instructions, school locations, supplier / transfer schedule, retention and recovery schedule and support contacts. Real-data activation is a separate provider-controlled step tied to that agreement reference. No academy account can enable itself through the public app.

Reference: ICO guidance on controller–processor contracts, checked 5 October 2026.

Return to beta information