Tally Reading: legal & compliance
Tally (trading as Tally Reading)
Last updated: 16 November 2026
Tally Reading (“Tally”, “we”, “us”, “our”) provides a cloud-based reading management platform designed for UK primary schools. Schools use Tally to track pupil reading progress, manage book libraries, and optionally generate AI-powered book recommendations.
| Detail | Value |
|---|---|
| Product name | Tally (trading as Tally Reading) |
| Website | https://tallyreading.uk |
| Company name | Scratch IT LTD |
| Company number | 08151576 |
| Data Protection Officer | Sam Castillo (sam@tallyreading.uk) |
| ICO registration number | ZC098130 |
Under UK GDPR, each school that subscribes to Tally acts as the data controller for the personal data of its pupils, staff, and other users. Tally acts as a data processor, processing personal data on behalf of and under the instructions of each school. This relationship is governed by a separate Data Processing Agreement (DPA) between Tally and each subscribing school.
Where Tally processes personal data for its own purposes (for example, managing school administrator accounts, billing, maintaining the security of the platform, answering enquiries and support requests, and collecting optional feedback from parents on the parent reading page), Tally acts as an independent data controller.
We collect and process different categories of personal data depending on your relationship with Tally.
Schools enter the following data about their pupils into the platform:
| Category | Data fields |
|---|---|
| Identity | First name, surname (or combined display name as entered by the school) |
| Reading profile | Minimum and maximum reading level (Accelerated Reader levels 1.0 to 13.0), age range |
| Preferences | Likes and dislikes (free-text lists), favourite genre preferences |
| Reading sessions | Date, duration, number of pages read, location (school or home), teacher assessment notes (free text), enjoyment rating (1 to 5), book read |
| Progress data | Current book, reading streak (current and longest), streak start date |
| Teacher notes | Free-text observations recorded by the teacher |
| Class membership | Assignment to one or more classes within the school |
Important: Tally does not knowingly collect pupil email addresses, dates of birth, home addresses, or photographs. Schools are responsible for ensuring that free-text fields (such as teacher notes, likes, and dislikes) do not contain inappropriate or excessive personal data.
| Category | Data fields |
|---|---|
| Identity | Full name |
| Contact | Email address |
| Authentication | Password (stored as a salted hash using PBKDF2 with 100,000 iterations; the plaintext password is never stored or logged) |
| Role and organisation | Assigned role (owner, admin, teacher, or read-only), school/organisation membership |
| Activity | Login timestamps, last-active timestamps |
| Category | Data fields |
|---|---|
| Audit logs | IP address (derived from the cf-connecting-ip header provided by Cloudflare), user-agent string, action performed, entity affected, timestamp |
| Rate-limiting records | Hashed identifier, endpoint, timestamp (used to prevent brute-force attacks on authentication endpoints) |
| Request logs | Standard HTTP request metadata processed by Cloudflare in the course of delivering the service |
The parent reading page may now and then ask whoever is using it two questions: are you enjoying using Tally, and do you find it useful? Each is answered Yes, Somewhat or Not really, and there is room for an optional comment of up to 500 characters. Answering is voluntary. You can choose No or Later instead, and nothing else on the page changes either way.
The survey is anonymous. We store the two answers, the comment, the date and which school's parent page they came from. Nothing we store links them to your child, your parent link or any account, and we do not ask for your name or contact details, so we cannot pick out one person's answer unless they quote their comment to us. Please don't put anyone's name in the comment. Your browser remembers whether you have answered or declined so that you are asked only once; that record stays on your device (see Section 9.2).
Tally is the controller for these answers, and relies on its legitimate interests (Article 6(1)(f)) in finding out whether Tally works for families and making it better. Your child's school does not receive your answers. Only the Tally team reads them. They are kept for 12 months, or deleted sooner if your child's school stops using Tally and its data is deleted (see Section 7). Questions about them go to Tally, not the school (see Section 8).
When you write to us through the form on our website, or a member of staff sends a support request from inside Tally, we keep what you sent: your name, your email address, your message and the date. When we reply by email, we keep a copy of the reply, which of our addresses it came from, who on the Tally team sent it, and whether it was delivered. We may also keep short internal notes about the request, which are never sent to you. When you answer one of our emails, your answer is kept on the same record: its text, the address it came from and the names of any attachments. The attachments themselves are not kept there; a copy of your email goes to our own mailbox. Replies are sent through Cloudflare's email service (see Section 5.4).
When a school asks to try Tally, we may send a link to a school details form. It asks for facts about the school (name, address, URN, phone, trust or local authority, the systems it uses and the shape of the trial) and for the names, roles and work contact details of school staff: the person filling it in, the person who will accept the data processing agreement for the school, and optionally the school's data protection officer and billing contact. It asks for no information about pupils. What you send is kept with the enquiry it answers.
If someone at your school named you on that form, we got your details from them, not from you. We use them only to set up the trial the school asked for and to send the data processing agreement to the right person. The form asks the person filling it in to confirm they have told you they are sharing your work contact details with us, and this section is the information UK GDPR (Article 14) says you should have. You can ask us to correct or delete your details at any time (see Section 8).
Tally is the controller for this correspondence, including the contact details of people at schools that do not use Tally yet and of staff named in a school details form. We rely on our legitimate interests (Article 6(1)(f)) in answering the people who write to us, setting up a service a school has asked for, and keeping a record of what we said. We do not use enquiries for marketing and we do not add you to a mailing list. How long we keep it is in Section 7.
UK GDPR requires that every processing activity has a lawful basis. The table below sets out the lawful basis we rely on for each purpose.
| Purpose | Data used | Lawful basis | Notes |
|---|---|---|---|
| Providing the reading management service to schools | Pupil data, staff user data | Article 6(1)(b): Contract | Processing is necessary to perform the contract between Tally and the subscribing school. |
| User authentication and session management | Email, password hash, authentication tokens | Article 6(1)(b): Contract | Necessary to provide secure access to the service. |
| AI-powered book recommendations (optional) | Pupil reading level, preferences, likes/dislikes, books read, genre preferences | Article 6(1)(b): Contract with Article 6(1)(a): Consent as a secondary basis at the school level | Schools actively opt in by configuring their own AI API keys. Individual recommendations are triggered by teacher action. See Section 5.2 for details. |
| Audit logging and security monitoring | IP address, user-agent, action details | Article 6(1)(f): Legitimate interests | Our legitimate interest in maintaining the security and integrity of the platform and detecting unauthorised access. |
| Rate limiting on authentication endpoints | Hashed IP/identifier, timestamp | Article 6(1)(f): Legitimate interests | Our legitimate interest in preventing brute-force attacks. |
| Sending password-reset and welcome emails | Email address | Article 6(1)(b): Contract | Necessary to operate the account system. |
| Calculating and displaying reading streaks | Reading session dates | Article 6(1)(b): Contract | Core product feature for tracking reading progress. |
| Answering enquiries and support requests, and setting up a trial a school asks for | Name, email address, message, our replies and notes; the school details form: school facts and the names, roles and work contact details of the staff it names | Article 6(1)(f): Legitimate interests | Not used for marketing. Staff named on the form by a colleague are told about it (Article 14). See Section 2.5. |
| Optional parent feedback survey | Survey answers, optional comment, date, school. Not linked to any child, parent link or account | Article 6(1)(f): Legitimate interests | Voluntary and anonymous. Read only by Tally, to learn whether the service works for families. Not shared with the school. See Section 2.4. |
| Platform improvement and bug fixing | Aggregated, anonymised usage patterns | Article 6(1)(f): Legitimate interests | We do not use identifiable personal data for this purpose. |
Where we rely on legitimate interests (Article 6(1)(f)), we have conducted a Legitimate Interests Assessment (LIA) and concluded that the processing is necessary and proportionate, and that it does not override the rights and freedoms of data subjects (including children).
Tally processes personal data relating to children (typically aged 4 to 11 in UK primary schools). We take the following additional measures to protect children’s data:
We share personal data only with the third parties set out below, and only to the extent necessary for the stated purpose.
| Detail | Value |
|---|---|
| Provider | Cloudflare, Inc. (US-headquartered, with UK/EU data regions available) |
| Services used | Workers (serverless compute), D1 (SQL database), KV (key-value storage), R2 (object storage), CDN, DNS, email routing |
| Data shared | All data processed by the platform passes through Cloudflare infrastructure |
| Safeguards | Cloudflare is certified under ISO 27001 and SOC 2 Type II. For international transfer safeguards, see Section 6. |
| Data region | D1 database located in Western Europe (Germany) with location_hint=weur and replication off. Workers compute and CDN operate globally. Cloudflare DPA v6.3 covers international transfers (EU SCCs + UK IDTA). Cloudflare is certified under the EU-US Data Privacy Framework + UK Extension. |
| Detail | Value |
|---|---|
| Providers | Anthropic (Claude), OpenAI, Google (Gemini), at the school's choice |
| Activation | Schools must actively opt in, either by providing their own API key or by subscribing to our paid AI add-on, in which case Tally makes the requests using its own provider account. The feature is disabled by default. |
| Data shared | Pupil reading level, favourite genres, likes/dislikes, and a list of books previously read (title, author, genre). No directly identifying pupil data (such as names) is sent to AI providers. |
| Purpose | Generating personalised book recommendations for the teacher to review |
| Statistics summaries | A school leader may also ask for a written summary of the figures on the school’s statistics page. The school’s name, today’s date and its term dates are sent alongside the figures, so the summary can tell term time from a school holiday. Otherwise only whole-school or whole-class totals are sent. No pupil names, no identifiers, no characteristics, and nothing about any individual pupil. |
| Safeguards | Each school controls whether to enable this feature. A school using its own API key is bound by its own agreement with the chosen AI provider. A school on our paid AI add-on is served through Tally’s provider account, and that provider acts as a sub-processor to Tally, listed in our sub-processor register. |
Updated 25 February 2026: Student names have been removed from all AI prompts. Only pseudonymised reading profile data is now sent to AI providers.
| Detail | Value |
|---|---|
| Provider | OpenLibrary / Internet Archive |
| Data shared | Book metadata only (ISBN, title, author). No personal data is sent. |
| Purpose | Looking up book cover images and supplementary book metadata (page count, publication year) |
| Detail | Value |
|---|---|
| Provider | Cloudflare Email Routing (covered under Cloudflare DPA) |
| Data shared | Staff user email addresses and email content (password-reset links, welcome messages); the name and address of someone we reply to about an enquiry or support request, and the reply |
| Purpose | Transactional emails (password resets, account invitations) and our replies to enquiries and support requests. No marketing emails are sent. |
| Detail | Value |
|---|---|
| Provider | Wonde Ltd (UK-based MIS data provider) |
| Data shared | Pupil names, class and year-group membership, and (where published by the school's MIS) staff-class assignments, read from the school's Management Information System via Wonde. Tally does not write data back to the MIS. |
| Purpose | Keeping pupil and class lists in sync with the school's MIS without manual entry |
| Safeguards | Wonde acts under the school's authorisation and its own data processing terms; access is granted per school and can be revoked by the school at any time. |
| Detail | Value |
|---|---|
| Provider | Sentry (Functional Software, Inc., US-headquartered) |
| Data shared | Technical diagnostic data captured when an error occurs (error messages, stack traces, request metadata). May incidentally include a user or organisation identifier from the request context. Reading records and pupil contact details are not intentionally sent. |
| Purpose | Detecting, diagnosing and fixing faults to keep the service reliable and secure |
| Safeguards | Used under Sentry's data processing terms; diagnostic data is retained only for a limited period. |
| Detail | Value |
|---|---|
| Provider | MyLogin (provided via Wonde) |
| Data shared | Staff identity and authentication details needed to verify a sign-in (e.g. name, email/identifier and school). No pupil data is shared with MyLogin. |
| Purpose | Allowing school staff to sign in securely using their existing school credentials |
| Safeguards | Operates under the Wonde/MyLogin terms; used only for schools that enable single sign-on. |
We do not sell personal data. We do not share personal data with advertisers, data brokers, social media platforms, or any other third parties beyond those listed above.
Tally’s infrastructure is hosted on Cloudflare’s global network. Cloudflare, Inc. is headquartered in the United States. Where personal data is transferred outside the United Kingdom, we rely on the following safeguards as required by Articles 44 to 49 of UK GDPR:
| Transfer | Mechanism |
|---|---|
| Cloudflare (US-headquartered) | Cloudflare DPA v6.3 (auto-applies with service agreement), incorporating EU SCCs and UK IDTA (Version B1.0). Cloudflare is certified under the EU-US Data Privacy Framework and UK Extension. D1 database is located in Western Europe (Germany). |
| AI providers (US): if enabled by the school | Where a school supplies its own API key, the school is responsible for ensuring its use of that provider complies with its own data transfer obligations, and Tally does not hold a contract with the provider on the school's behalf. Where a school uses our paid AI add-on, Tally holds that contract and the provider acts as a sub-processor to Tally. |
Cloudflare transfers are covered by the Cloudflare DPA v6.3 and EU-US Data Privacy Framework certification. AI provider transfers are the responsibility of the school as controller where the school supplies its own API key; where the school uses our paid AI add-on, the provider is a Tally sub-processor and the transfer is covered by Tally’s agreement with that provider.
We retain personal data only for as long as necessary for the purpose for which it was collected, or as required by law.
| Data category | Retention period | Rationale |
|---|---|---|
| Pupil data | Retained while the school's subscription is active. Deleted within 90 days of subscription termination or upon school request. | Necessary to provide the service. Schools may request earlier deletion at any time. |
| Staff user accounts | Retained while the school's subscription is active. Soft-deleted (deactivated) upon account removal; hard-deleted within 90 days of subscription termination. | Necessary to provide access to the service. |
| Audit logs | IP addresses and user-agents automatically anonymised after 90 days. Audit trail (action, actor, timestamp) retained for 2 years, then automatically purged. | Necessary for security monitoring and incident investigation. |
| Rate-limiting records | Automatically purged after 1 hour. | Short-lived records used solely for brute-force prevention. |
| Authentication tokens | Access tokens: 15 minutes. Refresh tokens: 7 days. Password-reset links: 1 hour. | Minimised to reduce risk of token theft. |
| AI recommendation cache | 7 days in KV cache, then automatically expired. | Temporary cache to avoid redundant API calls. |
| Book cover image cache | Cached in browser localStorage for 7 days. Cached in R2 object storage indefinitely (non-personal data: book cover images only). | Performance optimisation. No personal data is stored in the cover cache. |
| Enquiries and support correspondence | Support requests from a school's staff, our replies and notes are deleted with the school's data when the school leaves Tally. Website enquiries and school details forms from schools that do not use Tally, with our replies and notes, are deleted 24 months after the last message between us. Once we set the school up on Tally, its enquiry is filed with the school and deleted with the school's data. You can ask us to delete yours sooner at any time. | Needed to answer you and to keep a record of what we said. |
| Parent feedback survey answers | 12 months from the date they are sent, then automatically deleted. Deleted sooner if the school's data is deleted after it leaves Tally. | Long enough to compare one survey with the next. |
| Cloudflare request logs | Managed by Cloudflare in accordance with their data processing terms. Typically retained for a limited period (see Cloudflare's privacy policy). | Infrastructure-level logging outside Tally's direct control. |
Under the UK General Data Protection Regulation and the Data Protection Act 2018, data subjects have the following rights. The method for exercising each right depends on whether you are a school staff member or a parent/carer acting on behalf of a pupil.
| Right | Description | How to exercise |
|---|---|---|
| Right of access | You have the right to obtain confirmation of whether we process your personal data and, if so, to receive a copy of that data. (Article 15) | Staff: contact privacy@tallyreading.uk. Parents/carers: contact your child’s school, which will liaise with Tally if needed. |
| Right to rectification | You have the right to have inaccurate personal data corrected without undue delay. (Article 16) | Staff can update their own name and email in the platform. For pupil data, contact the school. |
| Right to erasure | You have the right to request deletion of your personal data in certain circumstances. (Article 17) | Staff: contact privacy@tallyreading.uk. Parents/carers: contact the school. Schools can delete pupil records directly within the platform. |
| Right to restriction | You have the right to request that we restrict processing of your personal data in certain circumstances. (Article 18) | Contact privacy@tallyreading.uk or the school. |
| Right to data portability | You have the right to receive your personal data in a structured, commonly used, and machine-readable format. (Article 20) | Schools can export pupil and reading data via CSV export from the platform. Staff can request their data by contacting privacy@tallyreading.uk. |
| Right to object | You have the right to object to processing based on legitimate interests. (Article 21) | Contact privacy@tallyreading.uk. We will cease processing unless we demonstrate compelling legitimate grounds. |
| Rights related to automated decision-making | You have the right not to be subject to decisions based solely on automated processing that produce legal or similarly significant effects. (Article 22) | AI book recommendations are advisory suggestions for teachers, not automated decisions. Teachers retain full discretion. |
Because Tally does not have a direct relationship with pupils, requests concerning pupil data should be directed to the school in the first instance. The school, as data controller, is responsible for responding to data subject requests. Tally will assist the school in fulfilling such requests in accordance with our Data Processing Agreement.
Your answers to the optional parent survey (Section 2.4) are held by Tally, not the school, so questions and requests about them go to privacy@tallyreading.uk. Because the answers are not linked to your child, your parent link or any account, we can only find yours if you tell us what your comment said. An answer with no comment cannot be told apart from anyone else's.
We will respond to valid requests within one calendar month, as required by UK GDPR. This period may be extended by two further months where requests are complex or numerous, in which case we will inform you within the first month.
If you are dissatisfied with how your personal data has been handled, you have the right to lodge a complaint with the Information Commissioner’s Office (ICO):
Tally does not use third-party cookies, advertising cookies, or analytics cookies. We set one cookie and use the browser storage listed below. Section 9.4 says which of it is strictly necessary and which is not.
| Name | Type | Purpose | Duration | Scope |
|---|---|---|---|---|
refresh_token | httpOnly, Secure (production), SameSite=Strict | Stores the refresh token for maintaining authenticated sessions. Not accessible to JavaScript. | 7 days | Path=/api/auth only |
For anyone visiting the site, signed in or not:
| Key | Purpose | Duration |
|---|---|---|
krm_sso_enabled | Remembers whether this site offers MyLogin sign-in, so the sign-in screen still shows the MyLogin button if that check fails. Holds only "true" or "false", the same for everyone. Set on every page, the parent reading page included. | Until you clear this site's data |
cookieBannerDismissed | Remembers that you closed the cookie notice on the home page. | Until you clear this site's data |
For staff signed in to Tally:
| Key | Purpose | Duration |
|---|---|---|
krm_auth_token | Stores the short-lived JWT access token for API authentication. | 15 minutes (token TTL; cleared on logout) |
krm_user | Stores non-sensitive user profile data (name, email, role, organisation name) for UI display. | Until logout |
tally.saveQueue.v1 | Holds reading sessions and register entries you have recorded until Tally confirms it has them, so a poor connection doesn't lose them. Includes what was recorded (pupil, date, book and any notes) and the pupil's name. Saves still waiting when you sign out stay on the device and are sent only when the same person signs in again. | Until Tally confirms each save. A save not delivered within 7 days is given up, and up to 5 refused or given-up saves stay listed until you dismiss them |
tally.deviceId.v1 | A random ID for this browser and nothing else. It is sent with each register entry and kept with that entry's receipt on our servers for 14 days, so entries from one device are applied in the order they were made and a late resend cannot undo a newer tap. | Until you clear this site's data |
installNudgeDismissed | Remembers that you closed the suggestion to install Tally on this device. | Until you clear this site's data |
tally.garden.seen:<view>:<id> | The reading garden stage last shown on this device for a pupil, a class, a class's goals board or the whole school (for a class, also each goal's level), so new growth is celebrated once. <view> is student, class, board or school, and <id> is Tally's internal ID for it, never a name. | Until you clear this site's data |
Signing out removes krm_auth_token and krm_user. The other staff keys stay, so saves still waiting can go when you sign back in.
On the parent reading page:
| Key | Purpose | Duration |
|---|---|---|
tally.parentSaveQueue.v1 | Holds readings and book ratings you have logged until Tally confirms it has them, so a poor connection doesn't lose them. Includes your reading page link and what was logged. | Until Tally confirms each save, or it is given up after 7 days |
tally-parent-welcome-dismissed | Remembers that you closed the welcome card. | Until you clear this site's data |
tally.garden.seen:parent:<link> | The reading garden stage last shown on this device, so new growth is celebrated once. | Until you clear this site's data |
tally-parent-visits | Counts how many times the page has opened on this device, so the feedback survey is not shown on your first visits. | Until you clear this site's data |
tally-parent-survey:<survey> | Whether you answered the feedback survey, said No, or said Later (with the date to ask again). | Until you clear this site's data |
tally-parent-weekend:<link> | The last weekend this page asked whether your child read at the weekend, so it asks once a weekend. | Until you clear this site's data |
These are shared by every child's reading page opened on the same device, except the garden and weekend keys, which are kept per page. Nothing in them is sent to Tally apart from the queued saves themselves.
| Key | Purpose | Duration |
|---|---|---|
globalClassFilter | Remembers the currently selected class filter within the session. | Until the browser tab is closed |
pendingClassAutoFilter | Just after sign-in, holds the IDs of the classes you teach so the class filter starts on them. Removed once applied. | Until the browser tab is closed |
recentlyAccessedStudents | Tracks recently viewed students for quick navigation. | Until the browser tab is closed |
markedPriorityStudents | Tracks which students you have marked as seen, which hides them from the priority list for the rest of the session. | Until the browser tab is closed |
classAssignmentBannerDismissed | Remembers that you closed the notice saying your classes haven't been linked yet. | Until the browser tab is closed |
adminSetupStep | The step you reached in the admin set-up guide, so it reopens there. | Until the browser tab is closed |
activeOrganizationId | Owner accounts only. The school you switched to, so reloading the page keeps you in that school. Sent to Tally with each request to say which school you are viewing. | Until the browser tab is closed |
openSettingsTab, openAchievementsTab, openReadingNewsTab | Opens the right tab when a link takes you to Settings, Achievements or Reading News. Removed as soon as that page reads it. | Until the browser tab is closed |
tally:chunk-reloaded-at | The time Tally last reloaded a page because part of it failed to download, usually just after an update. It stops the page reloading in a loop. Set on any page, the parent reading page included. | Until the browser tab is closed |
sentryReplaySession | Set by Sentry, our error monitoring service (section 5.6), on every page except the parent reading page. Holds a random recording ID, when it started, and whether this tab was picked for a session recording. Recordings hide all text and block images and video. | Until the browser tab is closed |
All sessionStorage data is cleared when the browser tab is closed, and signing out clears it too. None of it is sent to Tally, except that an owner's
activeOrganizationId tells Tally which school they are viewing.
sentryReplaySession goes to Sentry only as part of a recording.
We do not use advertising or tracking cookies or storage.
The cookie and these keys are strictly necessary, and we set them without asking:
krm_auth_token and krm_user, which keep staff signed in.tally.saveQueue.v1, tally.parentSaveQueue.v1 and tally.deviceId.v1, which hold saves that have not reached us yet and keep one device's register entries in order.tally:chunk-reloaded-at, which stops a page reloading itself in a loop.Everything else listed above is not strictly necessary. Apart from sentryReplaySession, each of these keys remembers something on this device, such as a closed notice, a filter, a tab, a set-up step, the garden stage last shown, the parent page's visit count, survey answer and weekend reminder, or whether the site offers MyLogin. None of them is sent to us. sentryReplaySession belongs to Sentry's error monitoring and goes to Sentry when a tab is picked for a recording. We do not ask for consent before setting any of them.
You can remove all of it at any time by clearing this site's data in your browser settings. Staff will be signed out, any saves still waiting to be sent will be lost, and the page will treat your device as new.
We implement appropriate technical and organisational measures to protect personal data, including:
| Measure | Detail |
|---|---|
| Encryption in transit | All data transmitted between the user's browser and the Tally platform is encrypted using TLS (HTTPS). |
| Password security | Passwords are hashed using PBKDF2 with 100,000 iterations and a unique salt per account. Plaintext passwords are never stored or logged. |
| Token security | JWT access tokens have a 15-minute lifetime. Refresh tokens are stored in httpOnly cookies with Secure, SameSite=Strict, and Path-restricted attributes. |
| Multi-tenant isolation | All database queries are scoped to the requesting organisation. Pupils and staff from one school cannot access data belonging to another school. |
| Role-based access control | Four permission levels (owner, admin, teacher, read-only) restrict access to data and actions appropriate to each role. |
| Audit logging | Sensitive operations (user creation, modification, deletion, settings changes) are recorded in an audit log with timestamp, actor, action, and IP address. |
| Rate limiting | Authentication endpoints are rate-limited to mitigate brute-force and credential-stuffing attacks. |
| Soft deletion | User and organisation records are soft-deleted (deactivated) rather than immediately removed, preventing accidental data loss while supporting eventual hard deletion. |
| Minimal client-side data | Only essential data is stored in the browser. Sensitive tokens use httpOnly cookies inaccessible to JavaScript. |
| Infrastructure security | Hosted on Cloudflare's platform, which provides DDoS protection, Web Application Firewall (WAF), and is certified to ISO 27001, SOC 2 Type II, and PCI DSS. |
Each subscribing school enters into a Data Processing Agreement (DPA) with Tally, as required by Article 28 of UK GDPR. The DPA sets out:
We may update this privacy policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes:
We encourage you to review this policy periodically.
If you have any questions about this privacy policy, your personal data, or our data protection practices, please contact us:
| Channel | Detail |
|---|---|
| privacy@tallyreading.uk | |
| Data Protection Lead | Sam Castillo (sam@tallyreading.uk). Note: A formal DPO has not been appointed as Scratch IT LTD does not meet the mandatory appointment thresholds under Article 37 of UK GDPR. Sam Castillo acts as the named privacy contact for all data protection matters. |
For requests concerning pupil data, parents and carers should contact their child’s school in the first instance. The school may then contact Tally to assist with the request. Questions about the parent survey (Section 2.4) come straight to us at privacy@tallyreading.uk.
This privacy policy is made under and governed by:
References to “UK GDPR” throughout this policy mean the UK General Data Protection Regulation as described above.
Scratch IT LTD · Company 08151576 · ICO ZC098130