Your privacy

Frazzle is built local first. Almost everything you and your child put into the app stays on your phone and is never uploaded to us. This page explains, in plain language, what stays on your device, the small amount that is sent off it and why, and the controls you have.

Last updated 5 September 2026

Who operates Frazzle

Frazzle is a parenting-support app for parents and caregivers, not for use by children. For any privacy question, or to exercise a right described below, email privacy@frazzleapp.com.

The short version

• Your family's information stays on your phone. Your child's nickname, your answers, your plans, your reflections, and your progress are stored on the device and are not uploaded to us.
• Personalisation happens on the device. Recommendations and tailored guidance are calculated on your phone. We never receive a profile of your child or your family.
• A small amount of technical data leaves the device so the app can run, stay stable, and improve: pseudonymous usage analytics (which you control), crash diagnostics, an app-integrity check, and read-only content downloads. None of it carries your child's profile or the words you write.
• No accounts, no real names, no date of birth, and no camera, microphone, contacts, or location.
• If you subscribe, the payment is handled by the App Store and the purchase is verified through RevenueCat. We receive your purchase and trial status and purchase history, never your card details, and it is tied to an app-generated identifier, not to your name.

Information kept only on your device

The following is stored on your phone and is not sent to us. It is removed when you delete it in the app or uninstall.

• Your child's nickname or alias (a city name you choose) and a coarse age band. Never a legal name, a date of birth, an exact age, or a photo. The avatar is a preset picture.
• Your onboarding answers and the scenarios and priorities you pick.
• Your goals, usual struggles, the pressures you are under, and your Understanding your child answers.
• Your plans and builds, the moves you choose, and your practice progress.
• Your Reflect, Sort It Out, and Grow Together responses, the result lines you see, and how far you got.
• Your scenario browsing and recommendation history, including which suggestions you dismissed or accepted.
• Your PlayBook game progress and the practice content selected for your child.
• Your Journey figures: active days, features used, situations explored, and progress stages.
• Your schedules, reminder preferences, and a local record of notification decisions (which reminder was scheduled and whether you opened it, never its text).
• App settings, including your analytics choice, and locally cached Hard Moments audio and downloaded content.

The important distinction: personalisation is calculated on your device. Frazzle does not upload your child's profile, your goals, your plan wording, your reflection answers, or any personalised recommendation profile.

How personalisation and recommendations work

Frazzle tailors what it shows to your family, and it does this on your phone.

• Signals from your plans, the moments you browse, and your use of Hard Moments, Reflect, Personalise, and PlayBook can shape which suggestions appear.
• Some of this is specific to one child; some parent skill progress is kept across your whole household.
• The recommendations themselves are generated locally. The underlying answers never leave the phone.
• If you have analytics enabled, we may record that a recommendation was shown, dismissed, or followed, using fixed identifiers for the surface and option, never the personal answers behind it.

Information that is sent off your device

To run the app, keep it stable, deliver its content, and improve it, a limited amount of technical data is processed in the cloud through Google Firebase and Apple device services. None of it includes your child's nickname, profile, age band, or the content you write in the app.

• Pseudonymous usage analytics (Firebase Analytics), which you control. See below.
• Crash diagnostics (Firebase Crashlytics): technical error traces only.
• An app-integrity check (Firebase App Check, using Google Play Integrity on Android and Apple App Attest on iOS) that proves the app is a genuine, unmodified build, to protect the service from abuse.
• Read-only content downloads (Firebase Remote Config, Cloud Firestore, and Hosting): the app reads configuration, authored content, and Hard Moments audio from our servers. This is one way; your data is not uploaded to deliver it.

Frazzle does not upload any content you write in the app. It has no feedback form, comments, messaging, or other way to send us your words.

Analytics and crash diagnostics

Analytics is pseudonymous, not fully anonymous. Firebase Analytics uses an app-instance identifier and Crashlytics uses an installation identifier. These are not your name, and we do not link them to your identity or use them to track you across other apps or sites. Frazzle does not attach your name, your child's nickname, plan text, reflection answers, or search text to analytics.

• What it records are fixed catalogue identifiers and status values, never parent-written content: tabs and features opened; which scenarios are browsed; plan, build, and schedule actions; recommendations shown, dismissed, or accepted; PlayBook game sessions and ranking; Reflect and Sort It Out funnel stages such as started, completed, or abandoned; notification scheduling, suppression, opening, and whether its destination was reached; and in-app prompts shown, dismissed, or acted on. Where you search, we count that you searched, never what you typed.
• It also carries your device model, operating system, language, app version, and an approximate country derived from your IP address. We do not put the IP address itself into our analytics, though our providers process it in transit (see Service providers).
• Your choice, and it is off until you make it. Analytics is off by default everywhere. Frazzle asks once, you can decline, and nothing is collected unless you allow it. You can change your mind anytime in Settings.
• No advertising. No advertising identifier is used and ad personalisation is disabled.
• Crash reports carry the error and stack trace, device model, operating system and app version, and an installation identifier, stripped of any profile, age, scenario, or free-text data. Firebase keeps these for about 90 days.

Remote content and audio

Hard Moments audio and app content may be fetched from Firebase Hosting or Cloud Firestore and cached on your device. As with any web request, Google and Firebase may receive ordinary network information, including your IP address and app or device metadata, while serving these requests. Firebase publishes its own processing and retention details in its privacy documentation.

