Effective 30 October 2026 · Version 2026-11-10
Data-retention statement
The Shine School retention schedule and the deletion controls used for the service.
| Category | Retention |
|---|---|
| Raw phone GPS points | 30 days by default; a School Admin may set 1–90 days |
| Completed-trip route/stop coordinates | Redacted after 90 days; technical setting is 30–90 days |
| Notification delivery history | 90 days; technical setting is 30–90 days |
| Inactive push installations | Removed after 90 days; revoked immediately when access ends |
| Guardian accounts, bus pickup points and transport profiles | While active; delete or anonymize within 90 days after the relationship ends, subject to reviewed obligations |
| A child’s school records: their class, lesson registers, changes to them and parents’ calls | While the child attends the school, then about 5 years after they leave |
| Timetable, bell times, covers and when each register was first saved | While the school uses the service |
| Staff profiles, photos and teaching | While the person works at the school; after they leave, for a period the school is agreeing with Shine School |
| Staff time off and wipes with their reasons, and fingerprint clock-ins (device number and time) | While the person works at the school; after they leave, for the same period as their staff profile |
| Accounts with an in-app deletion request | Account and linked personal data deleted or anonymized within 30 days of the request, subject to an active hold or reviewed obligation |
| Security and administrative audit logs | While the school uses the service, designed without raw coordinates or unnecessary child information |
| Encrypted backups | No more than 35 days |
| Irreversibly aggregated statistics | May be retained when no school user, child, bus run, or pickup point can be identified |
Automated deletion and redaction
Retention jobs calculate fixed cutoffs, delete eligible location, heartbeat, delivery/provider, and inactive-installation records, redact old trip coordinates, and append category-level deletion evidence. A failed job rolls back its data changes. An authorized School Admin can pause scheduled deletion for their school; while it is paused, these jobs do not run for that school, and records past their period are deleted or redacted when it is resumed.
Accounts, pickup points and school records are not yet deleted automatically when a relationship ends; until that is added, they are deleted or anonymized on request (see the deletion page). Deletion counted from the day a child leaves, or a person stops working at the school, will be added before the first school records reach their period.
Holds and backups
An authorized School Admin may create a narrowly identified, reasoned hold with an expiry no more than one year away. Holds do not silently permit indefinite raw-location retention. Deleted production data may remain only until encrypted backups expire, no later than 35 days.
Contact [email protected] with a retention or deletion question. Effective date: 30 October 2026.