Last updated: 30 August 2026
Cambridge Technology Innovation Centre ("CambTIC", "we", "us") makes two apps: ReadToWrite and KeepReading. This page explains, app by app, what information each one uses, where it goes, and what you can ask us to do with it.
We keep this page honest. It describes what the apps actually do today. When we change what an app does with your information, we update this page first.
Two promises that cover everything below: we never sell personal data, and we never use it for advertising.
ReadToWrite is a learning app with accounts. In short: your account holds a profile; your practice work is stored so you — and any teacher or parent linked to you — can see progress; and AI services help generate and grade exercises. The AI services see the work, never your name.
To use ReadToWrite you sign in with an account. The account includes:
A student account may use one iPad, one iPhone and one Mac at the same time. To apply that rule, we store for each signed-in device: its type, system version, app version, and an app-generated device ID. Sign-in sessions last up to 30 days. If you turn notifications on, we store the Apple push token that delivers them.
A student account can be linked to a teacher or a parent using a 6-character code. A linked teacher or parent sees the student's exercises, answers, scores and progress. That is the purpose of the link: it is how an adult supervises the learning. Nobody else sees a student's work. Our own staff access account data only to run the service and to answer support requests.
Parts of ReadToWrite are powered by external AI services, working for us under their service terms:
What none of these services receive: your name, username, email, phone number, or any account identifier. What we send is the learning content itself.
Some grading is automatic. A grade in ReadToWrite is practice feedback, not an official result. Where a teacher is linked to the account, the teacher can see and review the graded work.
For readers in the EU and the UK: Japan is recognised by EU and UK law as a safe destination for personal data (an "adequacy" decision). For the US providers we rely on their published data-processing terms.
In the words the law uses: most of this processing is needed to provide the service you signed up for ("performance of a contract"). The device rule, the service journal and the last-active time protect the service and its users ("legitimate interests"). Optional profile fields are used with your agreement ("consent"), which you can withdraw at any time by emptying the field or contacting us.
ReadToWrite is used by school-age learners preparing for exams. A student account is set up through a teacher's or a parent's code, and a student cannot sign in without one. The adult who holds that code gives it to the student, and can see that student's work in the app.
Many countries set an age below which a parent or guardian must agree before a child's data may be used — for example 14 in China and South Korea, 13 in the United States, and between 13 and 16 across Europe. Where that applies, the agreement must come from the child's parent or guardian, or from a school acting together with them.
A date of birth is optional. It is not asked for when an account is created; it can be added later in the profile, and left empty. Where one has been given, we use it to show the learner's age in their own profile and to the teacher or parent who supervises them, and for nothing else. It does not change the material a student is given.
A parent or guardian can ask us at any time to show, correct or delete a child's data, or to end the child's use of the service: privacy@cambtic.com. If you believe a child is using ReadToWrite without a supervising adult, tell us and we will act.
Wherever you live, you can ask us to:
Write to privacy@cambtic.com. We answer within 30 days. If you are unhappy with our answer, you can complain to the data-protection authority where you live.
ReadToWrite is free today. If we add paid subscriptions, Apple will process every payment. We never see card numbers or bank details.
KeepReading has no accounts, no sign-up and no profile. It shows no ads and contains no analytics.
Neither app contains advertising or analytics SDKs. The external services we use, and what for:
These services work for us as processors of the content described above. We share personal data with no one else, and we never sell it.
ReadToWrite: see "How long we keep it" in the ReadToWrite section above.
KeepReading: the app stores nothing about you on our side — there are no accounts.
ReadToWrite's rules for children — supervision through a teacher or parent code, the age thresholds, and a guardian's rights — are in the ReadToWrite section above. KeepReading has no accounts and collects no profile from anyone, of any age.
We may update this policy as the apps evolve. For material changes we will tell you in the app or on this site. The "Last updated" date at the top shows the latest revision.
Questions, concerns, or requests about this policy or your data:
CambTIC Ltd (Cambridge Technology Innovation Centre)
A company registered in England and Wales.
Email: privacy@cambtic.com
This page is written to meet the openness requirements of the privacy laws where our learners live — including the EU and UK GDPR, China's Personal Information Protection Law (PIPL), and the United States children's privacy rules (COPPA). Writing it plainly matters more to us than legal boilerplate.