Tally Reading: legal & compliance

Sub-Processor Register

Tally (trading as Tally Reading)

Last updated: 23 September 2026


1. Purpose

This register records all sub-processors engaged by Tally Reading ("Tally", "we", "us") in connection with the processing of personal data on behalf of subscribing schools (data controllers). It is maintained in accordance with Article 28(2) of UK GDPR and the obligations set out in the Data Processing Agreement (DPA) between Tally and each school.

Schools, as data controllers, have the right to be informed of all sub-processors and to object to the appointment of new or replacement sub-processors.


2. Definitions

TermMeaning
ControllerThe subscribing school that determines the purposes and means of processing personal data
ProcessorTally Reading, which processes personal data on behalf of the controller school
Sub-processorA third party engaged by Tally to carry out specific processing activities on behalf of the controller
DPAData Processing Agreement between Tally and a controller school
BYOKBring Your Own Key -- the school provides its own API key to enable an optional feature
IDTAUK International Data Transfer Agreement
SCCsStandard Contractual Clauses (EU)

3. Sub-Processor Register

3.1 Core Sub-Processors

These sub-processors are engaged for all schools using the Tally platform.

Sub-processorPurposeData ProcessedLocationDPA StatusTransfer Mechanism
Cloudflare, Inc.Application hosting (Workers serverless compute), SQL database (D1), key-value storage (KV), object storage (R2), CDN and content delivery, DDoS protection, DNS, Email RoutingAll personal data: student records (names, reading levels, preferences, reading sessions), staff user accounts (names, emails, hashed passwords), audit logs (IP addresses, user-agents, actions), authentication tokens (hashed), organisation settings, book catalogue dataGlobal edge network. D1 database can be configured for EU/UK jurisdiction.Cloudflare standard DPA (available at https://www.cloudflare.com/cloudflare-customer-dpa/).UK adequacy decision for EU transfers. UK IDTA / EU SCCs for US transfers.
Functional Software, Inc. (Sentry)Error and performance monitoring for the web app and APITechnical diagnostics captured when a fault occurs or a request is sampled: error messages, stack traces, request paths, browser and device type, staff user id and organisation id. Recorded screen sessions (a small sample) have all text masked and media blocked. Parent portal links, sign-in secrets and fields that look like names, dates of birth or contact details are removed before anything leaves the browser or server. Reading records are not sent.EU (Frankfurt ingest, sentry.io de region)Sentry's standard Data Processing Addendum (https://sentry.io/legal/dpa/).UK adequacy decision for EU storage. EU SCCs / UK IDTA addendum for any US support access.

Note on Cloudflare: Cloudflare is the primary infrastructure provider. All data processed by the Tally platform transits Cloudflare infrastructure. Cloudflare holds ISO 27001, SOC 2 Type II, and PCI DSS certifications. Cloudflare maintains its own sub-processor list at https://www.cloudflare.com/cloudflare-sub-processors/.

3.2 Optional Sub-Processors (AI features)

These sub-processors are only engaged when a school actively opts in. The feature is disabled by default, and a school may enable it in either of two ways, which differ in who contracts with the AI provider:

  • School's own API key. The school supplies its own key. The school enters into its own contractual relationship with the provider and is responsible for its own international transfer compliance. Tally holds no contract with the provider on the school's behalf.
  • Tally's paid AI add-on. Tally makes the requests using Tally's own provider account. In this case the provider is a sub-processor to Tally, and Tally's own agreement and transfer mechanism with that provider apply.

The data sent is identical in both cases (see the data-minimisation note below).

Sub-processorPurposeData ProcessedLocationDPA StatusTransfer Mechanism
Anthropic (Claude AI)AI-powered book recommendations, and AI summaries of aggregate reading statistics (both optional)Pseudonymised reading profile: reading level (AR min/max), a two-year age band derived from the year group, genre preferences, likes/dislikes, list of books previously read (title, author, genre). No student names or other directly identifying data are sent.USBYOK: the school's own DPA with Anthropic, the school being the contracting party. AI add-on: Tally's DPA with Anthropic, Anthropic acting as a sub-processor to Tally.BYOK: school responsible as controller, and must ensure its own international transfer compliance. AI add-on: covered by Tally's transfer mechanism with the provider.
OpenAI (ChatGPT)As Anthropic above (alternative provider, optional)Same data as Anthropic (above)USSame two-path model as Anthropic: the school's own DPA under BYOK, or Tally's DPA with OpenAI under the AI add-on.BYOK: school responsible as controller. AI add-on: covered by Tally's transfer mechanism.
Google (Gemini)As Anthropic above (alternative provider, optional)Same data as Anthropic (above)US / GlobalSame two-path model as Anthropic: the school's own DPA under BYOK, or Tally's DPA with Google under the AI add-on.BYOK: school responsible as controller. AI add-on: covered by Tally's transfer mechanism.

Data minimisation: Student names are not included in AI recommendation prompts. Only pseudonymised reading-profile data (reading level, genre preferences, and book history) is sent to AI providers. No directly identifying personal data is shared with any AI sub-processor.

AI statistics summaries: A school leader may ask for a written summary of the reading figures shown on the school's statistics page. Only whole-school or whole-class totals are sent. In full, that is: the school's name; today's date and the school's term dates, so the summary can tell term time from a holiday; the class or period being viewed; the number of pupils and of reading sessions; how sessions split between home and school; this week's and last week's totals; sessions per day of the week; how many pupils fall into each reading status; how many pupils have no sessions; streak counts and lengths; how many pupils sit in each reading band; and the titles of the most-read, most-liked and least-liked books.

No pupil names, pupil identifiers, dates of birth, or demographic characteristics are included, and no information about any individual pupil is sent. Summaries are refused outright for any view containing fewer than five pupils, so the totals always describe a group rather than a child. Because only the school's own name, its calendar and aggregate counts leave the platform, this feature does not transmit personal data to the AI provider.

Note for schools bringing their own Google (Gemini) key: Tally calls Gemini through Google's standard Generative Language API. On a free-tier Google key, Google may use prompts to improve its products and keeps logs for longer. Use a paid-tier (billing-enabled) key, which Google does not use for training, or choose Anthropic or OpenAI instead. Tally sends no pupil names or identifiers in any case (see the data column above).

3.3 Transactional Email

Tally uses Cloudflare Email Routing for all transactional email (such as password-reset and account notifications). This is covered under the Cloudflare DPA (Section 3.1 above). No separate email sub-processor is currently engaged. If another email provider is adopted in future, an appropriate data processing agreement will be obtained before any personal data is processed.

3.4 Third-Party Services (No Personal Data Processed)

The following services are used by Tally but do not process personal data and therefore do not constitute sub-processors under UK GDPR. They are listed here for transparency.

ServicePurposeData SentPersonal Data?
OpenLibrary (Internet Archive)Book metadata and cover image retrievalISBN, book title, book authorNo. Only book catalogue data is sent. No student, user, or school data is transmitted.

4. Change Notification Procedure

4.1 Advance notice

In accordance with our Data Processing Agreement, Tally will provide subscribing schools with at least 30 calendar days' written notice before engaging any new sub-processor or replacing an existing sub-processor that processes personal data.

Notice will be provided by:

  1. Email to the school's designated administrative contact (the email address associated with the admin or owner account); and
  2. Update to this Sub-Processor Register, with the new entry clearly marked as "Pending -- effective [date]".

4.2 Content of notice

Each notification will include:

  • The name of the proposed sub-processor
  • The purpose of the processing
  • The categories of personal data to be processed
  • The location of processing
  • The proposed effective date
  • A summary of the data protection safeguards in place (DPA status, transfer mechanism, certifications)

4.3 Controller's right to object

Schools have the right to object to the appointment of a new or replacement sub-processor within the 30-day notice period. Objections must be submitted in writing to privacy@tallyreading.uk.

Upon receiving a valid objection, Tally will:

  1. Acknowledge the objection within 5 working days;
  2. Engage with the school to understand and, where possible, address the concerns raised;
  3. If the concerns cannot be resolved, either: (a) withdraw the proposed sub-processor appointment; or (b) offer the school the option to terminate the DPA and subscription without penalty, with data return or deletion as specified in the DPA.

4.4 Emergency changes

In exceptional circumstances where a sub-processor change is required urgently (for example, to maintain the security or availability of the service), Tally may implement the change with less than 30 days' notice. In such cases, schools will be notified as soon as reasonably practicable and will retain the right to object as described above.


5. Sub-Processor Due Diligence

Before engaging any new sub-processor, Tally will:

  1. Assess the sub-processor's technical and organisational security measures;
  2. Verify that the sub-processor can comply with the data protection obligations set out in our DPA with schools;
  3. Ensure that an appropriate data processing agreement is in place with the sub-processor;
  4. For international transfers, verify that an appropriate transfer mechanism is in place (UK IDTA, SCCs, or adequacy decision);
  5. Document the due diligence assessment and retain it for audit purposes.

6. Review Schedule

This register is reviewed:

  • At least annually (next review due: February 2027)
  • Whenever a sub-processor is added, removed, or materially changed
  • Upon request by a controller school