Effective Date: October 3, 2026
This policy covers our current subscription reporting and the optional ad measurement features described below where available in your version of the app.
ToddlerTalk ("we," "our," or "us") values your privacy. This Privacy Policy explains how we handle information when you use our iOS app, ToddlerTalk.
Audio Recordings. You may record short clips of your toddler's voice. When you request a translation, that clip is sent to our processing partner to produce a result. We do not store audio on our servers.
Recordings you keep are saved on your device so you can play them back later, including clips captured before you subscribe. You can share a recording and its translation using the system share sheet. Sharing is something you start; we do not upload that share to our servers.
When we request a translation, we include a default age of two years so the model can produce age-appropriate suggestions. We do not currently ask you to set your toddler's age.
Onboarding Survey. After you continue from the paywall, we may ask two optional questions: how you heard about ToddlerTalk, and what you want to use it for. You can skip either question or the whole survey. If you answer, we store:
The option you picked for how you heard about us, and a short free-text detail if you chose "Somewhere else"
Your free-text answer for what you want to use the app for
Technical details: app version and build, iOS version, and device model
We do not ask for your name or email in the survey. If you type personal details into a free-text answer, we will store what you typed.
Usage Data. We collect information about how the app is used so we can understand which features help and where the app fails. This includes:
Which screens and features you open, and when
Whether a recording succeeded, how long it was, and whether the microphone permission was granted
Whether you play back or share a recording, rate a translation, or delete an item from history
Whether an analysis succeeded or failed, how long it took, how many translations were returned, and an error category when it fails
Subscription flow events, including when the paywall is shown, when a purchase is started, and whether it completed, was cancelled, or failed, along with the subscription product identifier and a general reason for failure
Technical details: app version and build, iOS version, and device model (for example "iPhone15,3")
This usage data is associated with a device identifier stored on your phone when you first use the app. That identifier is typically Apple's Identifier for Vendor, or a random identifier if that is unavailable. It is not your name, email, Apple ID, or advertising identifier, and it is not linked to your identity. It does allow us to recognize the same installation over time, which is how we tell whether a problem affects one device or many. This identifier may change after you remove and reinstall apps from this developer.
Survey answers are stored separately from usage data and are also associated with this device identifier.
What Usage Data Never Includes. We do not include your audio recordings, transcriptions of your toddler's speech, or the translations produced in this usage data.
No Account Required. ToddlerTalk does not require a user account, and we do not collect your name, email address, postal address, phone number, contacts, or precise location through our own usage analytics. If you allow optional ad measurement, Meta may collect the advertising identifier as described below.
Subscription Records. Apple sends our backend signed subscription records, including transaction and subscription identifiers, product, dates, trial status, payment amount and currency, and revocation information. We use these records to understand subscriptions and revenue, including renewals while the app is closed. We do not join them to advertising profiles or send these server records to Meta. They are stored on Supabase and are separate from our device-based usage data. Tracking permission does not control this first-party subscription reporting.
Apple Private Ad Attribution. The app can report broad milestones (app activation, trial, and payment) to Apple's privacy-preserving attribution system. Apple controls delayed, privacy-limited reports to eligible advertising networks. This mechanism does not read the advertising identifier and does not require tracking permission. It does not give us a person-by-person list of which ad produced each subscription.
Optional Ad Measurement (Meta). In versions with optional Meta measurement enabled, if you allow tracking in the iPhone permission prompt, we initialize Meta's SDK to measure advertising for ToddlerTalk. Meta receives app activation information and verified subscription events: trial starts when identifiable, actual payment amounts and currencies, subscription product identifiers, and first observed paid subscription events. The SDK also processes technical and attribution information, which can include the advertising identifier, SDK-generated identifiers, device and operating-system information, app version, event timestamps, and IP address. Meta may link this information with information it holds to attribute and improve advertising, under its Privacy Policy.
We do not send Meta recordings, transcriptions, translations, survey answers, toddler ages, or other child details. We do not forward our general usage analytics or its device identifier to Meta. StoreKit transaction identifiers are kept locally to avoid counting the same payment twice; our custom event parameters do not send those identifiers to Meta.
If you do not grant permission, the app does not initialize Meta's SDK or send these advertising events. The app's features and subscription prices do not depend on your choice. Our separate first-party usage analytics described above continue to operate.
To process your toddler's speech and provide AI-generated suggestions
To let you play back and share recordings you choose to keep on your device
To measure how features are used, so we can decide what to build and improve
To understand how people discover ToddlerTalk and what they want to use it for
To monitor reliability and performance, and to detect failures and outages
To debug and resolve technical issues
To understand how people move through our subscription flow, and to diagnose failed or interrupted purchases
To detect and prevent abuse of our service, including rate limiting
With your permission, we use Meta ad measurement to understand which advertisements lead to app usage and subscriptions and to improve our advertising. We do not use this information to make decisions about eligibility for services.
We do not store audio recordings on our servers.
Recordings, transcriptions, and AI suggestions are saved on your device. The app keeps a limited history. Deleting an item from history removes it, including its recording, from your device. Deleting the app removes all of this local data.
Subscription records are retained for subscription reporting and reconciliation. We do not yet operate an automated deletion schedule for these records. Contact us about access or deletion; transaction information may be needed to locate them.
Usage data and survey answers are kept only as long as they remain useful for the purposes described in Section 2. We do not currently operate a fixed deletion schedule for them. You may request deletion at any time; see Section 7.
Meta receives advertising measurement information under its own retention practices. Turning off tracking stops new event collection by this integration but does not erase information already received. Local payment deduplication records remain on your device until the app is deleted. Contact us about data requests; Meta also offers privacy controls under its Privacy Policy.
With tracking permission, we share the limited advertising measurement information described in Section 1 with Meta. This is separate from the audio processing and first-party analytics described below.
AI processing involves sending temporary audio data to our processing partner (OpenAI) to produce your result. Audio is not retained by us.
If you share a recording or translation from the app, it goes to the destination you choose (for example Messages or Files). We do not receive a copy of that share.
Our backend and database are hosted on Supabase, which stores data on our behalf as a service provider. Usage data, survey answers, subscription records, and service logs are stored there.
We may disclose information if required to do so by law.
ToddlerTalk is designed for parents and caregivers, not for unsupervised use by children.
Parents control whether to provide recordings. Audio of your toddler is processed to produce a translation and is not stored on our servers. Recordings remain on the parent's device unless the parent chooses to share them. We do not collect a child's name or any other identifying detail about your child.
All data transmissions are encrypted using industry-standard protocols. Access to stored data is restricted, and our database denies direct client access by default.
Because ToddlerTalk has no accounts, we identify first-party usage data and survey answers using the device identifier described in Section 1. Meta advertising data is handled separately.
Ad measurement. Choose “Ask App Not to Track” to decline. You can change permission in iPhone Settings > Privacy & Security > Tracking. When this feature is enabled, the app provides an “Ad measurement permissions” button in Settings to make or change your choice. Revocation stops new advertising events from this integration; it does not delete data already sent.
Access. You may ask what usage data and survey answers we hold for your device.
Deletion. You may ask us to delete the usage data and survey answers associated with your device.
Stop collection. You may ask us to stop collecting usage data from your device.
Local data. Your history and recordings are stored on your device. Deleting an item in the app removes that item. Deleting the app removes the rest, along with the device identifier.
Depending on where you live, you may have additional rights under laws such as the GDPR or the CCPA. To exercise any of these, contact us using Section 9. We may need your device identifier to locate your data, and we will explain how to find it.
We may update this Privacy Policy occasionally. Significant changes will be communicated in-app.
For questions, concerns, or data requests, contact us at adamrevetta@gmail.com.