Privacy Notice
Version 1.0, effective 12 August 2026.
Last updated 10 November 2026
STARUCATION Privacy Notice
Version 1.0. This notice explains what personal data the STARUCATION platform collects, why, how long it is kept and the rights available to you. It applies to everyone who uses the platform: school leaders, staff, teachers, students and guardians. Where the platform processes student educational records on behalf of a school, the school is the data controller and the platform is its processor; the Student Data Addendum sets out those obligations in detail.
1. Who we are
The platform operator provides the STARUCATION academic platform to schools under a Master Services Agreement. Questions about this notice can be raised through the in-product Service Desk (category "Data") or with your school administrator, who can escalate to the platform's data protection contact.
2. Data we collect
Account data: name, email address, role, school, title and department, locale, sign-in timestamps.
Educational records (students): enrolments, attendance, submissions, grades and feedback, progress, risk assessments and support plans, credentials.
Family data (guardians): relationship to a student, contact details, fee and payment records.
Communications: internal mail, monitored student-teacher messages, announcements, form responses, support tickets.
Documents: files uploaded to the document vault and signature envelopes, with checksums and audit trails.
Technical data: IP address, user agent, device and browser characteristics, and request logs used for security and audit.
Payment data: invoice numbers, amounts, payment status and provider references. Card and bank details are entered directly with the payment provider and never stored by the platform.
3. Why we process data (legal bases)
To deliver the Service under the contract with your school (performance of a contract).
To keep the platform secure, prevent abuse and maintain immutable audit logs (legitimate interests).
To comply with legal obligations, including safeguarding duties and record-retention rules that apply to schools.
For student data, on the documented instructions of the school as controller. Where consent is required (for example for optional features), the school collects it and can withdraw it at any time.
4. Safeguarding
Messages between students and teachers are monitored for safeguarding phrases. Flagged messages are reviewed by the school's designated safeguarding lead; the platform sees only the number of open flags per school, never the messages. Flags and reviews are recorded in the audit log and retained with the school's records.
5. Sharing and subprocessors
We share data only with:
Your school and the people your school authorises.
Subprocessors that host or operate parts of the Service under written data-processing terms: a cloud infrastructure provider (data hosted in the region selected by the school, by default the United Kingdom or European Union), a transactional email provider, and the payment processors a school enables (Stripe, PayPal or an invoice gateway). The current subprocessor list is available from your school administrator; schools are notified thirty days before a new subprocessor is added.
Authorities where required by law or to protect the vital interests of a child.
We do not sell personal data and do not use student data for advertising or profiling unrelated to education.
6. International transfers
Where data leaves the hosting region, transfers rely on adequacy decisions or standard contractual clauses with supplementary measures. Schools may request the transfer assessment through the Service Desk.
7. Retention
Account data: for the life of the account and 90 days after closure.
Educational records: for as long as the school instructs, in line with its retention schedule; exported or deleted within 90 days of a school's termination.
Audit logs and safeguarding records: seven years, or longer where the school's legal obligations require.
Payment records: seven years for financial compliance.
Backups: rolling 35 days, after which deleted data is no longer recoverable.
8. Security
Data is encrypted in transit and at rest. Sensitive fields (for example bank details and emergency contacts) are additionally encrypted at the application layer. Access is role-based and tenant-isolated, sessions expire after twelve hours, and every consequential action is written to an immutable audit log with the actor's IP address.
9. Breach notification
If we become aware of a personal data breach affecting your school's data, we notify the school's principal and designated contact without undue delay and in any event within 48 hours of confirmation, with the nature of the breach, the categories and approximate number of records concerned, likely consequences and the measures taken. We support the school in meeting its own notification duties to authorities and to affected individuals within statutory deadlines (72 hours where the relevant regulation so requires).
10. Your rights
Depending on your jurisdiction you may have the right to access, correct, delete or export your personal data, to object to or restrict processing, and to complain to a supervisory authority. For educational records, requests are handled by your school as controller; the platform assists the school in responding within one month. Guardians may exercise these rights on behalf of their children as described in the Student Data Addendum.
11. Changes
We may revise this notice by publishing a new version and asking users to acknowledge it at their next sign-in. Previous versions remain available from your school administrator.