Prana Breath

Privacy Policy

How we handle information in connection with the Prana Breath app. Short version: we do not collect your personal data, we receive only crash reports and usage statistics that do not identify you and that you can turn off, and your backup stays in your own Google Drive.

Last updated
November 19, 2026
App
Prana Breath (“the App”)
Developer
Oleksandr Albul (“we,” “us,” “our”)
Contact
Email the developer

This Privacy Policy explains how we handle information in connection with the App, wherever you got it: Google Play or Huawei AppGallery. Please read it before using the App.

1. Summary in plain language

We built Prana Breath to work without collecting your personal data. We do not need it, we do not want it, and we do not have systems set up to gather it. There is no Prana Breath server that holds your sessions, your notes, your health data, or your settings. If a government body, court, or anyone else ever asked us to hand over that data, we would have nothing to give them, because it is not stored on our side.

The one thing the App sends to us is crash reports and usage statistics: which features are used and where the App fails, tied to a random ID that the App makes up and that says nothing about who you are. Both are on by default and you can turn either off at any time. Section 6 lists exactly what they contain and how long we keep them.

The App does offer two optional features that hand your data to a place you choose, never to us. You can back up your own data to your own Google Drive: the backup file is written into your Google account, and we never see it (section 4). And on Android you can save your sessions and health test results to Health Connect, the health data store on your own device, where your other health apps can use them if you let them (section 5).

2. What we do not collect

We do not collect, store, or process:

  • Your name, email address, or phone number
  • Your location
  • Your health, fitness, or breathing session data on any server we control
  • Your contacts, photos, or files
  • Your advertising ID, device ID, or any other identifier tied to who you are (the random ID in section 6 is made up by the App and is not linked to you)

The App does not require you to create an account with us, and we do not ask for personal information to use it.

3. No tracking or analytics SDKs inside the App

The App does not include third-party advertising SDKs, tracking pixels, fingerprinting tools, or analytics plugins that read your cookies, other apps, email, or similar data. We are not in the business of profiling users, and the App is built without the technical means to do so. Its crash reports and usage statistics (section 6) are our own code, and they go only to our own server.

4. Optional backup to your own Google Drive

The App can save a copy of your Prana Breath data to your own Google Drive, so that you can restore it after reinstalling the App or moving to a new device. This feature is entirely optional and is off until you turn it on. If you never use it, nothing in this section applies to you and the App never contacts Google Drive.

4.1 What we ask for, and why

When you enable backup, the App asks Google for a single permission:

Scope What it allows
https://www.googleapis.com/auth/drive.appdata Reading and writing files in the hidden, application-specific folder that Prana Breath creates inside your Google Drive

We request this one scope and nothing else. We do not request access to your Drive files, your email, your contacts, your profile, or any other Google service. You grant the permission on Google’s own consent screen, and you can refuse it and keep using the whole App as before.

4.2 What the App writes there

The backup file contains the data the App keeps on your device, such as your breathing patterns and their settings, your training history and progress, and your App preferences. It is your practice data, written in the App’s own format. We do not add identifiers, advertising IDs, or any tracking data to it.

4.3 What we cannot see

The drive.appdata scope grants access only to a hidden folder that the App itself created. Within that permission the App cannot see, list, read, modify, or delete any other file in your Google Drive. Your documents, photos, and everything else stay invisible to it.

Just as importantly: the backup travels from your device to your Google account. It does not pass through, and is not copied to, any server belonging to us. We have no ability to open your backup, and no copy of it exists on our side.

4.4 Limited use of Google user data

The App’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms, the data in that folder is used only to provide and improve the backup and restore feature you asked for. We do not transfer it to anyone, we do not use it for advertising, we do not sell it, and we do not allow humans to read it. None of that is a promise we have to work hard to keep, because the data never reaches us in the first place.

4.5 Your data is yours, and so is the responsibility for it

We deliberately built the backup this way so that you stay in control. That control comes with responsibility, and we want to be straightforward about it:

  • The backup lives in your Google account. Its safety depends on how you protect that account: your password, your two-factor authentication, and who else can reach your device or your Drive.
  • Google’s own terms and privacy policy govern that storage. Once the file is in your Drive, it is subject to Google’s practices, not ours.
  • We cannot recover a lost backup. If you delete it, lose access to the Google account, or the account is closed, the data is gone and we have no copy to restore from. Keeping your own additional copy of anything you cannot bear to lose is a good idea.
  • We cannot restore it for you, and we cannot read it for you. A request of the form “please retrieve my data” is one we are technically unable to fulfil, by design.

This is the trade we chose: no servers of ours means nothing of yours for us to lose, leak, or be compelled to hand over, and it means the copy in your Drive is yours to look after.

