Timo · Privacy policy
We don't collect anything from your kids.
Timo has no accounts, no sign-up, and no login — for the child using it or the parent setting it up. This page explains exactly what that means, and the one narrow exception that exists only to protect a purchase.
Last updated 27 September 2026
No account
No sign-up, login, or personal details — not from a child, not from a parent.
No tracking
No analytics or crash-reporting SDK of any kind is built into Timo.
No ads
Timo shows no ads and never sells or shares data with advertisers.
What stays on your device
Settings, saved timers, and usage counters — like the weekly free-timer count — live only in Timo's local storage on your device and never leave it. Uninstalling the app deletes all of it.
The one identifier that can survive a reinstall
To let a paid Timer Bundle purchase survive an app reinstall, Timo generates a random identifier on your device the first time it's needed and stores it in the iOS Keychain, rather than in the local storage an uninstall wipes. This identifier isn't tied to a name, email, or Apple ID — it identifies the device's purchase history, not the person — and it's used only to restore a past purchase, never for advertising or cross-app tracking.
Face ID stays with iOS
Timo uses Face ID (or Touch ID, or your device passcode as a fallback) to keep parent settings and purchases out of a child's reach. This is handled entirely by iOS itself — Timo never receives, stores, or transmits any biometric data. The app only ever gets a yes-or-no result: whether the person holding the phone was authenticated.
The two services we use
Two, and only two. RevenueCat processes in-app purchases and subscriptions — Timo sends it the on-device identifier above so a purchase can be tied to, and restored on, the same device, plus standard purchase and receipt data from Apple as part of validating a transaction. Timo never sends RevenueCat a name, email, or other identity information. Apple, through the App Store's StoreKit, handles the purchase transaction itself, the ordinary way any iOS app's purchases do. No other third party is integrated into Timo.
Notifications, entirely on your device
Timo schedules a local "timer's done" notification directly on your device. This isn't a push notification from a server — nothing about it is sent anywhere; it's generated and delivered entirely on-device.
No analytics, advertising, or tracking
Confirmed directly against the app's source and dependencies: there is no analytics SDK, no crash-reporting SDK, and no advertising SDK anywhere in Timo — no Firebase, Mixpanel, Amplitude, Crashlytics, Sentry, AppHud, or any ad network. Timo shows no ads, does no behavioral tracking or profiling, and does not sell or share data with advertisers or data brokers.
Children's privacy — COPPA, GDPR-K, and the UK Age Appropriate Design Code
Since Timo doesn't collect personal information from or about children anywhere in the app, its footprint is small under all three frameworks — but each expects a policy that says so explicitly, not one that just stays quiet about it.
COPPA (US)
No personal information is collected from children, so no verifiable-parental-consent flow is needed for data collection. The one on-device identifier Timo stores exists solely to restore a purchase, as described above, and Timo shows no behavioral advertising to children.
GDPR-K (EU)
The same "essentially no personal data leaves the device" facts apply here too. The one place personal data does flow to a third party is the purchase transaction, through RevenueCat and Apple — RevenueCat acts as a sub-processor for that data under its own GDPR compliance and data processing agreement.
UK Age Appropriate Design Code
Relevant since Timo is a service likely to be accessed by children. Its design already lines up with the Code's expectations: no profiling, no nudge techniques encouraging longer use or purchases, privacy-protective settings by default, and a parental gate — Face ID — in front of purchases and settings changes.
Data retention and deletion
There's no server-side account or database holding a child's or parent's data to retain or delete — everything lives on the device. A normal uninstall removes all local settings, saved timers, and usage data. The one exception is the Keychain-stored device identifier and its associated RevenueCat purchase history, which is designed to persist across a reinstall so a purchase isn't lost, and isn't removed by a normal uninstall.
How this maps to the App Store's privacy label
A best-effort summary of how Timo's actual behavior maps to Apple's Privacy Nutrition Label categories — not a substitute for the questionnaire in App Store Connect itself.
Questions about any of this? We're glad to answer them.
Contact us