On this page
1. Who is responsible
The controller under the GDPR is:
- Company
- Prinz Technology Consultancy, svetovanje na področju informacijskih tehnologij d.o.o., trading as Prinz Tech Consulting
- Address
- Dunajska cesta 33, 1000 Ljubljana, Slovenia
- Registration number
- 7326106000 (matična številka)
- VAT ID
- SI86067494
- Privacy contact
- privacy@healthaccessmcp.com
In this policy, "we" and "us" mean this company.
2. What this policy covers
- Health Access, the iOS app ("the app").
- healthaccess-mcp, the MCP server, and healthaccess, the command-line tool ("the MCP server" and "the CLI"). Both run on your own computer.
- This website, healthaccessmcp.com.
- Email you send to us.
It does not cover the services you choose to use alongside them: the storage provider that holds your folder, the AI assistant you connect, and Apple's own services. Each of those has its own privacy policy.
3. Your health data
What the app reads and writes
With your permission, the app reads data from Apple Health on your iPhone. You choose the data types in Apple's permission sheet. The app can only read. It has no permission to write to Apple Health. It writes what it reads as JSON and Markdown files into a folder you pick. Depending on what you allow and what Apple Health holds, the files can contain:
- workouts, with heart rate over time, laps and intervals, and the route with GPS positions if one was recorded;
- daily values, such as activity rings, steps, heart rate and heart rate variability, sleep, breathing, blood pressure, blood glucose, body measurements, nutrition, mobility, mindful minutes, mood and logged symptoms;
- cycle tracking and other reproductive health data, unless you turn off "Include reproductive health data" in the app's Settings;
- medication dose events, ECG recordings (the voltage series only if you turn on "Include ECG voltage") and characteristics such as age, year of birth, biological sex and blood type;
- a one-page summary,
briefing.md, and the status of plans you put on your Watch.
This is health data, a special category of personal data under Article 9 GDPR. That is why the app is built so that it never reaches us.
Where it is processed
- On your iPhone. The app reads Apple Health and writes the files there.
- In the folder you picked. It can be in iCloud Drive, Dropbox, Google Drive, OneDrive, on a network drive, with any other provider in the Files app, or "On My iPhone". If the folder is with a storage provider, that provider stores and syncs the files under your own contract with it. The provider is your choice. We have no access to your account there and no influence on how the provider handles the files. Its terms and privacy policy apply.
- On your computer. The MCP server and the CLI read the folder there.
Your health data is never sent to us. We run no server that could receive it, and there is no account. We cannot see, use, sell or pass on your health data, because we never have it.
What the MCP server and the CLI do
They run only on your computer. The MCP server talks to your AI client through standard input and output and opens no network port. Both read the folder, and they write into it only:
- workout plans, as
plans/<id>.json; - an effort rating and a short note on how a session felt, when you give them;
- one small file per computer and AI client,
mcp/clients/<id>.json, so the app can show that an AI is connected. It holds the AI client's name and version, your computer's name, the server version, when the server was first and last used, the name of the last tool and a call count. It never holds tool arguments or results.
What you share with an AI
When you connect an AI assistant, it reads the data it needs from the folder. What it reads becomes part of your conversation and goes to the provider of that assistant, under that provider's terms. That is your choice and your relationship with that provider. We are not involved and receive nothing. If you want the data to stay on your computer, use a local model.
The setup message the app copies for you contains the folder's name and, for iCloud Drive, its usual path on a Mac. It goes only where you paste it.
Apple's HealthKit rules
Apple's rules for apps that use HealthKit apply to this app, and we follow them. We do not use Health data for advertising, marketing or data mining. We do not share it with third parties. The app uses it only to write the files you asked for, and it never puts Health data into usage statistics.
What the app keeps on your iPhone
The app keeps its settings, a link to your folder, a random install id and a sync log in its own storage on your iPhone. The sync log lists when the app woke and what it wrote. None of this is sent to us. iOS includes it in your device backup if you make one. Deleting the app deletes it.
4. Usage statistics
Usage statistics tell us which features are used and whether they worked. They are off by default in the app and in the MCP server. Nothing is sent unless you turn them on.
In the app
You turn them on in Settings → Trust → Usage statistics and confirm in a dialog that names what is sent and where. From then on the app sends these events to PostHog:
| Event | Properties |
|---|---|
| app_opened | none |
| export_completed | workout_count, duration_ms, trigger (one of manual, observer, bgtask, foreground) |
| export_failed | error_domain, code |
| plan_scheduled | none |
| plan_put_on_watch | method (schedule or preview) |
| setup_message_copied | none |
Each event also carries the time it happened, the app version and build, the iOS version, the device type, the name and version of PostHog's software library and a random install id. It can also carry a random session id that the library creates. The install id is made on your iPhone when the app first starts. It is not your Apple Account, your name or an Apple device identifier, and we cannot link it to you. A filter in the app removes everything else the library would normally add, such as language, time zone, network and screen size. The events never contain a health value, a file name or a folder path.
As with any connection over the internet, PostHog sees the IP address the events come from. The app tells PostHog not to look up a location from it.
Settings → Trust → What left this phone lists every event the app sent in the current session, with the host it went to.
In the MCP server and the CLI
The CLI, healthaccess, sends no usage statistics. It contains no network code.
The MCP server you install with npm, npx -y healthaccess-mcp, is built without network code. It cannot send usage statistics at all.
Every build we publish, on npm and as release archives, is built the same way. Only a server you build yourself from source with the default features contains an optional statistics client. It sends usage statistics only when both of these are true:
- you turned them on, with
telemetry = truein~/.config/healthaccess/config.tomlor with the--telemetryoption; and - a PostHog project key is set as
posthog_api_keyin the same file.
The server ships without a key, so these builds cannot send anything either until you add one. When both are set, it sends two events to the PostHog host named in the config file. Without a host, it uses PostHog's EU host, eu.i.posthog.com.
| Event | Properties |
|---|---|
| mcp_started | version |
| mcp_tool_called | tool, duration_ms, ok, and on failure error_kind, one of io, json, schema, not_found, ambiguous, validation, refused, codec, config |
Each event also carries the time, the server's name and version, the name of the operating system and a random id. The server creates that id the first time it sends and writes it into config.toml as anonymous_id. The events never contain tool arguments, results, workout contents, file names or paths. PostHog sees the IP address of your computer, as with any connection.
The events go to the PostHog project the key belongs to. If you use a key of your own, the statistics go to your project and we receive nothing. We receive them only if the key belongs to our PostHog project.
healthaccess-mcp --check prints whether usage statistics are on. A server built from source with cargo install --path mcp --no-default-features contains no network code, like the npm build.
Legal basis, processor and how to stop
- Purpose. To see which features are used and where things fail, so we can fix and improve the app and the server. Not for advertising and not to build profiles. PostHog is told not to create person profiles.
- Legal basis. Your consent, Article 6(1)(a) GDPR. Storing the random id on your device and sending it rests on the same consent.
- Processor. PostHog, Inc. processes the events for us, on our instructions and under a data processing agreement, in its EU region.
- How to withdraw. In the app, turn off Settings → Trust → Usage statistics. For the MCP server, set
telemetry = falseor remove the--telemetryoption, and start a new session in your AI client. No further events are sent from then on. Withdrawing does not affect what was sent before. - Retention. We have not set a shorter period of our own. The events are kept for as long as PostHog keeps event data by default for our project in its EU region, and no longer than the project exists.
5. In-app purchases
The app offers two optional purchases: one that removes the support card on the home screen for good, and a coffee. Both are sold through Apple's App Store. Apple is the merchant. Apple processes the payment, your Apple Account and any refund, under its own terms and its privacy policy.
We do not receive your name, email address, Apple Account or payment details. The app asks Apple, through Apple's StoreKit on your iPhone, whether the card has been removed, and remembers the answer on the phone. Apple gives us anonymised sales reports: how many of each product were bought, in which countries and for how much. They do not show who bought.
Legal basis: the contract you enter into when you buy, Article 6(1)(b) GDPR. We keep the sales reports and Apple's payment statements for as long as Slovenian accounting and tax law requires, Article 6(1)(c) GDPR.
6. This website
healthaccessmcp.com is a set of static pages. It has no login and no forms. It sets no cookies, has no analytics and does no tracking. It runs no scripts in your browser. Everything it loads, including the typefaces, comes from this site, so your browser connects to no one else while you read it.
Hosting
Cloudflare, Inc. hosts the site and delivers it from its network, as our processor. To deliver each page and to protect the site against attacks and abuse, Cloudflare processes what your browser sends with every request: your IP address, the page requested, the date and time, the browser's user agent and the page you came from. Cloudflare keeps these standard server logs for a short time for security, under its own policies. We do not use them to identify visitors.
Legal basis: our legitimate interest in delivering the site and keeping it secure, Article 6(1)(f) GDPR.
7. When you write to us
When you write to support@healthaccessmcp.com or privacy@healthaccessmcp.com, we keep your email address, your name if you give it, your message, any attachments and our replies. We use them only to answer you and to solve the problem you describe. Our email provider stores the messages for us.
Legal basis: our legitimate interest in answering questions and supporting the people who use our software, Article 6(1)(f) GDPR. For requests about your rights, also our legal obligation to answer them, Article 6(1)(c) GDPR.
We delete the conversation when the matter is closed, unless the law requires us to keep it longer.
Please do not send us health data files. We do not need them to help you. The support page says what to send instead.
8. What we do not do
- No accounts. There is nothing to sign up for.
- No advertising, and no advertising identifier.
- No selling or renting of data, to anyone.
- No tracking across apps or websites. The app's privacy manifest declares this to Apple.
- No crash reports and no screen recordings. Both are switched off in the app.
- No profiling and no automated decisions that have legal or similarly significant effects on you.
9. Who receives data
- PostHog, Inc., as our processor: usage statistics, only if you turn them on.
- Cloudflare, Inc., as our processor: the server logs of this website.
- Apple, as the merchant: everything about a purchase, under Apple's own privacy policy.
- Our email provider, as our processor: the email you send us.
- Authorities, courts and our professional advisers, such as accountants, only where the law requires it or to establish or defend legal claims.
Your storage provider and your AI assistant receive only what you give them, under your own contract with them. We do not pass anything to them.
10. Transfers outside the EU
- PostHog stores the usage statistics in its EU region. PostHog, Inc. is based in the United States. Its data processing agreement covers any access from outside the EU, using safeguards such as the EU Standard Contractual Clauses.
- Cloudflare runs a global network and may process the server logs outside the EU. Its data processing agreement uses safeguards such as the EU Standard Contractual Clauses.
- Apple transfers purchase data as described in its own privacy policy.
11. How long data is kept
| Data | Kept |
|---|---|
| Your health data | Never held by us. It stays in your folder until you delete it. The app never deletes files there. |
| Usage statistics | PostHog's default period for event data in our project. See section 4. |
| Website server logs | A short time, by Cloudflare, for security. |
| Until the matter is closed, unless the law requires longer. | |
| Sales reports and payment statements | As long as Slovenian accounting and tax law requires. |
12. Children
The app, the MCP server and this website are not directed at children under 16. We do not knowingly process personal data of children under 16. If you think a child has sent us personal data, write to us and we will delete it.
13. Your rights
Under the GDPR you have the right to:
- access your personal data (Article 15);
- have it corrected (Article 16);
- have it erased (Article 17);
- restrict its processing (Article 18);
- receive it in a portable format (Article 20);
- object to processing based on our legitimate interest (Article 21);
- withdraw your consent at any time, without affecting what happened before (Article 7(3)).
Most of them you exercise yourself
Your health data sits in your own folder, so you do not need us for it.
- Access, correct, copy or erase your health data by opening, editing, copying or deleting the files in your folder. They are plain JSON and Markdown, which is already a portable format.
- Stop the app reading Apple Health in Health → Sharing → Apps → Health Access.
- Stop usage statistics as described in section 4.
- Erase what the app keeps on your iPhone by deleting the app.
- Erase what the MCP server keeps on your computer by removing
telemetry,posthog_api_keyandanonymous_idfrom~/.config/healthaccess/config.toml, or the whole file.
For the data we hold
For usage statistics, email and anything else we hold, write to privacy@healthaccessmcp.com. It is free. We answer within one month. We may ask for information to confirm that a request is yours.
Usage statistics sit under a random id, so we can only find yours if you tell us the id. For the MCP server, it is the anonymous_id line in config.toml. Send it to us and we will delete the events under it. The app does not show its install id, so we cannot tell which events came from your iPhone (Article 11 GDPR). Turning off usage statistics stops new events. Deleting and reinstalling the app creates a new id that cannot be linked to the old one.
14. Complaints
You have the right to lodge a complaint with a supervisory authority. Ours is the Slovenian Information Commissioner:
- Authority
- Informacijski pooblaščenec
- Address
- Dunajska cesta 22, 1000 Ljubljana, Slovenia
- Website
- https://www.ip-rs.si
You can also complain to the authority in the EU country where you live or work, or where you think the infringement took place. You are welcome to write to us first.
15. Changes to this policy
When we change this policy, we publish the new version on this page with a new effective date. If a change would need your consent, we ask for it before the change applies to you. Earlier versions are available on request.
16. Contact
Privacy questions and requests: privacy@healthaccessmcp.com. By post: Prinz Technology Consultancy d.o.o., Dunajska cesta 33, 1000 Ljubljana, Slovenia. Help with the app or the server: Support.
Effective 26 October 2026.