Privacy Policy
Bellows is a custom breathwork app developed by a single individual. This policy explains what data the app handles on your device, what is shared with Google Play, and what is never shared.
What the app stores on your device
All of the following stays on your phone. It is never uploaded to any server we operate, and we do not operate any server that receives your data.
- Sessions, sets, patterns, phases — every breath session you create, edit, duplicate, or import. Includes phase durations, lung-fill depths, and sound names.
- Favorites — which sessions you've marked as favorites.
- Sound and session preferences — your selections in the builder, recently used sounds, etc.
- Purchased entitlements — a cache of the SKU strings you have bought through Google Play, stored via Android DataStore. Used only to render "Owned" or "Not owned" UI in the app.
- Event log — a local table recording up to 500 recent app events for your own debugging (for example "paywall viewed", "purchase completed"). You can inspect, export, and clear this list from Settings → tap Version 1.0 seven times → Event Log. The event log never leaves the device.
The app's database is bellows_db (Room or SQLite) plus entitlements (DataStore Preferences). Both live in app-private storage and are removed when you uninstall the app. There is no cloud backup, no sync, no remote storage.
What is sent to Google
The app contacts only Google Play infrastructure, and only for the actions described below. No other network calls are made.
- Google Play Billing — when you tap Buy, Unlock, or Tip, the app talks to your installed Play Store to fetch product details, present the official Play purchase dialog, and verify your purchase history. Google handles payment, receipts, refunds. We receive a one-way notification from Play confirming the purchase; we do not send Play any of your session content.
- Google Play Asset Delivery — when you purchase a paid sound or session pack, Google downloads the pack's MP3 or JSON files to your device's internal storage via Play's content delivery network. Files are stored under your app's private directory and are removed when you uninstall.
We do not use Firebase Analytics, Google Analytics, Crashlytics, ads SDKs, attribution SDKs, or any third-party telemetry. There is no firebase-analytics or firebase-crashlytics in the binary.
Permissions the app requests
com.android.vending.BILLING— required to make Play Billing purchases. No runtime prompt.INTERNET— used implicitly by Play Billing and Play Asset Delivery. The app itself does not initiate any HTTP requests.
The app does not request camera, microphone, location, contacts, storage, or any other runtime permission.
Account data
The app does not require an account. There is no sign-up, no sign-in, no email capture, no profile. Your Google account is involved only because Play Billing uses it for purchases; that data lives with Google, not with us.
Children
The app is rated Everyone. It does not target children and does not knowingly collect any data from anyone, including children under 13.
International transfers
The app does not transfer your data anywhere — there is no cloud, no sync, no analytics, no remote backup. The only data egress is to Google Play (per the section above) which operates its own compliance infrastructure per Google Play terms.
Your rights and choices
Because all data stays on your device, your controls are local:
- Delete a session — long-press a session in the library, tap Delete.
- Delete all app data — uninstall the app. This removes the database, DataStore, and any downloaded asset packs.
- Export your event log — Settings → tap Version 1.0 seven times → Event Log → Export CSV.
- Clear the event log — same screen, tap Clear.
Changes to this policy
If we ever change what the app does with data, we will update this document, bump the "Last updated" date, and ask you to accept the change on next launch. If the change is material (for example adding a new network call), the app will surface a re-consent dialog.
Contact
Questions, concerns, or data requests: hello@bellowscustombreathwork.com
Replace the address above with your real contact before publishing this page.
Data categories summary (for Play Console data-safety form)
| Category | Collected? | Shared? | Notes |
|---|---|---|---|
| Location | No | No | — |
| Personal info (name, email, address, phone) | No | No | — |
| Financial info (payment, credit) | No | No | Handled by Google Play; we never see it |
| Health and fitness | Yes (breath sessions on-device only) | No | Not shared with anyone; stays on your device |
| Messages | No | No | — |
| Photos and videos | No | No | — |
| Audio files | Yes (sounds you select; recorded breath cues are not captured) | No | — |
| Files and docs | No | No | — |
| Calendar | No | No | — |
| Contacts | No | No | — |
| App activity (interactions, search history) | Yes (event log on-device only) | No | — |
| Web browsing | No | No | — |
| App info and performance (crash logs, diagnostics) | No | No | — |
| Device or other IDs | No | No | — |
All "Yes" rows are on-device only. They are not transmitted to us, to Google, or to any third party.
Encryption: the app's local storage uses Android's app-private filesystem encryption on devices with a locked screen and a device PIN or biometric. We do not add additional application-layer encryption.