Subscriptions and purchases

Frazzle offers an optional paid subscription (monthly or annual), with a free trial for eligible App Store accounts. You do not need an account to use or to buy it.

• Apple processes the payment. The purchase happens through the App Store using your existing Apple account. Frazzle never sees or stores your card number or Apple ID; Apple handles billing under its own privacy policy.
• RevenueCat verifies the purchase. We use RevenueCat to confirm and manage your membership. To do this it processes your purchase history and subscription status (which product, whether a trial is active, renewal and expiry, and purchase events) and the App Store receipt for the transaction. This is used for the app to work and for subscription analytics, as RevenueCat's role requires.
• Tied to an anonymous identifier, not your name. Because there are no accounts, RevenueCat identifies your membership by an app-generated identifier, not your name, email, or your child's details. RevenueCat publishes its handling in its privacy policy.
• Subscription analytics. If analytics is on, we record fixed, non-personal events such as the paywall being shown, a plan selected, and a purchase started, completed, cancelled or restored. These carry no card details, no name, and none of the words you write.
• Restoring membership is separate from your plans. Restore purchases asks the App Store to re-confirm a subscription you already bought, so your access follows you to a new device or after reinstalling. It does not restore your on-device plans, reflections, or Journey history, which stay only on the original device and are not backed up to us.
• Retention. Purchase records are retained by Apple and RevenueCat under their own rules while you have a membership and as their billing and legal obligations require. Cancelling in App Store settings stops future renewals; managing or cancelling is done through Apple, not through us.

Local notifications and your lock screen

Frazzle can remind you of your own plans and send an occasional nudge to come back. These are handled in a deliberately private way.

• Local, never push. There is no Firebase Cloud Messaging, no push token, and no messaging server. A reminder carries the line you wrote, composed and scheduled on your phone. Its text is never sent anywhere, and we could not message you even if we wanted to.
• Separate controls. There are individual switches for plan reminders, activity reminders, and come-back nudges, plus one master off. Each is off until you turn it on, and turning it off takes effect immediately.
• Sensible limits you can shape. Recurring reminders normally run for two weeks and then ask whether to keep going. Quiet hours default to 10pm to 7am and can be adjusted within supported limits. Activity reminders are capped, and reminders you set yourself take priority. Come-back nudges are a short, limited sequence, not a permanent drip.
• Discreet by default. A reminder's lock-screen wording is discreet unless you choose more detailed wording, and a child's name is never included in a notification.
• Follows the selected child. Reminders are delivered for the child currently selected; the other child's saved reminders take over when you switch profiles.
• What we count. If analytics is on, we record only a fixed notification category, how many occurrences were scheduled, why one was suppressed, and whether one was opened. Never its text.

Service providers and overseas processing

We rely on a few processors, and their servers may be located outside your country, including in the United States. Such transfers rely on standard contractual protections.

• Google (Firebase and Google Cloud) for analytics, crash diagnostics, app integrity, and content delivery.
• Apple for App Attest on iOS and for App Store payment processing.
• RevenueCat for verifying and managing subscriptions (purchase history and status).
• Cloudflare for this website's cookieless visitor analytics (see below).
• We do not sell your data, and we do not share it for advertising.

This website

Everything above describes the Frazzle app. This website, frazzleapp.com, uses Cloudflare Web Analytics to count visits.

• No cookies and no cross-site tracking, which is why there is no cookie banner.
• No personal data. It records only aggregate, non-identifying signals: page views, how long a visit lasts, the country a visit came from, and which site referred you. Cloudflare processes ordinary network information such as an IP address to produce these counts, without building a profile of you.

Retention, export, and deletion

In the app you can, at any time:

• Delete a single plan, delete a child profile, clear downloaded content and cache, or delete all local app data. Uninstalling the app also removes local data.
• Export your data by copying it or sharing it as a file through your device's share sheet. Once you send it to another app or place, it is under your control and outside ours.

A few honest notes. Some manually recorded progress can remain after you delete an individual plan, and clears only when you delete the child profile or all local data. Deleting local data does not reach information already transmitted: any analytics you allowed and crash diagnostics follow our providers' own retention rules (for example, Firebase crash data is kept for about 90 days). Neither carries your name or a stable Frazzle identifier, so neither can be individually located to remove.

Children's information

Frazzle is designed for parents to use. It does not knowingly collect personal information directly from children. What it holds about a child is a chosen alias and a broad age range, stored on the parent's device and never uploaded.

Your choices and consent

• Turn analytics on or off anytime in Settings.
• Turn reminders on or off, all of them or one kind at a time, in the app and on your phone.
• Choose discreet or detailed lock-screen wording.
• Export, clear cache, or delete all local data.

Access, correction, and complaints

Because there are no accounts and your family's information stays on your device, there is no server-side profile for us to retrieve or correct. The app itself is where you view, change, and delete it. For questions, requests, or a complaint, including rights under the GDPR, UK GDPR, CCPA, or the Australian Privacy Principles, email privacy@frazzleapp.com. If you are in Australia and are not satisfied with our response, you can contact the Office of the Australian Information Commissioner.

Changes to this policy

If the app's data practices change, we will update this page and the in-app "Your privacy" screen before the change takes effect, and revise the date above.

Contact

Questions about your privacy? Email privacy@frazzleapp.com.