1. Who we are
Toddle provides interactive stories for children aged 3 years and older and their caregivers. Stories are organised by reading level rather than by age, and there is no upper age limit. This policy explains information handled by the Toddle app on iOS and Android, its account and subscription services, our support service and our website.
The controller is Toddle Learning Ltd. Company number: 17430689. Registered office and postal contact address: Suite Ra01 195-197 Wood Street, London, United Kingdom, E17 3NU.
Contact: hello@toddlelearning.app. Website: https://toddlelearning.app/.
The app is offered in English through participating App Store and Google Play countries and regions. Website processing is described separately below; it differs from the app's planned story-engagement analytics.
2. The short version
- Children do not create Toddle accounts or profiles. An adult looks after account and purchase decisions.
- Three complete free stories, one per Story level, are included for offline reading without an account.
- A parent account is required for subscription access across supported devices. It does not synchronize reading history, settings or downloads.
- Apple (iOS) and Google Play (Android) handle payments. Supabase supports accounts, backend services and story delivery. RevenueCat helps manage and verify subscriptions.
- Account, purchase and technical information is processed to operate these services. This includes device and network information; we do not describe the app as collecting no data.
- The current release has no optional story-opening, completion or reading-retention analytics. Billing records and operational logs are separate from those measurements.
- Toddle has no advertising. We do not use the Android advertising ID, and we do not use personal information to track people across unrelated apps or websites for advertising.
3. Information used for accounts
Adults can sign in using Apple or Google. Supabase processes the sign-in and maintains the Toddle account. Account information includes a Toddle identifier, sign-in provider identifiers, an email address or Apple private relay address where supplied, and session/authentication information. Apple authorization information is stored where needed to revoke the sign-in grant when an account is deleted.
The app requests only the email scope for Apple sign-in. Google sign-in can also supply your display name and profile-picture link. We retain the display name in authentication metadata; profile-picture links are removed before storage in current authentication records. Toddle does not display these fields in its account interface. We use the sign-in information for account authentication, not to create a child profile.
Access codes. Adults can enter an access code behind the parent gate to open an isolated demo account with temporary premium access, without Google sign-in or payment. Supabase creates an account identifier and a synthetic email address for each activation, and stores an expiring access grant. We do not ask for a personal email address for this route. The code is validated against a server-held digest; it is not stored in the app. Sign-out and profile deletion use the normal account controls. This does not create or cancel a store subscription.
We do not ask children for names, birthdays, photos or contact details. The app does not provide child accounts, messaging or public profiles.
4. Purchases and subscription services
Subscriptions are processed by the store you downloaded the app from. On iOS, Apple processes monthly and annual subscription payments, renewals and refund requests. On Android, Google Play processes them through Google Play Billing. We do not receive complete payment-card or bank-account details from either store.
Toddle and RevenueCat use the Toddle account identifier and purchase information to establish subscription access. This includes product and transaction identifiers, purchase evidence (such as a purchase token on Android), subscription status, and relevant purchase, renewal and expiry information. Verification allows access on supported devices signed into the same Toddle account and helps prevent an existing purchase being assigned to a different active account.
RevenueCat also receives technical information from its subscription software, including app/SDK versions, operating system and device information, and locale information. On iOS this includes an Apple identifier for vendor (IDFV) where available. On Android, subscription processing uses the Toddle account identifier, product and transaction identifiers, and Google Play purchase tokens described above. Toddle does not enable RevenueCat attribution integrations or call its optional device-identifier collection methods. Network connections expose an IP address to the receiving service. We do not collect or transmit the Android advertising ID, and the app does not request the AD_ID permission. Toddle disables RevenueCat's optional attribution-identifier collection and diagnostics settings, but these settings do not remove all ordinary subscription requests or device metadata.
Subscription software may refresh information after returning to the app once a billing session has been initialized. It is not accurate to say that all subscription network activity occurs only while a parent screen is visible.
Cancelling. Deleting the app or your Toddle account does not cancel your subscription. Cancel renewal through the store that billed you: the Apple account that purchased the subscription on iOS, or Google Play (Payments & subscriptions) on Android. Refund requests are handled by Apple or Google under their own policies.
5. Story delivery, local information and support
Story downloads and catalogue requests disclose network information such as IP addresses, request times and requested resources to hosting systems. Operational logs may contain requested story-file paths; these are not the same as tracking story openings or completions. Authentication, verification and deletion services may also log account identifiers, status and failure information.
Reading progress, selected Story level, reading mode and downloaded stories are stored locally rather than synchronized through a Toddle account. A limited subscription-verification record supports offline access until the earlier of 30 days after verification and the last verified paid-through date. Device backups and removal of app data depend on the operating system and device settings.
If you contact support, we receive the details and message you send. The in-app feedback option opens your email application. Nothing is sent unless you choose to send the email. If you do, we receive your email address, message and any attachments you include. Google hosts our support email. Please avoid sending unnecessary information about a child.
6. Why we use information
For UK data-protection purposes, we use the following bases, where applicable:
- Account and subscription operations: performance of the adult's requested contract, where the processing is necessary for that purpose.
- Service security and proportionate operational logging: legitimate interests in providing and protecting the service, subject to assessing the rights of those affected, especially children.
- Support: performance of the contract for service requests, or legitimate interests in responding to other enquiries, as applicable.
- Legally required records and responses: compliance with the specific legal obligation that applies.
Improving our stories: We plan to introduce limited engagement statistics to understand which stories are opened and completed, improve existing content, and guide the creation of new stories. These statistics are not currently collected. Before enabling them, we will explain what information is collected and provide any choices or consent required by applicable law.
Agreeing to Terms, signing in or solving the parent gate is not itself consent to optional analytics.
7. Service providers and disclosures
We use:
- Supabase: authentication, account database, backend functions and story hosting/delivery.
- RevenueCat: subscription infrastructure, purchase validation and subscription reporting.
- Apple: Sign in with Apple and App Store payment and subscription services on iOS.
- Google: Sign in with Google, Google Play Billing and distribution on Android, and hosting our support email correspondence.
Their roles vary by service. Apple and Google operate their own sign-in and store services under their own policies; not every provider acts solely as our processor. We may also disclose necessary information to professional advisers or where required by law or needed to protect rights and safety.
Provider information: Supabase, RevenueCat, Apple, Google.
8. Children and privacy
We do not ask children to submit personal details, and we do not use their information for advertising or behavioural targeting. Technical information from a child-directed service can nevertheless be personal information, even when the account belongs to an adult.
The app does not request location permission, does not collect precise location, and does not contain third-party advertising. Where technical identifiers are used for subscriptions or security, they are not used for advertising, profiling or tracking across other apps and services.
The parent gate separates adult controls from reading. It is not verified parental consent or proof of age.
If you think a child has submitted personal information or created an account, contact us so we can investigate and take appropriate action.
9. Account deletion and subscriptions
In the app: You can request deletion through the parent account controls in Settings.
Without the app: Instructions are also available at https://toddlelearning.app/account-deletion. You can request deletion without installing or opening the app by emailing hello@toddlelearning.app from the address linked to your account. Use the subject ‘Toddle account deletion request’. Do not send your password. We may ask you to confirm you own the account.
Deletion removes the Supabase account, any associated access-code grant and related Apple grant record, and attempts Apple sign-in revocation where a grant is available. The in-app deletion control does not currently automatically delete the RevenueCat customer record or purchase history. Contact hello@toddlelearning.app to request deletion of remaining information, subject to applicable retention requirements. It clears usable account access on the initiating device. A device that remains offline may retain previously verified access until its existing offline deadline. Local story files and progress can remain; possession of those files does not extend premium access.
Deleting the app or Toddle account does not cancel your subscription. See Section 4 for how to cancel with Apple or Google Play. You can delete a Toddle account without waiting for the subscription to expire.
10. Retention and deletion limits
We keep active account information while the account is in use. Access-code premium grants expire at their configured deadline; expiry does not itself delete the demo account. You can delete that account through Settings. We also remove expired demo accounts through operational cleanup; expiry is not a promise of immediate erasure. The account-deletion control removes the Supabase account and associated Apple grant record, but currently does not automatically delete the RevenueCat customer or purchase history. Requests to delete remaining information can be made by emailing hello@toddlelearning.app, subject to applicable retention requirements. Subscription software may continue making requests after a billing session has started. Account deletion therefore does not erase every provider record or guarantee restoration to a new account. You may contact hello@toddlelearning.app to exercise your data rights; this is not a promise of immediate provider-wide erasure.
Operational and security records have different retention periods. Supabase's current Free plan provides one day of API/database log availability and one hour of Auth audit-log availability. These limits do not apply to all stored records or other providers. The current plan does not include scheduled project backups. Provider recovery copies and other technical records can have different lifecycles.
Our support retention schedule is six months after resolution, with exceptions limited to relevant records needed for a legal obligation or ongoing dispute. Local files, reading progress and settings remain on your device until removed through available app controls or the device's storage lifecycle. Operating-system backups may retain copies according to your settings.
Launch-announcement requests are kept only as needed to send the single requested announcement, unless withdrawn sooner. Careers correspondence is used for the current enquiry, without a future candidate pool. Provider records may follow separate retention requirements; deleting an account does not cancel a subscription or delete Apple's or Google's own billing records.
11. International processing
The Supabase project is hosted in Frankfurt, Germany. This does not mean all information stays in Germany or the European Union. RevenueCat, Apple, Google and our website host may process information in other countries, including the United States. Their privacy information describes their services and processing locations. Contact hello@toddlelearning.app for information about safeguards applicable to your data and to exercise your rights.
12. Rights and contact
Depending on the law that applies, you may have rights to access, correct, delete or obtain a copy of personal data; restrict or object to processing; and withdraw consent where processing relies on it. Some rights have conditions or exceptions. Contact hello@toddlelearning.app. We may need to verify your identity and will respond within the applicable legal period.
UK users can complain to the Information Commissioner's Office. Other users may complain to their competent local authority where applicable. You do not have to contact us before exercising a statutory complaint right.
13. Changes
We will publish revisions with an effective date and provide additional notice where required. Changes requiring consent will not take effect for the affected processing until the necessary consent has been obtained.
14. Visiting our website
Vercel hosts our website and processes network information, including IP addresses and requests, to deliver and secure pages. Our site includes Vercel Web Analytics for website usage statistics. These can include pages viewed, referring pages, approximate location, timestamps and browser/device information. This is separate from planned app story-engagement statistics, which are not currently collected. Vercel describes its analytics as using no third-party cookies and a temporary visitor hash; its 24-hour visitor-session lifetime is not a deletion deadline for all analytics or hosting records. See Vercel's analytics privacy information.
Our website loads fonts from Google's font servers. These connections expose network information, such as IP addresses, to Google. See Google's privacy policy. Hosting, security and proportionate website measurement support our interests in operating and improving the website, subject to applicable law and visitor rights.
Contact, launch-announcement and careers links open your email application. Opening a link does not itself send an email. If you send one, we receive your email address and message in our Google-hosted inbox. Please avoid unnecessary information about a child.
If you ask to hear when Toddle launches, we use your email address for one requested launch announcement, not an ongoing newsletter. You can withdraw the request by emailing hello@toddlelearning.app. We keep the request only as needed to send that announcement, unless withdrawn sooner. We use careers messages and CVs to consider and respond to the current enquiry, without retaining them for a future talent pool. The retired friends-and-family waitlist is no longer stored or used.
Toddle Learning Ltd · Company number 17430689