Trust and security
Data-protection review for your deployment
Prepare a deployment-specific data review: purposes, roles, hosting, access, integrations, retention, exports and contractual questions for Education Host.
Education Host operates in line with UK GDPR. Its published Privacy Policy describes its own data processing; an institutional platform also needs a review of the proposed data, purposes, roles, access, integrations and lifecycle. Confirm deployment-specific processing terms and institutional approvals before transferring real data or relying on the service.
Use the data review matrixWhat should an institutional data review establish?
Describe data categories and flows without sending the records in an initial enquiry. Use the matrix to identify the appropriate institutional reviewers and questions that need a scoped response. It is a review aid, not a completed impact assessment or data-processing agreement.
| Area | Starting point | Confirm with the institution and proposed service |
|---|---|---|
| Purpose and categories | The Privacy Policy describes Education Host's own processing | Platform purposes, people affected, necessary fields and any sensitive information |
| Roles and instructions | Institutional deployments have their own processing context | Controller/processor roles for each activity, documented instructions and applicable terms |
| Location and service chain | Managed hosting uses UK data-centre infrastructure at 6DG Birmingham Central | Locations and parties for the selected platform, backups, integrations and support; any transfers needing review |
| Access and identity | Role-based platform workflows; identity support varies by platform | Authorised users, sensitive-field visibility, support access and joiner/leaver controls |
| Retention and recovery | Lifecycle requirements depend on purpose and configuration | Schedules, holds, archives, backup expiry, recovery and restrictions on restored material |
| Exit and assistance | Deployment-specific arrangements are agreed during procurement | Exports, deletion/return, access removal, incident communications and handling institutional requests |
How do the data questions differ by platform?
Student hosting can involve account details, course/group membership and user-published websites. Cloud Pulse adds teaching-environment contents and the institution's image/workload choices. School workflows may involve staff absence or pupil/trip information. Describe the actual data required and the authorised roles for the selected workflow; do not assume every platform needs the same fields.
For school MIS connectivity, confirm the supported route, school permissions and available data during onboarding. Trip Manager medical information may include trip snapshots; review refresh and visibility for the workflow rather than assuming every screen is a live medical record. School policies and emergency procedures continue to apply.
What processing terms and documents should be reviewed?
Raise institutional contract, supplier-assessment and impact-assessment requirements during scoping. Identify the proposed activities, parties, data and service chain so the relevant terms can be reviewed. A public privacy notice does not settle every processing obligation for an institutional deployment.
ICO guidance explains the controller/processor contract context. Your institution's reviewers determine the documentation and approvals needed for its proposed use. Deployment-specific processing terms are confirmed during procurement; this page is not a published signed DPA or an assurance that an assessment has been completed.
What happens to data during recovery or service exit?
Agree separate purposes and controls for live data, assessment/operational records, archives and backups. Record how exports are delivered, which copies remain for an agreed purpose, how access ends and how expiry or removal is handled. Do not infer immediate deletion of every backup from deletion of one live account.
Review recovery as well as deletion: identify what a restore may reintroduce, who approves it and how the institution's current access and lifecycle decisions continue to apply. Test a representative export or recovery before the service becomes operationally critical.
What should be agreed before real data enters a pilot?
Nominate the institutional data-protection and service reviewers, record open questions and agree permitted data and access for the trial. Use approved test or minimised data where appropriate; a pilot is not an exemption from review. Escalate unresolved critical questions before live records are transferred.
- Purpose, categories, permitted users and access have been reviewed.
- Required contractual and institutional approvals are in place for the activity.
- Integration permissions, recovery, retention and wind-down are understood.
- Authorised contacts and the route for incidents or data-related requests are recorded.
Data-protection review for your deployment — frequently asked questions
Direct answers for IT, security, procurement and teaching teams.
Does UK hosting alone approve a platform for our data?
No. Location is one review area. Assess the purposes, categories, access, service chain, lifecycle, contract and institutional requirements for the selected deployment.
Is the Privacy Policy the same as our deployment's processing agreement?
No. The published Privacy Policy describes Education Host's own processing. The institution should confirm relevant roles, activities and deployment-specific processing terms during procurement.
Can we download a signed standard DPA from this page?
No signed standard DPA is published here. Raise your documentation requirements during scoping so the proposed processing terms and institutional review can be addressed.
Should we send pupil or student records with an initial enquiry?
Describe the categories, scale and intended workflow without sending records or credentials. Agree any later data transfer, permissions and safeguards through the institutional process.
Can every platform use the same retention period?
Retention depends on purpose and institutional requirements. Agree owners, schedules, exceptions and the handling of live, archive and backup copies for the selected service.
Does a pilot need data-protection review?
Agree the permissions, documentation and safeguards appropriate to the pilot before transferring real data. A trial does not by itself establish approval for a later wider deployment.
Every deployment starts with a conversation
Tell us about your institution, modules and requirements — we will answer the technical and commercial questions honestly, including where something is not the right fit.
