BreathCare

Legal

Privacy Policy

Last updated 17 November 2026

BreathCare is an app for breathing, meditation, affirmations and quotes. It has no accounts. This page says exactly what happens to your data — what stays on your iPhone, what leaves it, and what you can ask us to do.

The short version

1. Who is responsible for your data

The controller of the personal data described here is:

Grzegorz Mróz Ventures
Krajewskiego 1/29
01-520 Warszawa
Poland
support@breathcare.app

Write to that address with any question about this policy or about your data. We have not appointed a Data Protection Officer; the same address reaches the person who decides how BreathCare handles data.

This policy covers the BreathCare app for iPhone, its lock-screen widget and Live Activity, and this website. It does not cover Apple, whose handling of your App Store purchase is governed by Apple's own privacy policy.

2. What stays on your iPhone

Everything the app knows about you and your practice is written to its own storage on your iPhone, inside the app's container, and it stays there. The app does not upload it. We have no copy and no way to get one.

This is what the app stores on the device:

Why: this is the app. Without it there is no greeting by name, no recently played list, no saved quote, no pattern of your own and no reminder.

Lawful basis: Article 6(1)(b) GDPR — processing necessary to provide the service you asked for. In practice we are not a party to it: the data never reaches us.

How long: until you delete it in the app, or until you delete the app. Deleting BreathCare removes it from your iPhone.

A consequence worth knowing before you rely on it: there is no backup of our own, no sync and no export. If you delete the app, or lose the phone without an iPhone backup, what you saved is gone and we cannot restore it.

3. Analytics

This, advertising measurement (section 4) and purchase events (section 5) are the parts of BreathCare in which data leaves your phone, so they get the longest sections.

Who processes it, and where

