breatheby Eden

privacy

Washington Consumer Health Data Privacy Policy

Effective 4 November 2026

This page describes the consumer health data handled for breathe under Washington’s My Health My Data Act. It covers Washington residents and people whose consumer health data is collected in Washington.

Arian Rousta, an individual developer based in the United States, is responsible for this processing. In this policy, “the developer” means Arian Rousta. For questions or requests, email hello@poweredbyeden.com.

Consumer health data includes information linked, or reasonably linkable, to you that identifies your physical or mental health. It can include conclusions drawn from your practice, messages or use of a health-related feature.

What is collected and why

  • Health readings: heart rate, resting heart rate, heart rate variability measured as SDNN, respiratory rate, blood oxygen, sleep, active energy, steps and workouts. With your permission, these support body readings, calm baselines, suggestions and explanations on your device.
  • Practice records: your chosen breaths, custom breaths, session times and durations, breath cycles, Life Force, breath holds, records, milestones, streaks and other practice counts. These run your practice, show its history and progress, and shape suggestions.
  • Session heart-rate records: the average, lowest and highest readings and a trace of up to 48 points when heart rate is available. These show what happened during your session.
  • Health-derived information: your calm baseline, recovery label, whether a personal baseline supports that label, usual workout hour and related timing records. These help the app choose and explain a suggested breath.
  • Messages and feedback: health information you put in Ask Eden, Compass, support messages, privacy requests, attachments or TestFlight feedback, together with replies that can contain health information. These provide the response, guidance or support you request and fulfil privacy requests.
  • Identifiers associated with health information: your optional profile name and photo on your device, and contact or tester details supplied with health-related support or feedback. These identify the local profile or let the developer answer your request.
  • Technical records connected to health-related use: your IP address, approximate location, network operator, user agent, app build, membership status and cloud-request records. These deliver requests, apply rate limits, investigate faults and manage the relay’s running costs.

Cloud-request records include the route, screen or feature, model, token counts, response time and outcome. Technical records fall within this policy when they identify or can reasonably be linked to your health-related activity.

The developer does not use health data for advertising, marketing or model training. Health data is not sold or given to data brokers.

Where the information comes from

  • You, through the details you enter, messages you send and practices you choose.
  • Apple Health and your Apple Watch, when you allow the relevant access.
  • Records and calculations created from your practice and permitted Health readings.
  • Your device and network connection when you use cloud features.
  • Apple’s testing and diagnostic services, when you provide TestFlight feedback or enable crash-report sharing.

What stays on your device

Raw Health readings, detailed practice history, your profile and custom breath names are stored on your device and can be included in your own device backups. Compass text is used on your phone and is not added to cloud requests. Some practice counts and Health-derived labels go to cloud services only through the choices described below.

The app’s widgets and Live Activities use local information. Your Watch sends readings and completed sessions to your paired iPhone through Apple’s Watch Connectivity.

In 1.0.6, the app does not automatically add Health numbers, dates, samples or workout-derived context to cloud requests. The body-page question also excludes Health numbers and dates. If you type readings or workout details into a cloud message, those words are sent.

What goes to other companies

Cloud writing: Cloudflare and Anthropic

Cloudflare operates the relay that carries a permitted request. Anthropic supplies Claude, which writes the requested line or reply.

For a suggested-breath line, the request can contain:

  • The breath’s name from the app’s catalogue and the part of day.
  • A fixed occasion phrase about the day, your chosen practice, how your body is reading, or the hour.
  • Whole weeks since your first session, capped at 260.
  • Your completed-session count, streak and days since your last session.
  • Whether you have finished that breath before and whether it is your chosen daily practice.
  • A recovery label while body signals are on: charged, steady, strained or depleted.
  • Whether a personal baseline supports that label. This can be yes only while body signals are on.

For a session-ending line, the request can contain the breath’s catalogue name, part of day, session minutes from 0 to 240, streak and recovery label. A custom breath’s name is omitted. The recovery label is included only while body signals are on.

For Ask Eden, a cloud turn sends the first 500 characters of your current message. It can also send the two most recent cloud-answered questions and their replies, each limited to 500 characters. It includes the recovery label only while body signals are on.

App-written readings, local replies and the questions answered by those local replies are excluded from cloud history. Your messages can still contain health information or identifying details you type yourself.

Cloudflare also receives request headers and your IP address. Its event records include approximate location, network operator, user agent and build label, and can include your IP address. The developer’s separate usage entries contain no message text or IP address.

The relay does not forward your IP address to Anthropic. The words you type can still identify you.

Support email: Google

Google hosts the support mailbox. If you send health information in an email or attachment, Google and the developer receive it to answer and resolve your request.

Support does not usually need your Health records. Avoid sending readings, medical history or screenshots containing health information. If health information is needed, the developer explains what is needed and asks for your explicit consent before asking you to send it.

