Academic Intelligence
DPIA Support Documentation
Version: 1.0
Effective date: 12 May 2026
Website: checkitquick.academicintelligence.co.uk
Service provider: Academic Intelligence Ltd
Registered office: 60 Viceroy Court, 36 Dingwall Road, Croydon, England, CR0 2NG
Company number: 17204358 (Companies House)
Contact email: [email protected]
Privacy contact: [email protected]
Security contact: [email protected] (include Security incident in the subject for incidents)
Hosting location: London, United Kingdom
The full DPIA Support Documentation (all sections, templates and tables) is published on the CheckItQuick service at checkitquick.academicintelligence.co.uk/Home/DpiaSupportDocumentation. The summary below may be reproduced on your website or in supplier paperwork.
Short summary
checkitquick.academicintelligence.co.uk supports schools with their DPIA process by providing information about data flows, hosting, retention, subprocessors, security controls and risks. The Service is hosted in London, United Kingdom. It does not intentionally retain parent or pupil records. It stores only the information needed to operate the integration, including school configuration, school URLs, iSAMS/API URLs, API keys/secrets, SSO settings, Google-auth-linked user accounts, user email addresses, logs and support records. Schools remain the controller for school, parent and pupil data and should complete their own DPIA before enabling the Service.
Data flow summary (high level)
| Flow | Summary |
|---|---|
| Browser ↔ CheckItQuick | HTTPS to the application (UK-region hosting). |
| Browser ↔ MySchoolPortal | SSO as configured by the school. |
| CheckItQuick ↔ iSAMS | Configured API for read/write-back per school settings. |
| Configuration/logs → PostgreSQL (Neon) | Operational data store — not an MIS replica. |
| Email / billing / CI | Brevo, Zoho mailboxes, Stripe, GitHub as described in the Subprocessor list. |
School checklist (before go-live)
- Confirm lawful basis (and Article 9 basis if special category fields are exposed).
- Update the school privacy notice if needed.
- Minimise iSAMS API scope and field exposure.
- Decide approval routes for write-back to iSAMS.
- Test with non-live records where possible.
- Nominate privacy/security contacts and agree offboarding / credential rotation.
Related documents
- Privacy Policy
- Cookie Policy
- Terms of Service
- Data Processing Agreement
- Security Overview
- Data Retention & Deletion Policy
- Breach notification process
- Subprocessor list
Static mirror last updated: 12 May 2026.