Privacy
HealthPipe Privacy Policy
Effective date: October 2, 2026
HealthPipe is developed by Arron Taylor. This policy explains how the HealthPipe iOS app handles information when you export Apple Health data and use automatic exports.
Your health data and your destination
HealthPipe requests read access to the Apple Health categories you choose. It reads and processes those records on your device to create the selected JSON or CSV export. HealthPipe does not write changes to Apple Health.
When you run an export, HealthPipe sends the selected health data directly to the HTTPS receiver you configure. This can include metric names, dates, values, units, and source information, depending on the selected metrics and format. Your health export is not sent to the HealthPipe scheduling service as part of push registration or scheduling.
You decide which destination receives your exports. That destination may store, use, or share the information under its own policies. Use a receiver you trust and have permission to use. HealthPipe does not control data after it reaches your receiver.
Information stored on your device
HealthPipe stores app settings, selected metrics, destination configuration, delivery history, and pending export records in its local app storage. Pending export payloads may contain health information and are retained locally so interrupted deliveries can resume or retry. Delivery history can include timing, delivery outcomes, record counts, and error details.
Custom authorization headers and other configured header values are stored in the iOS Keychain. They are sent to your chosen receiver when required to deliver an export. Local information is retained as needed to operate the app; HealthPipe does not promise that delivery history or pending exports are erased immediately after each attempt.
Automatic exports and push notifications
HealthPipe uses a scheduling service operated through Doomo at api.doomo.dev to help wake the app with silent push notifications. The service receives and stores your Apple Push Notification service device token, a registration identifier, the preferred sending interval, whether scheduling is enabled, and operational timestamps such as the last push time. These details are used to register your device and send background wake-up notifications through Apple.
The scheduling registration does not include your health export payload, receiver URL, or receiver authorization headers. The device token identifies an app installation for push delivery; no HealthPipe account or login is required.
Like other internet services, service infrastructure may process technical request information, such as IP addresses, request timing, and errors, to operate and secure the service. Push registration records are retained to operate scheduling. Turning off automatic exports disables scheduling for the current registration; it does not itself erase that registration record. Contact us if you want help removing a scheduling registration.
iOS controls background execution. Silent pushes and your selected interval do not guarantee that an export will run at an exact time.
Advertising, analytics, and sharing
HealthPipe does not include advertising or third-party analytics SDKs and does not track you across other companies’ apps or websites. We do not sell your health data, use it for advertising, or send it to the scheduling service for profiling.
Information is shared as needed to provide the functions you choose: health exports and configured headers go to your receiver, and push registration information is processed by the scheduling service and Apple’s push infrastructure. Hosting and infrastructure providers may process service information to operate that service.
Support communications
If you contact us, we receive the email address and information you include. We use that information to respond and troubleshoot your request. Please do not send health exports, API keys, passwords, authorization headers, or other sensitive information. Redact these from screenshots and error messages.
Your choices
Choose the health categories HealthPipe may read through Apple Health’s app permissions. You can revoke access at any time.
Change selected export metrics, date ranges, formats, and your receiver in HealthPipe.
Turn off automatic exports and optional alerts in the app. Revoking health access also prevents the app from reading those categories for future exports.
Contact us about scheduling-registration removal or other privacy questions. We may need limited information to identify the relevant registration; do not send health records.
Contact your receiver’s operator to manage or delete data already delivered there. Revoking access or disabling exports does not recall previous deliveries.
Security
HealthPipe requires HTTPS for export destinations and uses HTTPS to communicate with the scheduling service. Credentials are stored using the iOS Keychain, and local app data is held in the app’s storage container. These measures reduce risk, but no storage or transmission system can guarantee absolute security. Keep your device and receiver secure and protect receiver credentials.
Policy changes and contact
We may update this policy as HealthPipe changes. The effective date above identifies the current version.
For privacy questions or requests, contact Arron Taylor at taylorarronj@gmail.com.
Arron Taylor
Software engineer building products that matter. Writing about faith, technology, and life in Milwaukee.
No comments yet. Be the first to share your thoughts!