Privacy policy

Last updated 7 November 2026

Health to Mac is made by Mostly Media EOOD, a company registered in Bulgaria (EU). Mostly Media EOOD is the data controller for the little this site and the purchase process handle: Cloudflare page views and Polar checkout. Polar is the merchant of record for payments. The apps themselves send us no health data — there are no accounts, no servers that receive your data and no analytics or ads inside them.

Who we are and how to reach us

The provider and data controller is:

Mostly Media EOOD (Mostly Media Ltd.), Saltanat 81, Primorski, 9000 Varna, Bulgaria. UIC 207632668.

Contact: support@healthtomac.com. The same provider details appear in the footer of every page.

What the iPhone app does with your data

  • It reads the Apple Health categories you allow. It can't write to Health, and you can change what it reads at any time in Settings → Health → Data Access & Devices → Health to Mac.
  • It sends that data to the Mac you pair it with, over your own network (your Wi-Fi, or your own Tailscale network if you use one), encrypted end to end with a key your Mac made for this iPhone, and nowhere else unless you set up an export:
    • Save a File writes a JSON or CSV file that you save with the Files picker, wherever you choose.
    • REST API sends new data to the URL you enter, with the token or header you enter. It must be an https:// address unless it's on your own network. We never see any of it.
  • The Highlights tab adds up your Health data on the iPhone each time it's shown, and compares a few numbers with published studies. To pick the right age group it can read your date of birth and sex from Health, but only if you allow that separately; or you can type a birth year and sex in yourself (kept in the app's settings on this iPhone). None of this is saved with your Health data or sent anywhere.
  • On the iPhone it stores only what it needs to sync: your Mac's addresses, the key your Mac made for this iPhone (in the iOS Keychain), how far it has synced, your REST export's URL and token (the token in the Keychain), and a short activity log. Unpairing deletes the addresses, the key and the sync position. A saved file is deleted from the app's temporary folder as soon as you've saved it or cancelled.

The connection to your Mac

The iPhone app sends that data to your Mac only after you pair the two, by scanning a pairing code the Mac shows you. It forgets the Mac's addresses and the key as soon as you unpair. There is no account and no server of ours in the middle; the connection is on your own network, encrypted end to end with a key your Mac made for that iPhone.

What the Mac app does with your data

  • It stores your Health data in a database file on your Mac. That file stays on your Mac; nothing is uploaded to us.
  • It sends data elsewhere only to destinations you set up yourself:
    • Strava. If you connect your own Strava API application, Health to Mac downloads your activities from Strava using your credentials.
    • Exports. If you set up automatic exports, Health to Mac writes files to folders you pick, or sends data to the REST endpoint, MQTT broker or Home Assistant instance you enter. Email exports go through a mail account you configure yourself.
    • AI assistants. If you connect an assistant through Health to Mac's MCP server, that assistant can read your data when you ask it something. The assistant's own privacy policy covers what happens next.
  • Update checks. The Mac app checks our website for new versions. Like any web request, this reveals your IP address and the app version to the web host. No Health data or other personal information is sent, and no system profile is collected.

This website

Cloudflare serves these pages and counts page views with a cookieless counter: it does not set tracking cookies, and its privacy policy covers the request data (such as IP address and user agent) it processes to deliver the page. Google Search Console only shows us which search phrases lead here and how the site appears in Google's index; none of that is tied to a visitor. There are no advertising or cross-site tracking cookies on this site.

Buying and support

Polar (polar.sh) is the merchant of record and processes your payment. There is no licence key: after checkout Polar emails you the download link. Polar shares with us the buyer's name, email address and country, plus the order details; we use those only to provide the purchase, handle refunds and keep the tax records the law requires. We keep buyer records for as long as Bulgarian tax and accounting rules require, and otherwise only for as long as needed to answer your support request or a refund claim.

Email you send to support@healthtomac.com is routed through Cloudflare Email Routing and stored by the mail provider we use; we keep it until your request is resolved, then delete it. Please don't send health data or database files with a support request.

You can ask us for a copy of the personal data we hold about you, ask us to correct or delete it, or withdraw a consent, by writing to support@healthtomac.com. You also have the right to complain to the Bulgarian supervisory authority, the Commission for Personal Data Protection (CPDP).

Health data never reaches the company: the apps keep it on your devices and send it only where you choose.

Children

Health to Mac isn't directed at children and doesn't knowingly collect anything from anyone.

Changes

If this policy changes, the new version will be posted here with a new date. Health to Mac is open source, so you can always check what the apps actually do.

Contact

Questions: support@healthtomac.com, or see Support.