Tally Reading: legal & compliance
Tally (trading as Tally Reading)
Last updated: 10 November 2026
This policy defines how long Tally Reading ("Tally") retains personal data processed on behalf of subscribing schools, and how that data is disposed of. It gives effect to the UK GDPR storage-limitation principle (Article 5(1)(e)): personal data is kept in identifiable form for no longer than is necessary for the purposes for which it is processed.
Tally processes personal data only as a data processor, on the instructions of school controllers. This policy covers data held in Tally's databases and caches (Cloudflare D1, KV and R2) and transient processing by third-party services.
The one exception is answers to the optional parent feedback survey, which Tally holds as controller, unlinked from any pupil and outside this processor policy, and keeps for 12 months (see the Privacy Policy, section 2.4).
Unless a school instructs otherwise, or a legal obligation requires longer retention, the following periods apply. "Subscription duration + 90 days" means data is retained while the school's subscription is active and for a 90-day grace period afterwards (to allow renewal or data export), after which it is permanently deleted.
| Data category | What it includes | Retention period | Disposal |
|---|---|---|---|
| Student records | Name, reading level/range, class, notes, likes and dislikes, genre preferences, last-read date, reading band; from the school's MIS where connected: year group, date of birth, gender, first language, SEN/EAL/FSM/pupil-premium status | Subscription duration + 90 days; a pupil removed by the school is permanently deleted 90 days after removal | Permanent deletion |
| Badges and derived reading statistics | Badges earned, totals of books/sessions/minutes, genres and authors read | Subscription duration + 90 days | Deleted with the student record |
| Latest AI book recommendations | The most recent set of AI-suggested books for a pupil (one per pupil, replaced each time) | Until replaced, or until the student record is deleted | Deleted with the student record |
| Parent portal access links | Link token, academic year, issue and revocation dates | Until revoked, or until the student record is deleted | Deleted with the student record |
| Celebration messages | Pupil first name and achievement shown in the in-app news ticker | 2 days | Automated daily cleanup |
| Reading sessions & streaks | Session date, duration, pages, assessment, rating, notes, book reference; streak counters | Subscription duration + 90 days | Deleted with the student record |
| Staff user accounts | Name, email or username, role, class assignments, last-login timestamp | Subscription duration + 90 days | Permanent deletion |
| Password hashes | PBKDF2 hash only (no plaintext) | Until the user account is deleted | Deleted with the user record |
| Refresh / password-reset tokens | Token hash, expiry, revocation/use timestamps | Deleted on expiry, use or revocation | Automated daily cleanup |
| Login attempts | Email, IP address, user-agent, outcome, timestamp | 30 days | Automated daily cleanup |
| Enquiries and support correspondence | Name, email address and message of the person who wrote in (a website enquiry, a school details form, or a support request from a school's staff); a school details form's answers: school facts and the names, roles and work contact details of the staff it names (no pupil data); Tally's email replies, with the sending address, the Tally staff member who sent each one and its delivery status; Tally's internal notes. Tally is the controller | Support requests from a school's staff: subscription duration + 90 days, deleted with the school's data. Website enquiries and school details forms with no school on Tally: 24 months after the last message in either direction, then deleted with our replies and notes. An enquiry Tally files with the school it sets up is deleted with that school's data instead. Deleted sooner on request | Permanent deletion |
| Audit logs | Actor, organisation, action, entity, timestamp, IP/user-agent | IP & user-agent anonymised after 90 days; entries deleted after 2 years | Automated (two-phase) |
| Rate-limit records | IP/user identifier, endpoint, timestamp | 1 hour | Automated daily cleanup |
| AI recommendation cache | Hashed reading-profile input mapped to AI response | 7 days (automatic expiry) | Platform TTL |
| Book-cover cache | Cover images (no personal data) | Up to 90 days | Platform lifecycle / client TTL |
| Organisation settings, classes, AI configuration | School name, timezone, thresholds, class details, encrypted API keys | Subscription duration + 90 days | Deleted with the organisation |
| Book catalogue | Title, author, ISBN, etc. (shared, non-personal) | Indefinite (not personal data) | n/a |
A nightly automated job applies these retention periods: it removes expired tokens and old login-attempt, rate-limit and audit records, anonymises older audit data, and permanently deletes organisations (and their data) that have been inactive beyond the grace period. A legal-hold flag suspends all automated deletion for an organisation where retention is legally required.
Schools, as controllers, may at any time:
Tally actions verified deletion requests promptly and, where deletion is requested, confirms completion in writing. Cached recommendation data referencing a deleted subject expires within 7 days.
Retention periods may be extended where required by law — for example, to comply with a legal hold or regulatory investigation, to establish or defend legal claims, or to meet safeguarding or financial record-keeping obligations. Anonymised, aggregated statistics that cannot identify any individual may be retained indefinitely.
This policy is reviewed at least annually (next review due February 2027), whenever a new category of data is introduced, on any sub-processor or legal change, and following any data-protection incident.