We use PostHog as a processor, on its EU Cloud (https://eu.i.posthog.com). The events are stored in the European Union.

The identifier, honestly

The analytics library generates a random identifier for your installation of the app and stores it in the app's container on your device. It is not your name, your email address, your Apple Account, your phone number, your advertising identifier or your device's serial number — it is a random string created on your phone the first time you open the app.

It is still personal data under the GDPR, because it lets events be grouped together as coming from one installation. That is called a pseudonymous identifier, and calling it “completely anonymous” would be wrong. So we do not call it that. It disappears when you delete the app; a reinstall generates a new one, unconnected to the old one.

What is sent

A fixed list of events, written into the app by hand. Nothing else is collected:

Once the app knows where this installation came from, every event also carries it: “organic”, “Apple Search Ads” or “Meta”, and for Apple Search Ads the campaign, ad group and keyword numbers and the country that Apple reports (see section 4). For an installation from Apple Search Ads this is usually known within seconds of the first launch; otherwise it is known after setup, and events sent before then carry no such label. That label describes an ad, not you.

What is never sent

What is switched off

Why we do it

To see which parts of the app are used, where people give up, and whether a change made things better or worse. Without it we would be guessing.

Lawful basis: our legitimate interests — Article 6(1)(f) GDPR — in understanding and improving the app. We have weighed that against your privacy: the data is a short fixed list with none of your own words in it, no profile is built, the analytics data is not sold and not passed on for advertising, and the identifier cannot be linked to you by us.

How to object — read this, because there is no switch yet

The app does not currently have an in-app control to turn analytics off. We are telling you that plainly rather than describing a toggle that is not there.

You have two ways to stop it:

4. Advertising measurement

We advertise BreathCare, and we want to know which ads actually bring people to it and which of them lead to a subscription. Three things serve that, and none of them shows you an ad.

Meta (Facebook)

The app contains Meta's software development kit (the “Facebook SDK”, core part only — there is no Facebook login and no sharing). It sends to Meta Platforms Ireland Limited:

Never sent to Meta: your name, your answers, what you played, your patterns, your reminders or their names, your saved quotes, any health data, your email address, and anything you type.

Meta uses this data under its own privacy policy, facebook.com/privacy/policy, which also describes what Meta does with it for its own purposes.

Apple's ad-attribution reports (SKAdNetwork)

When an installation follows one of our ads, Apple itself sends the advertising network a report that an installation happened. Apple designs these reports so that they do not identify you or your device. Apple sends a copy to our server (section 5), which only records that it arrived.

Apple Search Ads

When the app is first opened, it asks iOS for an attribution token and sends it to Apple's attribution service. Apple answers whether the installation came from an Apple Search Ads ad and, if it did, the campaign, ad group and keyword numbers and the country. No advertising identifier is involved and no permission prompt is needed. The answer is stored on your iPhone and added to the analytics events described in section 3.

Why we do it

Lawful basis: our legitimate interests — Article 6(1)(f) GDPR — in knowing whether our advertising works. Reading your advertising identifier is based on your consent, Article 6(1)(a), which you give or refuse in the iPhone's prompt.

How to refuse or stop it

5. Purchase events and our server

The app itself never contacts a server of ours. But we do run one small server, and Apple talks to it. It exists for one purpose: measuring whether our advertising leads to subscriptions.

The installation identifier

The first time it is needed, the app creates a second random identifier for your installation and stores it on your iPhone. It is separate from the analytics identifier in section 3 and is never attached to analytics events. Only if you have allowed tracking when your iPhone asked does the app hand this identifier to the App Store together with a trial or subscription purchase, so that Apple's later messages about that subscription carry it. If you have not, the purchase carries no identifier of ours. Like the analytics identifier, it is not your name, your Apple Account or your advertising identifier, and it is personal data all the same.

What Apple sends to our server

When something happens to your subscription — a trial or a paid period starts, it renews, a renewal fails, it expires or it is refunded — Apple sends our server a signed notification. It contains the kind of event, which plan it concerns, Apple's numbers for the transaction, dates, the price and currency, the App Store country, and the installation identifier above if the purchase carried it. It does not contain your name, your email address, your Apple Account or any payment details. Apple does not give us those.

What our server does with it

This report to Meta depends on your answer to the iPhone's “Allow tracking” prompt at the moment you buy. Apple's rules count it as tracking, and the app's privacy label in the App Store declares it as such. One limit, said plainly: if you allowed tracking when you bought and switch it off later in iPhone Settings, Apple keeps attaching the identifier to that subscription's renewals and our server cannot see the change, so those renewals are still reported. A purchase made after you switched tracking off carries no identifier.

The server is hosted by Railway, a cloud hosting provider, which stores the server's log on our behalf as a processor.

Why we do it

Lawful basis: your consent — Article 6(1)(a) GDPR — which you give by tapping “Allow” in the iPhone's tracking prompt.

How long: our server keeps nothing but its log, and the log is kept only for as long as the hosting provider retains log lines. What Meta receives is kept by Meta under its own policy.

How to object

Choose “Ask App Not to Track” when the iPhone asks, or switch BreathCare off later in iPhone Settings → Privacy & Security → Tracking: purchases made after that carry no identifier and are not reported. There is no in-app switch. You can also withdraw your consent or object in writing by emailing support@breathcare.app. Because we cannot tell which installation identifier is yours, please read section 12 on what we can and cannot do; we will answer honestly either way.

6. When you email us

“Contact us” and “Report a bug” do not send anything by themselves. They open a message in Apple's Mail on your phone, already addressed to support@breathcare.app. You decide whether to send it. Your mail provider carries it, and we receive whatever your mail identity shows — normally your email address and the name on the account.

A bug report can carry three optional things. Each is your choice, and you can see all of them in the message before you send it:

The diagnostics block contains:

It contains no advertising identifier, no identifier for vendor and no location, and nothing about your practice beyond that one total — no times, dates, lengths, titles or answers.

Lawful basis: Article 6(1)(b) GDPR where you are asking for support with a subscription, and Article 6(1)(f) — our legitimate interest in answering messages and fixing the app — otherwise.

How long: we keep support correspondence for 24 months after the matter is closed, then delete it. If a message matters for a legal claim or a tax record, we keep it for as long as the law requires.

7. Subscriptions and the App Store

BreathCare Pro — the yearly or monthly subscription, and the 7-day free trial that comes with the yearly plan for new subscribers — is sold through the App Store. Apple takes the payment and manages renewal and cancellation.

We never see your card number, your billing address or the email address on your Apple Account. Apple does not give them to us.

Cancelling happens in the App Store, in your Apple subscription settings — not by writing to us.

To know whether to open, the app asks the App Store on your device whether this Apple Account has an active subscription. That check is between your iPhone and Apple. What we learn about a subscription comes only through the notifications described in section 5.

Apple is its own controller for the purchase, the payment and the subscription record. What Apple does with that data is described in Apple's privacy policy.

Lawful basis for the part that happens in the app: Article 6(1)(b) GDPR — giving you the subscription you paid for.

8. Reminders, notifications and the lock-screen quote

Reminders are scheduled entirely on your device, through iOS's own notification system. Nothing is sent from a server, and there is no push token — we have no technical way to send you a notification.

The quote on your lock screen works the same way. The Live Activity and the lock-screen widget draw quotes from the collection that ships inside the app; they are started and updated on your iPhone and receive nothing from us.

A reminder's type, name, time and days live on your phone with the rest of your data, and are covered by section 2.

Lawful basis: Article 6(1)(b) GDPR. iOS also asks for your permission before it will show notifications at all, and you can withdraw that at any time in iPhone Settings.

9. What BreathCare does not do

Stated as a list so you do not have to infer it from silence:

10. How long data is kept

11. Where your data is processed

Most of it is not processed anywhere but your own phone.

Analytics events go to PostHog's EU Cloud and are stored in the European Union. We have not authorised any transfer of PostHog analytics data outside the European Economic Area. We are established in Poland, and support email reaches us in Poland.

Advertising-measurement data and purchase events go to Meta Platforms Ireland Limited, and Meta may transfer them to Meta Platforms, Inc. in the United States. Meta Platforms, Inc. is certified under the EU–U.S. Data Privacy Framework, which the European Commission recognises as adequate protection.

Our server runs at Railway, a hosting provider based in the United States, so the subscription notifications it receives and its log may be processed there.

Apple processes your purchase under its own arrangements, which may involve transfers outside the EEA under the safeguards Apple describes in its privacy policy. That part is Apple's decision, not ours.

12. Your rights

Under the GDPR you have the right to:

To exercise any of them, write to support@breathcare.app. We answer within one month, and tell you if we need longer, as Article 12(3) allows.

What having no account means in practice

Because there is no sign-up, we hold nothing that connects you to an identity. Honestly stated:

13. Complaining to a supervisory authority

If you think we have handled your data unlawfully, you can lodge a complaint with the Polish supervisory authority:

Prezes Urzędu Ochrony Danych Osobowych (President of the Personal Data Protection Office)
ul. Stawki 2
00-193 Warszawa
Poland
uodo.gov.pl

If you live in another EEA country, you can complain to your own national data protection authority instead. You can also go to court. Please consider telling us first — it is usually faster.

14. Children

BreathCare is not directed at children under 16, and we do not knowingly process their personal data. If you are under 16, please use the app only with a parent's or guardian's agreement.

If you are a parent and want the app's data gone from a child's phone, deleting the app does it. If you want to raise anything else, write to support@breathcare.app.

15. Security

Data the app stores sits inside the app's own container, protected by iOS's sandbox and by the device encryption that your passcode unlocks. Keeping a passcode on your iPhone is the single most effective thing you can do for this data.

Analytics events, the data Meta's software sends and Apple's notifications to our server travel over encrypted HTTPS connections. Our server accepts a subscription notification only after checking Apple's signature on it. PostHog and our hosting provider handle data as our processors, only on our instructions, under Article 28 GDPR.

No system is perfect, and we will not claim otherwise. What we can say is that the amount of your data we hold is deliberately as small as we could make it.

16. Changes to this policy

When this policy changes, the date at the top of the page changes with it, and this page always carries the current version.

Because you have no account, we have no way to email you about a change — we do not know your address. If we make a change that materially affects your rights, we will say so on this page, and we will describe it rather than leave you to compare two versions.

This version, of 17 November 2026, describes BreathCare 2: it adds the meditation, affirmation and quote features, the data they keep on your phone, the events they add to analytics, the purchase events our server receives from Apple and passes to Meta, and the crash reports kept on the device.

17. Contact

Grzegorz Mróz Ventures
Krajewskiego 1/29
01-520 Warszawa
Poland
support@breathcare.app

BreathCare is a wellness app, not a medical device. It does not diagnose, treat or prevent anything. A wellness practice, not medical care — stop if you feel unwell.