Privacy Policy
Last updated: 14 November 2026
We take privacy seriously, including the privacy of children and families. This Privacy Policy explains what information Autodidax Reading (Reading App) uses, what we save, and how artificial intelligence (AI) is used to help your child learn to read.
1. Scope, Age Range and Availability
Autodidax Reading (Reading App) is designed for children learning to read, used with a parent or guardian's consent, and for adults who want to practise reading. It is currently offered only to users located in Singapore; if we expand to other countries in the future, we will update this Policy accordingly.
This Policy is intended to comply with Singapore's Personal Data Protection Act 2012 (PDPA).
- Users aged 18 and above may create and manage their own account and give their own consent to this Policy.
- For users under 18, a parent or legal guardian must create the account and provide consent on the child's behalf. See Section 4 below and our Parent/Guardian Consent form. We do not knowingly collect personal data from a child except through an account created and consented to by their parent or guardian.
2. Information We Save
We designed the Reading App to collect and store as little information as possible.
We do not save:
- voice recordings made during reading sessions;
- conversations between a user and the AI tutor; or
- transcripts of those conversations.
Reading progress. The Reading App saves:
- the last page opened, so that the user can continue from where they stopped; and
- a record of pages read aloud with the AI tutor: for each such page, which page it is, the dates it was first and most recently read, and the number of times it has been read. A page is added when the tutor hears it being read; turning pages without reading adds nothing.
This record is what the Dashboard in the app's menu shows: how many pages of each section (Letters, Words, Sentences and Books) and of each deck or book have been read. It does not include what was said, pronunciation scores, mistakes, or how long reading took. The Dashboard is shown to whoever is signed in to the account, so on a child's account both the parent or guardian and the child can see it. It is not shared with anyone else.
Usage records. When the AI reading tutor is used, we record when each session starts and ends and how much of each service it used (seconds of speech recognised, characters of speech generated, and AI model tokens), so we can charge the correct amount of credit and help with questions about charges. These records do not include what was said. Detailed per-event records are deleted within 7 days; session records are kept for 12 months.
Where an account is created, we also process:
- account information — the name and email address of the Google account used to sign in, Google's identifier for that account, whether the account is for a child or for an adult, and the date and version of the consent given;
- credit information — the credit balance, the date it expires, and a record of any credit that expired unused; and
- where applicable, payment information needed to operate the account.
See Section 9 for how long this is retained.
Other operating records. To run the service we also keep two small records per account: the date on which the tutor last gave its once-a-day reading tip, and a count of how many page pictures the account has loaded in the current ten minutes and the current day, which protects the reading library from being copied. The picture counts are deleted after 2 days and do not record which pictures were viewed.
Sign-up location check. The Reading App is offered only in Singapore, so when a new account is created we use the IP address of the device signing up to check that it is connecting from Singapore. The IP address is looked up in a country database held on our own server (IP geolocation data by DB-IP, https://db-ip.com, licensed under CC BY 4.0), so it is not sent to anyone else for this check, and it is not stored with the account. Our server logs are described below.
Server logs. The Reading App does not keep a log of individual requests, and does not record IP addresses or browser details. Our hosting provider (Microsoft Azure) does not keep such a log for us either. The app writes short technical messages while it runs (for example, errors, or an internal account number when a usage limit is reached) so that we can fix problems; these never contain voice recordings, conversations, transcripts or IP addresses, and are not stored. If we later start keeping logs to help secure the service, we will update this Policy to say what is kept and for how long.
3. Voice and AI Processing
The AI reading tutor is provided by three services working together:
- Speech recognition (Microsoft Azure AI Speech). While a reading session is running, the child's voice is streamed from the browser to our server and on to Microsoft's speech service, which turns it into text and, for pages with words or sentences, scores how closely each word was pronounced against the page text.
- The tutor's replies (Anthropic's Claude). The text of what the child said, the pronunciation scores, the text of the page being read, a short written description of the page's picture, and any teaching notes we have written for that page are sent to Anthropic's AI model, which generates the tutor's reply. The pictures themselves are never sent.
- The tutor's voice (Microsoft Azure AI Speech). The reply text is sent to Microsoft's speech service, which turns it into speech that is played in the browser.
Our server passes this information between the services during the session and does not store the audio, the text, or the replies.
Although our Reading App does not save voice recordings or conversations, Anthropic and Microsoft may retain API inputs and outputs for a limited period for purposes such as abuse monitoring and security, subject to the API service and data-retention settings we use.
4. Account Set-Up, Consent and Email Confirmation
When an account is created, the account holder is asked who will use the account:
- a child under 18, in which case the account holder must be the child's parent or legal guardian; or
- the account holder themselves, in which case they must be 18 or older.
We record this choice, along with the date and version of the consent given. We do not ask for or store a date of birth.
Accounts for a child. Before a child can use the AI reading tutor, the parent or legal guardian must:
- Create the account by signing in with their own Google account and email address; and
- Complete the Parent/Guardian Consent step, confirming they are the child's parent or legal guardian and agreeing to this Policy.
Accounts for users aged 18 and above. Adult users may create their own account and give their own consent to this Policy, without a parent's involvement, by signing in with their own Google account and confirming they are 18 or older.
The Reading App cannot be used until consent is complete. We only accept Google accounts whose email address has been verified by Google, so the person giving consent must be able to sign in to that Google account, which confirms they control its email address. We do not send a separate verification email.
We use this Google sign-in and attestation process as a reasonable means of confirming that the person giving consent controls the account's email address. It does not independently verify age, identity or legal guardianship. Account holders remain responsible for the accuracy of the information they provide, including the choice of who will use the account.
If we make significant changes to this Policy or the Parent/Guardian Consent, we may ask account holders to review and accept the updated version before continuing to use the Reading App (see Section 12).
Parents and guardians are encouraged to supervise their child's use of the Reading App.
5. How We Use Information
Information processed through the Reading App is used only as necessary to:
- provide the reading and AI tutoring functions;
- allow a user to continue from the last page opened;
- show the account's reading progress on the Dashboard;
- operate and secure the service; and
- manage accounts and payments, where applicable.
We do not use children's information for advertising.
We do not sell personal information.
6. Third-Party Service Providers and Cross-Border Data Transfer
The Reading App is powered by Microsoft Azure AI Speech (speech recognition and speech synthesis) and Anthropic's Claude API (the tutor's replies), and is hosted on Microsoft Azure.
- Microsoft processes the child's voice to turn it into text and pronunciation scores, and turns the tutor's replies into speech, as described in Section 3.
- Anthropic processes the transcribed text, pronunciation scores and page text to generate the tutor's replies, as described in Section 3.
- Microsoft Azure hosts the application and its database, in Microsoft's Singapore (Southeast Asia) region, and so processes the limited information described in Section 2 (such as the reading progress and account information) to operate and secure the service.
- Google Sign-In, where used, processes information necessary to authenticate the account.
- HitPay processes payments. To create a top-up payment we give HitPay the amount and the account holder's name and email address, and HitPay provides us with the information necessary to confirm and manage the payment. During our initial Singapore release, payments are made using PayNow. Other payment methods, including credit and debit cards, may be offered in the future.
The Reading App, its database and the Microsoft speech services run in Microsoft Azure's Singapore (Southeast Asia) region. Anthropic processes the text sent to its AI model on servers located outside Singapore (in the United States), and Google and HitPay may also process information outside Singapore, so a user's or child's information may be transferred to, and processed in, countries other than Singapore.
Where we transfer personal data outside Singapore, we take steps required under the PDPA to ensure the recipient provides a standard of protection comparable to the PDPA, including relying on our service providers' contractual and security commitments.
Information processed by our third-party service providers is handled according to their applicable terms, privacy commitments and data policies.
7. AI Training
By default, neither Anthropic nor Microsoft uses information submitted through their APIs, including inputs and outputs, to train or improve their AI models.
We do not opt in to sharing our users' API inputs and outputs with Anthropic or Microsoft for model training.
8. Analytics and Cookies
We do not use advertising cookies or third-party tracking cookies. We may use strictly necessary cookies or similar technologies to keep users signed in, maintain security and operate the Reading App. We do not use these technologies for advertising.
9. Data Retention
We do not retain voice recordings, conversations or transcripts.
We retain the reading progress (the last page opened and the record of pages read aloud with the tutor) for as long as the account remains active, or until the associated information is deleted at the parent's or user's request.
Account information is retained for as long as the account remains active and thereafter only for as long as reasonably necessary for account administration, security, legal or accounting purposes. Section 11 explains the limited records that may be kept after an account is deleted, why, and for how long.
Payments are processed by third-party payment providers. We do not directly store full payment card or bank account details. Our payment providers process information necessary to complete and record payments in accordance with their own privacy and data-retention policies.
Anthropic and Microsoft may separately retain certain data for a limited period in accordance with their own data-retention policies (see Sections 3 and 6).
10. Data Security
We take reasonable steps to protect information handled by the Reading App from unauthorised access, loss, misuse or disclosure.
However, no Internet-based service can guarantee absolute security.
If we become aware of a personal data breach, we will assess it and make notifications to affected individuals and the Personal Data Protection Commission (PDPC) where required under the PDPA.
11. Parents' and Users' Choices
A parent, legal guardian, or user aged 18 and above may:
- request access to, and a copy of, the information we hold about them or their child;
- request correction of information stored by us; and
- request deletion of the account and the information stored with it. This is also how consent is withdrawn: the Reading App cannot be used without consent, so withdrawing it means the account is closed and deleted as described below.
To make a privacy request, please contact us using the details below. We will respond within a reasonable time and in accordance with the PDPA.
What we keep after an account is deleted
When we delete an account at your request, we delete the account information, the reading progress (the last page opened and the record of pages read aloud with the tutor), and the usage and top-up records stored with it. A small number of limited records may survive the deletion, for the purposes and periods below:
- Deletion record (consent and billing summary). A record that the account was deleted, identified only by an internal account number. It contains the type of account (for a child, or for an adult), the version and date of the consent given, and the credit balance, credit expiry date and top-up totals at the time of deletion. It does not include the name, email address, reading information or usage history. Purposes: to show that consent was obtained and that the deletion was carried out, and to reconcile credits and payments in our accounts. Kept for: 12 months after the deletion, then deleted. Records of other administrative changes to accounts (for example, a corrected credit balance) are kept for the same 12 months.
- Sign-up record. A one-way scrambled (hashed) form of Google's identifier for the account, with the date it was first used to sign up. It does not include the name, email address or any other account information, and cannot on its own be turned back into the identifier. Purpose: to make sure free starting credit is given only once per Google account, even if an account is deleted and created again. Kept for: as long as we offer free starting credit to new accounts, then deleted.
- Our correspondence about your request. The emails exchanged when you asked for the deletion, which include your email address. Purpose: to show which request was made and that we acted on it, since the deletion record above does not identify you. Kept for: 12 months after the request is completed, then deleted.
- Payment records held by our payment provider. Where a top-up was paid through HitPay, HitPay keeps its own record of the transaction. Purposes: to complete, record and reconcile payments and to meet legal, tax and anti-fraud obligations. Kept for: the period set by HitPay's own policies and applicable law, which we do not control.
Separately, copies of deleted information may remain for a short time in database backups (up to 7 days), until they expire automatically. These copies are not used for any other purpose.
12. Changes to This Privacy Policy
We may update this Privacy Policy if the Reading App, applicable laws or the services we use change.
If we make significant changes affecting children's privacy, we will update this policy and, where appropriate, notify parents or obtain new consent.
13. Contact Us and Complaints
Data Protection Officer
KINDLIVELY PTE LTD
admin@kindlively.com.sg
Parents and users may also contact us to request access to, or correction of, information, or to have the account deleted (which also withdraws consent).
If you have an unresolved concern about how we handle personal data, you may also contact Singapore's Personal Data Protection Commission (PDPC) at www.pdpc.gov.sg.