4.6 Turning it off and deleting the backup

You can stop using the feature at any time:

  • Revoke the permission at myaccount.google.com/permissions, which immediately ends the App’s access to that folder.
  • Delete the stored data from your Google Drive settings, under the section listing apps that store hidden application data, or by using the delete option in the App before you revoke access.

Revoking access does not affect the data on your device, and it does not affect your purchases or subscriptions.

5. Optional saving to Health Connect

On Android, the App can save some of your data to Health Connect, the health data store that is part of Android 14 and later, and an app from Google Play on earlier versions. This feature is entirely optional and is off until you turn it on, in the App under Settings › Data & privacy. If you never turn it on, the App never contacts Health Connect.

5.1 What the App writes

There are two switches, and each covers only what is listed next to it:

Switch in the App What is saved Health Connect data type
Sessions Each finished breathing or meditation session: when it started and ended, whether it was breathing or meditation, and the name of the practice Mindfulness
Health metrics Values you enter in the App’s health tests: heart rate, blood pressure, breathing rate, blood oxygen (SpO₂) and body temperature Heart rate, Blood pressure, Respiratory rate, Oxygen saturation, Body temperature

When a switch is turned on, the App also saves the matching data you recorded earlier, and from then on it keeps Health Connect up to date: a session or a reading you edit is updated there, and one you delete is deleted there. Your notes, ratings, breath holds and other test results are never saved to Health Connect.

5.2 What the App does not do

  • It does not read anything from Health Connect. The App asks only for permission to write, never to read, so it cannot see the data that other apps keep there.
  • The data does not reach us. It goes from the App to Health Connect on your device. It does not pass through, and is not copied to, any server belonging to us.
  • It is not used for anything else. The App’s use of Health Connect complies with the Health Connect Permissions policy, including its Limited Use requirements: the data is used only to provide the feature you turned on, and is not used for advertising, sold, or transferred to anyone.

5.3 Who else can see it

Once saved, the data is kept by Health Connect and controlled by you. Other apps on your device, such as Google’s or Samsung’s health apps, can read it only if you give them permission in Health Connect, and their own privacy policies then apply to what they do with it. Health Connect itself is provided by Google, and Google’s terms and privacy policy apply to it.

5.4 Turning it off and deleting the data

  • Turn a switch off in the App to stop saving. What was already saved stays in Health Connect.
  • Withdraw the permission at any time in Health Connect’s settings, under the App’s name. The App then stops saving, and its switch turns off.
  • Delete the saved data in Health Connect, which the App opens from Settings › Data & privacy › Open Health Connect.

6. Crash reports and usage statistics

To find and fix crashes, and to see which features are worth working on, the App sends a small amount of technical data to a server we run ourselves. Nothing of it goes to Google, to advertisers, or to any other company, and we never sell or share it.

6.1 What is sent

Crash reports Usage statistics
What The error and where in the App’s code it happened (the stack trace), and whether the App crashed or froze Which features were used, for example that a session was completed or the purchase screen was opened; which built-in practice or health test it was, never its results (a practice or test you made yourself is sent only as “custom”); and how long a session lasted, as a range such as “5–15 min”
With it App version and store version (Google Play or AppGallery), operating system name and version App version and store version, operating system name and major version, app language, and a session number that changes after an hour without use
Never Your practice names, notes, health test results, files, or anything you typed The same

Each report carries a random ID that the App creates the first time it starts and that is deleted when you uninstall it. It is not your advertising ID or device ID, and we cannot connect it to your name, account, or device. It lets us count how many installs a crash affects, and it is what lets you ask us to delete your data (section 6.3).

Because of that ID, the data is not anonymous in the strict legal sense but pseudonymous: it cannot tell us who you are, yet it does let us tell one install’s reports from another’s. Data protection law treats pseudonymous data as personal data, and so do we: everything in this section applies to it.

Reports travel over an encrypted (HTTPS) connection. Our server never stores your IP address. It keeps only a scrambled form of it that changes every day, which lets us block abuse of the server and cannot be turned back into the address. Stack traces are cleaned before they are saved: file paths, device names and similar details are removed. The server is in Frankfurt, Germany, rented from OVHcloud, which provides the machine and does not use what is on it; only we can open the data, from our own private network.

6.2 How long we keep it

Data Kept for
Individual usage events, with the random ID 35 days, and in any case no longer than about two months
Individual crash reports, with the random ID 90 days, and in any case no longer than about four months
Daily totals, such as “120 installs completed a session on 3 May” 2 years
Monthly totals, and one cleaned example of each kind of crash As long as the App exists

