Health for Agents

Privacy Policy

Effective date: September 27, 2026 (version 1.1)

Health for Agents is designed to keep users in control of their Apple Health data. The app reads HealthKit data only after the user grants permission in iOS. The app does not include advertising, third-party analytics, tracking SDKs, or a developer-operated server backend for collecting health data.

Data the app can access

With the user's explicit permission, Health for Agents can read health and fitness data from Apple HealthKit. This may include sensitive information such as activity, workouts, sleep, heart rate, body measurements (including body fat), nutrition, reproductive health, and mental-health records. Depending on permissions, device support and iOS version, exports may also contain ECG measurements, heartbeat series, precise GPS locations from workout routes, hearing tests, clinical records (including diagnoses, allergies, laboratory results, medications, immunizations, insurance details and medical notes), and individually selected vision prescriptions. The app reads existing workout routes from HealthKit; it does not record live location.

Current profile information may include date of birth, biological sex, blood type, skin type, wheelchair use and activity move mode. Daily activity summaries may also be exported. Access is optional and controlled through Health permissions. The app cannot distinguish a denied read permission from an absence of records. Medication tracking and dose events, CDA documents and attachments are not supported by this version. An export is not a complete Apple Health backup.

How Health data is used

Health data is used only to provide the app's core features: showing a limited debug preview, creating local JSON or ZIP exports, sharing an export through the iOS share sheet, and sending selected recent data to an AI agent API endpoint configured by the user.

Legal basis and consent (GDPR)

Where the GDPR applies and consent is the applicable basis for the health-data processing described here, we rely on consent under Article 6(1)(a) and explicit consent under Article 9(2)(a). HealthKit permissions control which records the app may read. Separately, the app asks for confirmation before an in-app agent transfer or approval of future Shortcut transfers. Granting HealthKit access alone does not authorize sending data to an endpoint.

You can withdraw permission for future access through Apple Health or iOS Settings and disable your Shortcut automations to stop scheduled sends. Withdrawal does not affect the lawfulness of processing before withdrawal and does not recall files or data already sent to another recipient. An endpoint operator is responsible for its own processing and applicable legal basis.

What can be sent to an agent endpoint

For Send to Agent, sample records are selected from 24 Hours, 7 Days, or 30 Days. The JSON payload can include HealthKit sample identifiers, sample type identifiers, start and end dates, numeric or category values, units, text values, metadata when present, export metadata such as schemaVersion, generatedAt, scope, and source, and a short instruction asking the receiving agent to analyze trends and avoid medical diagnosis.

Structured details can include the sensitive data listed above, source app and device information, and clinical FHIR record contents. Coverage information lists queried, empty, excluded or failed types. Current profile characteristics are included as a separate context snapshot when readable; they are not limited to measurements recorded within the chosen time range. Activity summaries have calendar-day granularity and may include a full day that overlaps a selected range. File exports additionally support All Time. Debug previews are limited to 24 hours and 500 samples.

If the user saved an API bearer token in the app, the token is sent only as an Authorization header to the configured endpoint. The bearer token is not included inside the JSON HealthKit export.

Local storage and exports

Export files are created locally on the user's device. Old exports are deleted automatically when the app starts, and users can manually delete existing exports from inside the app. When a user shares or saves an export through iOS, the user chooses the destination and is responsible for what happens to that exported file afterward.

API uploads use a temporary JSON file protected by iOS file protection. The app attempts to delete it when the upload operation ends, including on handled errors. This cleanup may not execute if iOS terminates the app. Copies saved or shared outside the app are not deleted by its export cleanup.

Sending data to an AI agent

The app can send recent HealthKit data to an HTTPS API endpoint entered by the user. Health for Agents does not include, operate, select, or control a third-party AI service or developer-operated backend. The recipient is the exact endpoint URL entered by the user. Before an in-app Send to Agent transfer, the app shows a review screen that identifies the recipient URL, explains the categories of HealthKit data being sent, and asks the user to confirm the transfer.

