Tally Reading: legal & compliance

Data Retention Policy

Tally (trading as Tally Reading)

Last updated: 10 November 2026


1. Purpose and Scope

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).


2. Retention Schedule

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 categoryWhat it includesRetention periodDisposal
Student recordsName, 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 statusSubscription duration + 90 days; a pupil removed by the school is permanently deleted 90 days after removalPermanent deletion
Badges and derived reading statisticsBadges earned, totals of books/sessions/minutes, genres and authors readSubscription duration + 90 daysDeleted with the student record
Latest AI book recommendationsThe most recent set of AI-suggested books for a pupil (one per pupil, replaced each time)Until replaced, or until the student record is deletedDeleted with the student record
Parent portal access linksLink token, academic year, issue and revocation datesUntil revoked, or until the student record is deletedDeleted with the student record
Celebration messagesPupil first name and achievement shown in the in-app news ticker2 daysAutomated daily cleanup
Reading sessions & streaksSession date, duration, pages, assessment, rating, notes, book reference; streak countersSubscription duration + 90 daysDeleted with the student record
Staff user accountsName, email or username, role, class assignments, last-login timestampSubscription duration + 90 daysPermanent deletion
Password hashesPBKDF2 hash only (no plaintext)Until the user account is deletedDeleted with the user record
Refresh / password-reset tokensToken hash, expiry, revocation/use timestampsDeleted on expiry, use or revocationAutomated daily cleanup
Login attemptsEmail, IP address, user-agent, outcome, timestamp30 daysAutomated daily cleanup
Enquiries and support correspondenceName, 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 controllerSupport 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 requestPermanent deletion
Audit logsActor, organisation, action, entity, timestamp, IP/user-agentIP & user-agent anonymised after 90 days; entries deleted after 2 yearsAutomated (two-phase)
Rate-limit recordsIP/user identifier, endpoint, timestamp1 hourAutomated daily cleanup
AI recommendation cacheHashed reading-profile input mapped to AI response7 days (automatic expiry)Platform TTL
Book-cover cacheCover images (no personal data)Up to 90 daysPlatform lifecycle / client TTL
Organisation settings, classes, AI configurationSchool name, timezone, thresholds, class details, encrypted API keysSubscription duration + 90 daysDeleted with the organisation
Book catalogueTitle, author, ISBN, etc. (shared, non-personal)Indefinite (not personal data)n/a

3. Disposal Methods

  • Permanent deletion (hard delete): records are removed from the live database. Deleting a student or staff member cascades to all associated records. Tally also provides an organisation-level purge that permanently deletes all of a school's data across every related table and replaces the organisation record with an anonymised tombstone.
  • Anonymisation: where an accountability record must be kept (for example, audit logs), identifying fields are irreversibly removed while non-identifying data is retained. Properly anonymised data is no longer personal data.
  • Automatic expiry: caches and short-lived tokens expire automatically via platform mechanisms (database TTLs, object-storage lifecycle rules and browser storage expiry).

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.


4. Controller Requests

Schools, as controllers, may at any time:

  • request earlier deletion of their organisation's data, or of an individual student's data;
  • request an export of their data before deletion;
  • instruct Tally when a pupil leaves, so their data can be removed in line with the school's instructions.

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.


5. Exceptions

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.


6. Review

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.