Health details that are not needed to answer your request are deleted.

Device, Health and testing services: Apple

Apple provides the Health app, Watch Connectivity, Siri, device backups and testing or diagnostic services you choose to use. These services handle health information when your records, voice request, feedback or diagnostic information contain it.

With your permission, breathe writes completed iPhone sessions as Mindful Minutes in Apple Health. Watch sessions are saved as Mind and Body workouts. Apple handles your iCloud backups if you use them.

Apple’s on-device writing in breathe runs on your phone. That path does not send the readings to Apple’s cloud.

Affiliates and other recipients

Eden is the brand under which Arian Rousta publishes breathe. The developer does not share breathe’s consumer health data with affiliates.

The recipients above provide cloud hosting and writing, email, device services, backups, testing and diagnostics. There is no sale of consumer health data and no disclosure to advertising networks or data brokers.

Earlier versions

The source reviewed for 1.0.5 allowed app-written Health readings and local replies containing them into cloud Ask Eden requests. Unanswered cloud choices counted as yes for breathe+ members, including trials. Whether any person’s readings were actually sent is not established.

The relay blocked requests to Anthropic on 28 October 2026. Builds older than 1.0.6 remain blocked. Requests from those builds can still reach Cloudflare and leave event records.

Your choices

Before either cloud permission question, the app asks whether you are 18 or over. A no keeps Ask Eden and written lines on your phone. The rest of breathe remains available.

Cloud writing also requires breathe+ and an explicit yes to the relevant permission question. Ask Eden has its own question. A no to Written lines also keeps Ask Eden on your phone. An unanswered cloud question does not permit that feature to send.

People updating from 1.0.5 or earlier see a Privacy update notice before any cloud feature can send. Acknowledging that notice is not consent.

To stop new cloud requests, open You ▸ Written lines and You ▸ Ask Eden and turn them off. This stops future sending; it does not delete a request already sent.

To stop Health reading, open iOS Settings ▸ Privacy & Security ▸ Health ▸ breathe by Eden and turn off the reading permissions. You ▸ Sync to Apple Health stops the iPhone writing Mindful Minutes. The Watch follows its own Health permissions.

Your Washington rights

You can:

  • Ask whether consumer health data about you is being collected, shared or sold, and access that data.
  • Ask for a list of all third parties and affiliates that received your consumer health data, with an active email address or another online way to contact them.
  • Withdraw consent to the collection or sharing of your consumer health data.
  • Ask for your consumer health data to be deleted.

Make a request

Email hello@poweredbyeden.com and describe your request. You do not need to create an account. The developer asks only for information reasonably needed to verify your identity and find the relevant records.

Most records are on your devices, which the developer cannot access remotely. The relay has no account-based conversation archive. If a record cannot be located, the developer explains what further details could help.

Requests are handled without undue delay and within 45 days of receipt. Verification does not restart that deadline. If the complexity or number of requests makes an extension necessary, the period can be extended once by up to 45 days. You receive the reason within the original 45 days.

Ordinary requests are free. A fee or refusal for a manifestly unfounded, excessive or repetitive request is used only where the law allows it and is explained to you.

Withdrawal and deletion

The in-app cloud controls stop new requests immediately. For withdrawal by email, processing that depends on your consent stops as soon as practicable and within 15 days. Withdrawal does not undo a request already processed. Deletion is a separate right.

You can delete an Ask Eden conversation in chat history. You ▸ Reset all data ▸ Erase everything removes the local Health caches, practice records and conversations described above. It does not delete your Apple Health records, existing backups or copies already held by a provider.

A valid deletion request covers the developer’s records, including relevant archived or backup copies. The developer notifies every provider or other recipient that received the data of the deletion request. Those recipients must also delete the data as the law requires.

If deletion from an archive or backup is delayed under Washington’s permitted restoration process, the delay cannot exceed six months after the request is authenticated. This does not create a general six-month retention period.

You can remove records already in Apple Health through the Health app and manage your own device backups through Apple’s controls. An ordinary retention schedule does not override a valid deletion right.

Appeal or complain

To appeal a refusal, reply to the decision email or send an email to hello@poweredbyeden.com saying you want to appeal. You receive a written decision and its reasons within 45 days.

If an appeal is denied, the response includes a way to complain to the Washington State Attorney General. You can also use the Attorney General’s complaint page.

Exercising a right does not result in unlawful discrimination. Withdrawing information needed for an optional feature stops that feature from using it.

Changes to health-data uses

Before collecting, using or sharing an additional category of consumer health data, the developer discloses that category and obtains your affirmative consent. The same applies before collecting, using or sharing consumer health data for an additional purpose not described here.

Publishing a policy update alone is not that consent.

Read the privacy policy

Last updated 4 November 2026

breathe by Eden · hello@poweredbyeden.com