If the user-configured endpoint forwards data to an AI provider, stores the data, logs the data, or shares the data with another service, that behavior is controlled by the endpoint owner, not by Health for Agents. Users should only send health data to endpoints and AI services they control or trust, and whose privacy and security practices provide the same or equal protection for sensitive health data. The app cannot verify arbitrary user-supplied endpoints or guarantee their practices. Do not approve a destination unless you have checked its privacy policy, retention, deletion and downstream sharing practices. A destination may process data in another country, including outside the EEA; its operator is responsible for applicable transfer safeguards. No endpoint or third-party AI provider is selected by the developer.

The app stores the optional API bearer token locally in the iOS Keychain. The token is used only to authenticate requests to the user-configured AI agent API endpoint.

Shortcuts automations

Users may configure Apple Shortcuts to trigger a health update. Before saving Shortcut automation settings in the app, Health for Agents shows a one-time review screen explaining that future Shortcuts can send HealthKit samples from the saved range to the saved endpoint, including from user-created automations. Shortcut runs do not show an in-app confirmation every time. When a Shortcut runs, it uses the saved endpoint, selected time range, and bearer token from the app settings. If the endpoint or range changes, the user must save and approve the automation settings again. Whether an automation runs depends on iOS Shortcuts behavior and the user's device settings.

Version 1.1 expands the data categories. Users must review Health permissions and approve their saved Shortcut settings again before automated sends using the expanded scope. Subsequent runs do not require a new in-app confirmation for each transfer to the approved endpoint and range.

No tracking or advertising

Health for Agents does not use advertising identifiers, does not track users across apps or websites, and does not sell user data. The app does not include third-party analytics SDKs.

Data retention and deletion

The app stores local settings, including HealthKit authorization state, the configured API endpoint, selected Shortcut range and saved transfer approval. The optional bearer token is stored in Keychain and can be removed in Settings. A local sync history contains timestamps and status messages, such as counts and error information, and can be cleared in Sync History. Local settings and history remain until cleared or removed through the relevant app or system controls. Keychain entries may survive uninstalling the app; remove the token using the app's control when you no longer need it. Deleting exports does not delete the original records in Apple Health or copies held by recipients.

Your rights (GDPR)

Where applicable, you may request access, correction, erasure, restriction or portability of your personal data, object to processing, and withdraw consent. These rights depend on the processing and applicable legal conditions. You may also complain to a data protection supervisory authority.

The developer does not receive or hold your HealthKit exports on a developer-operated server. Manage original records and permissions in Apple Health, delete local exports and sync history in the app, and disable automations you no longer want. For data already shared, contact the recipient to exercise your rights over its copies. Contact us below for privacy requests concerning data we actually receive, such as support correspondence. You do not need to send health records with a request.

User responsibility after export or transfer

Health data is sensitive. After a user exports, shares, saves, or sends data outside the app, the user is responsible for the chosen destination and recipient. Users should avoid sending health data to services or people they do not fully trust.

Website hosting

This privacy policy page may be hosted by GitHub Pages or another static website provider. That hosting provider may process standard technical data, such as IP addresses or request logs, to deliver and secure the website. This website does not need cookies, advertising, or analytics to display this policy.

Children

Health for Agents is not designed for children and is not intended to knowingly collect information from children.

Changes to this policy

This policy may be updated when the app changes. The effective date above will be updated when material changes are made.

Not a medical device

Health for Agents is a technical data export utility. It does not offer medical advice, diagnosis or treatment and is not intended to replace professional medical judgment.

Contact

Health for Agents is provided by Sebastian Philipp Brabetz (OwnData Labs). For privacy questions or support, contact: owndatalabs+support@gmail.com.

If you email support, we receive your email address and the content you send through our email provider, Gmail. We use that information to answer your request, not to collect HealthKit records. Please avoid sending sensitive health data or bearer tokens. Where the GDPR applies, ordinary support correspondence is processed as necessary to respond to your service request (Article 6(1)(b)) or for our legitimate interest in handling other enquiries (Article 6(1)(f)). Correspondence is kept only as needed to handle the enquiry and any applicable retention obligations.