The totals and crash examples are counts and code locations only: they hold no random ID and cannot be connected to you. Our backups never contain the individual events or crash reports.

6.3 Turning it off and deleting it

  • Turn it off in the App under Settings › Data & privacy › Data sharing, separately for crash reports and for usage statistics. From then on nothing of that kind is sent, and what the App was still holding to send is deleted from your device.
  • Have it deleted. The same screen shows your random ID, with a button to copy it. Send it to us at support@pranabreath.app and we will delete every individual event and crash report sent with it. The totals in section 6.2 stay, because they do not contain the ID.
  • Uninstalling the App deletes the random ID, so nothing sent afterwards can be connected with what was sent before. What was already sent is deleted by the periods in section 6.2.

6.4 Why we may do this

If you are in the European Economic Area, the United Kingdom or Switzerland, the law asks us to name the legal basis: it is our legitimate interest in keeping the App working and in knowing what to improve (Article 6(1)(f) of the GDPR). We keep the data to the minimum above, it cannot tell us who you are, and you can object at any time: turning the switch off is that objection, and it takes effect at once.

7. Payments are handled by the app store

When you buy a subscription or Guru Lifetime, the payment is processed by the store you installed the App from: Google Play Billing, or Huawei In-App Purchases on AppGallery. We do not receive, see, or store your card number, billing name, or billing address. The store’s own privacy policy governs the payment: Google’s, or Huawei’s, which AppGallery shows you.

8. Aggregated data from the app stores

Apart from section 6, the only other information we see comes from the stores’ developer consoles (Google Play Console, Huawei AppGallery Connect). It is general, aggregated data such as:

  • App page views and install/uninstall counts
  • Broad demographic and regional statistics about the install base
  • Crash and performance reports, where the store collects them

This data is aggregated by the store and is not tied to you individually in any way we can access. We do not sell it, rent it, or share it with third parties, and no third party has expressed interest in it, because it has no value for that purpose.

9. Children’s privacy

The App is rated for users aged 3 and above, and is often used by families and children under adult supervision. Because we do not collect personal data from any user, this includes children. We do not knowingly collect personal information from a child of any age. The crash reports and usage statistics of section 6 are the same for every user, and a parent can turn them off on the child’s device. If a purchase or subscription is made through the App, that transaction is handled by the account holder through Google Play, and Google’s own policies on parental controls and Family Library apply.

The Google Drive backup requires a Google account, which Google’s own rules already restrict by age. Where a child uses the App, the backup should be set up and supervised by the parent or guardian who owns that account.

If you believe a child has provided us with personal information through some means outside our control, contact us and we will look into it, though as described above we do not maintain the infrastructure to store such information in the first place.

10. Data retention

The only data we keep on our side is the crash reports and usage statistics, for the periods in section 6.2. You can have them deleted earlier as described in section 6.3.

Data associated with your device, such as saved preferences or session history, stays on your device until you delete it or uninstall the App. If you enabled the Google Drive backup, the backup file stays in your own Google account for as long as you keep it there, under your control and Google’s retention rules. Section 4.6 explains how to remove it. If you saved data to Health Connect, it stays there until you delete it; section 5.4 explains how.

11. International users

Prana Breath is available worldwide. Regardless of where you are located, our approach is the same: what you create stays on your device or in places you choose, and the only data that reaches us is that of section 6. It is stored on our server in Frankfurt, Germany, inside the European Union, and we, in Ukraine, are the only ones who look at it. If you are located in the European Economic Area, the United Kingdom, or another region with its own data protection law, you are welcome to contact us with questions, and we will respond in good faith.

12. Your choices

There is no account with us to close. What you can do:

  • Use the App without ever enabling the Google Drive backup
  • Revoke the App’s Drive permission and delete the backup at any time, as described in section 4.6
  • Use the App without ever saving to Health Connect, or stop and delete what was saved, as described in section 5.4
  • Turn off crash reports, usage statistics, or both, and have what was sent deleted, as described in section 6.3
  • Review the permission and data settings available in your own app store and device settings, if you wish to limit what reaches the stores’ statistics
  • Ask us, with your random ID, what we hold for it, have it deleted, or object to its use; and, if you are in the EEA, the UK or Switzerland, complain to your local data protection authority

13. Changes to this policy

We may update this Privacy Policy from time to time, for example to reflect a new App feature or a legal requirement. The “Last updated” date at the top will change accordingly. If a future update meaningfully changes how we handle information, we will make that clear within the App or on this page. Continued use of the App after an update means you accept the revised policy.

14. Contact us

The person responsible for your data (the data controller) is Oleksandr Albul, Ukraine. For questions about this Privacy Policy, or to use any of the choices in section 12, write to support@pranabreath.app.

↑ Back to top