Legal
Privacy Policy
Versions. This policy describes version 1.0.3 of the app, and it also applies to earlier versions that are still installed. The in-app summary in version 1.0.3 shows version 2.5, written as if RevenueCat's subscription reporting to Meta were switched on; this version governs. Version 1.0.2 works as described here, except that it does not send the story-progress event in section 4.2, and on Android it has no Ad measurement setting and does not ask first in Canada and Australia: it starts Meta's SDK after “Agree & Continue” there too (section 4.5). Where an earlier version (1.0.1 or before) works differently:
- it does not show the welcome acknowledgment in section 1;
- it asks for a Parent PIN before parent-only areas and the subscription screen; the PIN is checked on the device, and only a derived verification value is kept, in the device's secure storage;
- it does not send the usage statistics in section 4.2 (versions before 1.0.1 may still try to send their older analytics events, which our server no longer accepts);
- it does not include Meta's SDK and sends Meta nothing (section 4.5). On iPhone and iPad, version 1.0.1 already makes the Apple install-attribution call described in section 4.4;
- RevenueCat receives no tracking choice from it.
Updating an installation that began on version 1.0.1 or earlier does not show the welcome and does not start Meta's SDK.
In short
Breathe Together Stories™ is built to respect your family's privacy.
- You do not need an account. There is no sign-up, password, or name-linked account profile on our servers.
- On a new installation, the first welcome screen asks the adult setting it up to confirm they are 18 or older, agree to the Terms of Service, and acknowledge this policy, with one “Agree & Continue” button. The welcome then offers five optional story preference questions, which can be skipped.
- The app no longer asks for a Parent PIN. Purchases are confirmed only by Apple's or Google's own purchase sheet and authentication.
- Preferences, Favorites, and your answers to the five optional story preference questions stay on your device. The answers are never sent anywhere.
- Starting with version 1.0.2 the app sends a small set of usage statistics to our own server. They contain no name, account, advertising identifier, device identifier, or installation identifier, and no identifier links one event to another. They are not collected on devices set to a region in the European Economic Area, the United Kingdom, or Switzerland, or to a European time zone. See section 4.2.
- The app shows no advertising. To measure whether our Facebook and Instagram ads lead to installations, the app sends Meta an install measurement once: on iPhone and iPad only if you choose “Allow” when iOS asks; on Android in Canada and Australia only if you choose “Allow” when the app asks; and on Android in the United States and New Zealand after the welcome, unless you turn it off. On Android it never includes the device's advertising ID. This measurement is not offered in the European Economic Area, the United Kingdom, or Switzerland. Meta may also use this information to target and deliver ads. You can turn all of this off at any time; see section 4.5.
- Apart from that Meta measurement, there is no third-party analytics software inside the app. We do not sell or rent your information, and apart from that measurement we do not share it for advertising.
- Separately, the iOS app calls Apple's SKAdNetwork/AdAttributionKit for privacy-preserving install attribution; Apple may send a postback to an eligible ad network and may also send us a copy of it. From version 1.0.3, the app can let RevenueCat report trial starts and subscription payments to Meta for the same installations (see section 4.5). That reporting is switched off, and we will update this policy before switching it on. Our own servers send nothing to Meta.
- The app contacts RevenueCat when it starts, including before a purchase. Apple or Google and RevenueCat process applicable payment and subscription information.
- Some older Android versions may still show a former story-personalization feature. New requests are rejected, and no new stories are created. See section 4.3.
- This website, separately from the app, uses cookieless Plausible Analytics to count visits and store-button taps. See section 10.
1. Who we are and who uses the app
Breathe Together Stories™ is owned and operated by Maxem Six, LLC. Maxem Six, LLC is the controller responsible for the processing described in this policy.
Maxem Six, LLC1401 21st St, Ste RSacramento, CA 95811United States
You can reach us about privacy at privacy@breathetogetherstories.app.
The app is intended for adults aged 18 or older — parents, guardians, and caregivers — to choose and use together with children at bedtime. It is meant to be set up and operated by adults and shared with children. Its stories and breathing activities are family-oriented, and children may listen or participate with the adult.
The welcome acknowledgment. On a new installation, the first welcome screen says, under its “Agree & Continue” button: “By tapping Agree & Continue, you confirm you’re 18 or older, agree to our Terms of Service, and acknowledge our Privacy Policy.” The app stores on the device only that this was acknowledged, the Terms of Service and Privacy Policy versions shown, and the date; no identifier is created. Families updating from an earlier version do not see the welcome. On iPhone and iPad, the acknowledgment is not consent to tracking: tracking is a separate choice made in iOS's own dialog. On Android in the United States and New Zealand, tapping “Agree & Continue” is what starts the Meta measurement; in Canada and Australia it is not, and the measurement is a separate choice (section 4.5).
No Parent PIN. The Parent PIN that earlier versions used for parent-only areas has been removed. The Family Backpack (settings, Restore Purchases, Manage Subscription, and links), the library, and the subscription screen open without one. Apple's or Google's own payment authentication protects purchases; see section 5.
2. There is no account
The app has no account system. There is no registration, sign-in, password, email sign-up, or social login. We do not create a name-linked account profile. The app does not access an advertising identifier on Android; on iPhone and iPad, Meta's SDK reads the advertising identifier (IDFA) only if you choose “Allow” in iOS's tracking dialog (section 4.5).
3. What stays on your device
Preferences, Favorites, and playback progress are stored on the device. Earlier app versions stored setup answers locally; this release removes those answers when it starts.
The welcome acknowledgment. On a new installation, a record that the acknowledgment in section 1 was made, with the policy version and the date.
Meta measurement marker. Once Meta has received the install (section 4.5), a marker that it has, so the app does not start Meta's SDK again. Meta's SDK also keeps the install identifier it created, and a note of when it reported the install, on the device.
An old Parent PIN verifier. This version does not create or store a PIN. If an earlier version set one, its verification value may remain in the device's secure storage. See section 5.
Optional story preferences. When the app first opens, a short welcome offers five optional story preference questions, which can be skipped. They cover when you usually listen, what makes bedtime tricky, story length, narrator, and the kinds of stories you like. They ask nothing about a child's name, age, birth date, or health, and there is no free-text answer. Your answers are saved only in the app's storage on this device and are used only on the device to choose which story to suggest, which story length to show first, and which narrator to start with. They are never sent to us, RevenueCat, Apple, Google, Meta, or any analytics service. You can change or clear them in the app at any time.
Usage-statistics record. Where usage statistics are collected (section 4.2), the app keeps one local record used to work out the flags it sends, such as the day it was installed, the last day, week, and month it was opened, when it last went to the background, and whether the subscription screen has been shown, plus any statistics waiting to be sent (at most 300, none older than seven days). This record itself is never sent.
Some older Android versions may still display a former story-personalization option. The service rejects requests through it, so no new stories are created.
4. What leaves your device
4.1 Purchases and subscriptions
Apple processes iPhone and iPad payments through the App Store; Google processes Android payments through Google Play. We do not receive your payment card, billing address, Apple Account, or Google account details. We use RevenueCat to support subscription purchases, verify entitlements, and restore purchases. The app contacts RevenueCat when it starts. Requests include an anonymous RevenueCat App User ID and subscription information, along with app, device, and network information such as the request IP address. On iPhone and iPad, RevenueCat also records the device's tracking choice (allowed or not) from iOS's tracking dialog (section 4.5) with the anonymous purchase record. From version 1.0.3, on installations where Meta's SDK has started and, on Android, while Ad measurement is on (section 4.5), the app also gives RevenueCat Meta's install identifier for this installation, so that RevenueCat can report subscription events to Meta (that reporting is switched off; see section 4.5). The app keeps RevenueCat's automatic collection of device identifiers turned off, so this does not also give RevenueCat the advertising identifier or ask it to record your IP address. We do not configure RevenueCat to save IP addresses as subscriber profile attributes; routine requests may still expose an IP address to the service. On Android, RevenueCat's software may also store its anonymous App User ID in Google's Block Store on the device, with Google's cloud backup turned on, after a purchase or when the app is opened. Where Google's backup and restore are available, this lets RevenueCat connect a reinstalled app, or the app on a new device, to the earlier anonymous ID so that purchases can be found again. Block Store is a Google service governed by Google's terms. RevenueCat processes information under its applicable privacy policy and data-processing terms. RevenueCat also sends our server a notice of each subscription event (for example a trial started, a renewal, a cancellation, or a refund). From each notice we keep only: the event's identifier, type, and time; whether it came from a live or a test purchase; the store; the product, any product it was changed to, and the kind of period (such as a trial, an introductory offer, or a regular period); the price and currency, the price in the currency paid, and the share of the price we receive after the store's fee; whether a trial converted to a paid subscription; whether an offer code was used, but not the code; and any cancellation or expiration reason. Our server also records when the notice arrived. We do not keep the RevenueCat App User ID, its aliases, transaction numbers, country, subscriber attributes, or any other field of the notice. We have not independently verified its retention period.
Google processes Android billing and related information under its own privacy terms.
4.2 Usage statistics
Starting with version 1.0.2 the app sends a small set of usage statistics to our own server so we can count app opens, which stories are started, how far they play, and which are finished, and how the subscription screen performs. Each event contains only: the event type (for example first open, first open of the day, app session started, welcome finished, story started, story progress, story finished, subscription screen shown, plan chosen, purchase started, purchase completed or not, or restore result); the story's catalog identifier, its length, and whether it was the free story, a subscriber story, or a short preview, where relevant; for story progress (from version 1.0.3), which of three points playback reached: 25, 50, or 75 percent of the story (the exact playback position is never sent); simple flags worked out on the device, such as first open of the day, week, or month, roughly how long ago the app was installed (exact only for 0, 1, 7, and 30 days; otherwise a range such as 2–6 or 31+), and whether the subscription screen was being shown for the first time; whether a trial or subscription is active, the plan chosen, and a broad purchase-error category; the app version and build, the platform (iOS or Android), and whether the build is a store or test build; the time, rounded down to the minute; and a random event number used only to avoid counting an event twice. A new event number is made for every event, so the number cannot link events together. Our server also records, to the second, when each upload arrives. The app sends events in small batches, so events uploaded together share that arrival time for as long as individual events are kept (30 days).
On Android, the first-open event may include the campaign labels (source, medium, and campaign) of the Google Play link that led to the install, read from the Google Play install referrer. Click identifiers and other link parameters are never sent.
Usage statistics never include a name, account, email, advertising identifier, device identifier, session or installation identifier, device model, operating system version, language, region, or time zone, story preference answers, or any text you type. Events are not linked to a person or device, and no identifier links one event to another.
Our server receives the network address of each request, as any internet service does, but does not store it with these statistics or log it. Individual events are deleted after 30 days; after that we keep only daily totals, which contain no identifiers. We do not share these statistics with Meta or any advertising or analytics company, and we do not use them for advertising or to build a profile of anyone. They contain no IDFA and are not linked to the Meta measurement in section 4.5.
The app does not collect usage statistics on devices set to a region in the European Economic Area, the United Kingdom, or Switzerland, or to a European time zone. On those devices the app stores and sends nothing for usage statistics.
Analytics in earlier versions. Earlier app versions could send limited usage events, grouped by a random installation identifier, if analytics had been allowed. That ingestion was disabled on November 2, 2026, and our server no longer accepts those events. Information previously received is handled under the retention periods below. This release clears events earlier versions left queued on the device and removes the installation identifier they used.
4.3 Older Android versions
Some older Android versions may still show a former story-personalization feature. New requests are rejected, and no new stories are created.
4.4 iOS install attribution
The iOS app calls Apple’s SKAdNetwork/AdAttributionKit API once per app installation with constant conversion value 0 and coarse value “low.” The app sends no event or installation identifier directly to an ad network through this call. Apple may send a privacy-preserving attribution postback to an eligible ad network, including Meta if a qualifying Meta ad led to the install. This system call is separate from the usage statistics in section 4.2 and from the Meta measurement in section 4.5, and does not require an App Tracking Transparency prompt. Apple may also send us a copy of the SKAdNetwork or AdAttributionKit postback. It contains campaign and ad-network identifiers and a coarse value, nothing about the person or device; we keep it as received to count attributed installs. Our own servers send nothing to Meta.
4.5 Advertising measurement (Meta)
The app uses Meta's software development kit (SDK) to tell Meta when an installation happens, so we can see whether our ads on Facebook or Instagram led to it. How this works differs by platform.
On iPhone and iPad
The request. On a new installation, iOS's own App Tracking Transparency dialog appears once, on its own, when the welcome reaches the screen that offers the free story — several screens after the acknowledgment in section 1, which is not tracking consent. It asks whether Breathe Together Stories™ may track you. Nothing in the app waits for the answer. iOS does not allow the request on child Apple Accounts. Families updating from an earlier version do not see the welcome, so the app does not show them this request.
If you choose “Allow”. Only then does the app start Meta's software development kit (SDK), once, on that launch. It sends Meta an install event and an app-activation event, which includes a session identifier; the SDK's own tracking-status message; and an event recording the SDK's attribution-measurement setting. These carry your device's advertising identifier (IDFA), an install identifier that Meta's SDK creates, device details (model, iOS version, language or locale, time zone, screen size and scale, carrier, and number of processor cores), the app's version and build, the app's URL schemes, and your IP address. The SDK also fetches its own configuration from Meta. The app does not start the SDK again on later launches. If you allow tracking later in Settings instead, the same happens once, on the next launch.
If you do not allow it. If you choose “Ask App Not to Track”, if tracking is turned off in Settings, or on a child Apple Account, the app never starts Meta's SDK and sends Meta nothing.
Changing your choice. You can change it at any time in Settings → Privacy & Security → Tracking. Turning tracking off does not recall information already sent to Meta.
On Android
In the United States and New Zealand, the app starts Meta's SDK once on a new installation, right after the adult taps “Agree & Continue” on the welcome (section 1), unless Ad measurement has been turned off in Family Backpack.
In Canada and Australia, agreeing to the Terms is not this consent: the app asks first. When the welcome reaches the screen that offers the free story, it shows a short explanation with two equal choices, “Allow” and “Don't Allow”. Only “Allow” starts Meta's SDK; “Don't Allow”, or closing the explanation, leaves it off, and everything in the app works the same. The app does not ask again; Family Backpack → Privacy Choices → Ad measurement changes the choice at any time. Until we switch this choice on, the app does not offer it and does not run this measurement on Android in Canada and Australia. To tell where it is, the app uses the device's time zone, its language and region setting, and the Google Play country; any sign of Canada or Australia counts. Your choice is kept on the device, with the date it was made.
What is sent. Meta's SDK sends Meta one install event, which carries an install identifier that Meta's SDK creates; the Google Play install referrer for this installation (for an install from a Meta ad, it contains Meta's own encrypted campaign information); where the Facebook app is installed on the device, the attribution identifier the Facebook app provides; device details (model, Android version, language or locale, time zone, screen size and density, carrier, number of processor cores, and storage capacity and free space); the app's version and build; and your IP address. The SDK also fetches its own configuration from Meta.
The app does not have Android's advertising-ID permission, and the SDK is set not to collect the advertising ID. Once Meta has received the install, the app does not start the SDK again on that installation; if the device was offline, it tries again on a later launch until the install is received. Families updating from an earlier version do not see the welcome, so the app does not start the SDK for them. Turning Ad measurement off keeps the SDK from starting again and stops the subscription reporting below (see “Turning it off”).
Subscription events (from version 1.0.3)
Status. This reporting is switched off: RevenueCat reports nothing to Meta. We will update this policy before switching it on.
What is reported. RevenueCat, which runs our subscriptions (section 4.1), would report to Meta when a free trial starts and when a subscription is bought, converts from a trial, or renews. Each report carries the event type and time, the price and currency, an order number, Meta's install identifier for this installation (the one Meta's SDK created, as described above), a one-way hashed form of RevenueCat's anonymous ID for this installation, on iPhone and iPad the device's identifier for vendor (IDFV), and app and device details RevenueCat last saw (such as app version, operating system version, device model, and language). Hashing does not make these reports anonymous: Meta can still connect them to the installation. Cancellations, refunds, and expirations are not reported to Meta.
When (if switched on). On iPhone and iPad, only if you chose “Allow” in iOS's tracking dialog: the app gives RevenueCat Meta's install identifier only while tracking is allowed and removes it from RevenueCat the next time the app opens after tracking is turned off, and RevenueCat sends App Store events to Meta only when iOS reports tracking as allowed. On Android, only while Ad measurement is on for the installation: in the United States and New Zealand from “Agree & Continue” until it is turned off, and in Canada and Australia only after “Allow”. Neither happens in the European Economic Area, the United Kingdom, or Switzerland.
On both platforms
Technical reports. If Meta's SDK itself crashes or stops responding during the one session in which it runs, Meta's own settings can have it send Meta a technical report about the SDK's code.
What Meta does not receive. Meta receives no story, listening, preference, child, or screen information, and no events other than the install, and RevenueCat's subscription events only if that reporting is switched on. The usage statistics in section 4.2 are not sent to Meta and are not linked to this measurement.
Where it is not offered. As with the usage statistics in section 4.2, the app does not start Meta's SDK, and on iPhone and iPad does not show the tracking request, when the device's time zone or region is in the European Economic Area, the United Kingdom, or Switzerland, or when neither can be read. If RevenueCat was given Meta's install identifier while the device was somewhere this measurement runs, the app removes it the next time it opens where it does not.
Why. To measure whether our ads on Facebook or Instagram led to the installation or a subscription. Breathe Together Stories™ shows no ads.
Meta's use. Meta is a separate company and receives this information under its own terms and Privacy Policy. Besides measuring our ads, Meta may combine it with other information it holds and use it for its own purposes, including to target and deliver ads (on Facebook, Instagram, and elsewhere) and to improve its products.
Turning it off. On Android, turn off Family Backpack → Privacy Choices → Ad measurement. The app then removes Meta's install identifier from RevenueCat and sends that change to RevenueCat at once (if the device is offline, the next time the app is online), so RevenueCat no longer reports later subscription events to Meta, including renewals it processes while the app is closed, and the app does not start Meta's SDK again. On iPhone and iPad, turn tracking off for Breathe Together Stories™ in Settings → Privacy & Security → Tracking: from the next launch the app sends Meta nothing and removes Meta's install identifier from RevenueCat in the same way. Deleting the app does not by itself remove it; if you have deleted the app, write to privacy@breathetogetherstories.app with the order number from your Google Play or App Store receipt, and we will use it to find the anonymous subscription record and remove Meta's install identifier from it. On any device, Meta's Accounts Center, under “Your activity off Meta technologies”, lets you disconnect past activity that apps and websites have shared with Meta and turn off future activity, and the Digital Advertising Alliance's page at aboutads.info/choices offers general opt-outs from interest-based advertising. None of these recalls information already sent.
On iPhone and iPad, RevenueCat also records the device's tracking choice (allowed or not) with the anonymous purchase record described in section 4.1.
4.6 Email you send us
Contact Us opens your own email app with our address filled in. The app does not send the message for you or attach diagnostic, device, or app data. We use what you write only to respond to you.
4.7 Purposes and legal bases
We use information to provide the app, manage subscriptions, respond to messages and privacy requests, count app use and improve the app using the usage statistics described in section 4.2 where they are collected, measure whether our ads led to the installation or a subscription (section 4.5; on iPhone and iPad only where you allow tracking), and meet legal obligations. The app does not make decisions based solely on automated processing that produce legal or similarly significant effects.
4.8 Recipients and service providers
Depending on the feature, recipients include Apple for App Store payment processing and iOS system attribution; Google for Play billing and its diagnostics; RevenueCat for subscription infrastructure; Meta for the measurement in section 4.5 (installs on Android once, after the welcome, and subscription events reported by RevenueCat only if that reporting is switched on; on iPhone and iPad only if you allow tracking); BTS-operated infrastructure for the usage statistics in section 4.2, subscription event notices from RevenueCat, attribution postback copies from Apple, and limited analytics previously sent by earlier app versions; and email providers when a person chooses to email us. Apple may send an attribution postback to an eligible ad network. Usage statistics and analytics are not forwarded from BTS to Meta or any advertising or analytics company.
5. Purchases are confirmed by Apple or Google
This version does not ask for a Parent PIN, and it does not create or store one. Every purchase is confirmed only through Apple's or Google's own purchase sheet and authentication. That store authentication, including Apple's Ask to Buy and Screen Time where a family uses them, is the purchase control.
If an earlier version set a Parent PIN, its verification value may remain in your device's secure storage — the iOS Keychain, or the Android Keystore-backed encrypted storage. The PIN itself was never stored as entered, and was never transmitted anywhere.
6. Children’s privacy
The app is intended for a parent or caregiver and child to use together. Children may listen. They have no accounts or profiles in the app. The usage statistics in section 4.2 contain nothing about who is using the app and cannot be linked to a person or device. The optional story preference questions in section 3 stay on the device and ask nothing about a child's identity. The current app does not ask for or send a child's name. Some older Android versions may still show a former story-personalization feature. New requests are rejected, and no new stories are created.
Earlier app versions may have stored setup answers on the device. This release removes those answers, and the analytics queue earlier versions left, when it starts. Earlier versions could send certain app-use events if analytics had been allowed; see section 4.2. The app does not verify that the person opening it is a parent or caregiver, or that they are 18 or older.
The Meta measurement in section 4.5 starts only after an adult's 18-or-older acknowledgment on the welcome; on iPhone and iPad it also needs “Allow” in iOS's tracking dialog, which iOS does not offer on child Apple Accounts, and on Android in Canada and Australia the adult's “Allow” in the app's own choice. Nothing about a child is sent to Meta.
The purchase information described in section 4 concerns the adult who makes the purchase, not the child. The Parent PIN that earlier versions used for parent-only areas has been removed; Apple or Google payment authentication protects purchases.
RevenueCat and store billing process purchase and restore information, and Meta receives the install measurement in section 4.5 (subscription events only if that reporting is switched on; on iPhone and iPad only where tracking is allowed). If you believe a child has sent us personal information outside these described flows, contact privacy@breathetogetherstories.app.
7. Retention and deletion
Information stored on the device remains while the app is installed. This release removes earlier setup answers and queued analytics events when it starts. Usage statistics (section 4.2) are deleted after 30 days; daily totals, which contain no identifiers, are kept. Subscription event notices from RevenueCat are kept as business and accounting records, and attribution postback copies from Apple are kept to count attributed installs. Previously received production analytics events from earlier versions are deleted after 90 days; other non-production events are deleted after 14 days. Server system logs from the period when earlier app versions were in use, which can include information those versions sent with their requests, are still kept; they are removed by the server's routine log rotation rather than on a fixed schedule. Information sent to Meta (section 4.5) is kept under Meta's own policies. Purchase and restore records are handled by Apple or Google and RevenueCat under their applicable terms; some record of a purchase must persist for Restore Purchases to work, and for tax and accounting obligations.
Deleting the app removes setup answers, story preference answers, the suggested plan, Favorites, playback preferences, any saved stories, the welcome acknowledgment record, the usage-statistics record, queued analytics events, and the installation identifier. On Android, a RevenueCat App User ID backed up to Google's Block Store (section 4.1) may be restored after a reinstall or on a new device; this is how purchases can be found again. A Parent PIN verifier left by an earlier version is held in platform secure storage and may follow different uninstall behavior; this policy does not claim that deleting the app removes it. Deleting the app does not delete information already sent to us or to Meta (section 4.5). Usage statistics carry no identifier, so they cannot be found and deleted for one person; they are deleted after 30 days. There is no account to delete.
For anything held outside your device — support emails, a purchase record, or information connected with an earlier version of the app — email privacy@breathetogetherstories.app and tell us what you'd like removed. We cannot delete records Apple, Google, or Meta hold under their own policies, and deleting a purchase record may make Restore Purchases stop working for that purchase.
8. Security, and its limits
Any Parent PIN verification value left by an earlier version stays in your device's secure storage. Purchase traffic and requests to our services are encrypted in transit. Favorites, story preferences, playback preferences, and story progress are stored in ordinary app storage, protected by your device's app isolation and its own encryption when a passcode is set. Since there is no PIN, anyone with access to an unlocked device may be able to open the Family Backpack and subscription screen; purchases still need Apple's or Google's authentication. No method of storage or transmission is completely secure.
8.1 International transfers
Maxem Six, LLC is established in the United States. Information sent to us, including usage statistics, subscription event notices, and privacy correspondence, may therefore be processed in the United States, including information from Canada (and Québec), Australia, and New Zealand. Apple, Google, RevenueCat, and Meta (for the measurement in section 4.5) may also process information in countries outside the country where it was collected, as described in their own privacy terms.
Where GDPR requires an appropriate safeguard for a transfer from the EEA to a country without an adequacy decision, applicable providers may use safeguards such as the European Commission's Standard Contractual Clauses. You may contact privacy@breathetogetherstories.app to ask about the safeguard applicable to a particular transfer and how to obtain a copy.
9. What we do not do
The app shows no ads or sponsored content and has no crash-reporting or diagnostics service of our own. It does not access Android Advertising ID: the Android app does not have the advertising-ID permission, and Meta's SDK is set not to collect it. On iPhone and iPad, Meta's SDK reads the IDFA only if you choose “Allow” in iOS's tracking dialog, and only for the Meta measurement in section 4.5. There is no tracking across other apps or websites apart from the Meta measurement in section 4.5. The app contains no social-media, marketing-pixel, marketing-attribution, or third-party analytics SDK other than Meta's SDK for that measurement. It does not use session recording or screen capture. iOS install attribution through Apple’s SKAdNetwork/AdAttributionKit system API is described in section 4.4. Story audio and artwork are bundled rather than streamed.
9.1 Your choices and rights
You can clear Favorites, change or clear story preferences, or delete the app entirely. On iPhone and iPad, you can change your tracking choice in Settings → Privacy & Security → Tracking (section 4.5); on Android, Family Backpack → Privacy Choices → Ad measurement. Those controls affect information stored on this device; they do not erase information already sent to our service or providers. “Turning it off” in section 4.5 also explains Meta's own controls.
Withdrawing consent. Where we rely on your consent (the tracking choice on iPhone and iPad, and the Ad measurement choice on Android in Canada and Australia), you can withdraw it at any time, as easily as you gave it, as described in section 4.5. Withdrawing does not change anything else in the app.
Depending on where you live, you may have rights to access, correct, or delete personal information we hold about you, or to object to certain processing. Depending on your use of the app, we may hold a purchase record, emails you sent us, previously collected analytics events, and information connected with earlier versions of the app. Write to privacy@breathetogetherstories.app and we will respond.
If GDPR applies to the processing of your personal data, you may have the right to request access, correction, deletion, restriction of processing, or portability of personal data, and to object to processing based on legitimate interests. These rights may be limited where an exemption applies or where we cannot identify information as relating to you.
To exercise a right, email privacy@breathetogetherstories.app. We may need information sufficient to verify and respond to the request, but we will not ask for more than is reasonably necessary. You also have the right to lodge a complaint with the data protection supervisory authority where you live, work, or believe an infringement occurred.
Complaints. If you are not satisfied with our answer, you can contact your privacy regulator: in Canada, the Office of the Privacy Commissioner of Canada (in Québec, the Commission d'accès à l'information du Québec); in Australia, the Office of the Australian Information Commissioner; in New Zealand, the Office of the Privacy Commissioner; in the United States, your state's attorney general.
The app does not collect usage statistics, show the iOS tracking request, or start Meta's SDK on devices set to a region in the European Economic Area, the United Kingdom, or Switzerland, or to a European time zone. Earlier app versions may have sent limited usage events; information previously received is handled under the retention periods above.
10. This website
This section applies only to this website, breathetogetherstories.app. It does not change anything above about the app, which contains no third-party analytics software other than the Meta measurement described in section 4.5.
We use Plausible Analytics, a service of Plausible Insights OÜ in Estonia, to count visits, understand which websites and campaigns bring visitors here, and count taps on available store buttons. For each visit it records the page, the referring website, campaign tags in the link you followed (such as utm_source or utm_campaign), the browser, operating system, and device type, an approximate country, region, and city worked out from your IP address, and how long the page was viewed and how far it was scrolled.
There are no cookies and no persistent identifier, and nothing is stored on your device. To count unique visitors for a day, Plausible combines your IP address and browser details with a random value that it deletes every 24 hours; it does not store your IP address. Before anything is sent to Plausible, this site removes everything from the page address except the path and campaign tags, so click identifiers added by advertisers such as Facebook or Google are not sent to Plausible, and it removes the query from the referring address. We see only aggregate statistics. There is no advertising pixel, retargeting, fingerprinting, cross-site tracking, or profile of any visitor.
If your browser sends a Global Privacy Control or Do Not Track signal, this site does not run analytics, and nothing is sent to Plausible.
The website does not ask for names, email addresses, or information about children; email links open your own email app. Like any website, it is delivered by a hosting provider (Netlify), which necessarily receives your IP address to send you the page.
Plausible processes this information for us under its data processing agreement and stores it in the European Union, and keeps these statistics for as long as our account is active. Where GDPR applies, our legal basis is our legitimate interest in understanding which of our outreach reaches parents, limited by the safeguards above; you can object by emailing privacy@breathetogetherstories.app.
Available store buttons take you to Apple's App Store or Google Play, where their privacy policies apply. When a Google Play link is available, it may carry a campaign tag naming this website so the store can report installs from here; the tag does not identify you.
11. Contact Us
Questions about this policy or your information:
privacy@breathetogetherstories.app
This address reaches our Privacy Officer, who is responsible for how we protect personal information, including as the person in charge of the protection of personal information under Québec law.
Breathe Together Stories™ is owned and operated by Maxem Six, LLC.
Maxem Six, LLC1401 21st St, Ste RSacramento, CA 95811United States
See also our Terms of Service and Support page.
