Privacy Policy

Privacy Policy

Last Updated: November 3, 2026

This Privacy Policy explains how HealthApp ("we," "us," or "our") handles information in the current iOS HealthApp application (the "App") and related services. It covers local health records, camera-based fingertip pulse and heart rate variability ("HRV") estimates, measurement-result analytics, installation identifiers, diagnostics, attribution, subscriptions, and support.

Important summary: Health records and measurement calculations are primarily kept or performed on your device. The App does not provide a HealthApp-operated cloud health-record backup or analysis service. However, the current App sends available pulse, HRV, and recovery-score values in measurement-result events to Google Firebase Analytics, as explained in Section 4. Local processing therefore does not mean that no health-related information leaves your device.

1. Health Information and Local Records

Depending on the features you use, the App handles manually entered blood glucose, blood pressure, and heart rate readings; medication entries and schedules; notes and timestamps; camera-based pulse and HRV estimates; derived wellness scores; and supported activity information you authorize it to read from Apple Health.

Blood glucose and blood pressure readings must come from external measurement devices. The camera feature estimates pulse and HRV from optical pulse signals; it does not measure blood glucose, blood pressure, or oxygen saturation.

Health histories, calculations, charts, and supported reports are stored or generated on your device. The current App does not automatically upload your full health history to HealthApp-operated servers for analysis, cloud backup, or cross-device synchronization.

There are separate transfers you should understand: measurement-result analytics described in Section 4; records you choose to export or share; and information you choose to send to support. Analytics events are not a backup of your health history and do not allow you to restore that history through the App.

2. Fingertip Pulse and HRV Estimates

With camera permission, the App uses the device camera and may use the camera flash while you place a fingertip over the camera. It analyzes changes in light and color caused by blood flow to estimate pulse and variation in the intervals between detected pulse beats. This is an optical pulse estimate, not an electrocardiogram. It does not scan a fingerprint, recognize your identity, or create or store a fingerprint template.

In the released App, raw camera frames and temporary optical samples are processed locally during measurement. They are not saved as raw measurement recordings or uploaded to HealthApp-operated servers, Firebase/Google, AppsFlyer, or Meta.

Resulting pulse and HRV estimates, derived scores, timestamps, measurement-quality information, and supported report information can be saved locally. The separate Firebase measurement-result events can contain the available numerical results identified in Section 4, but do not contain raw camera frames or raw optical sample arrays.

You can stop a measurement and allow, decline, or revoke camera permission in device settings. Revoking camera permission prevents future camera measurements. It does not delete previously saved local results or information already received by an analytics provider.

3. Installation, Support, and Purchase Information

The current iOS App does not require a user-created login account. It uses installation-linked identifiers and service records for functions such as membership status, installation reporting, purchases, and technical operation. These records are separate from your local health history.

When you contact support, we receive the contact details, messages, and attachments you choose to send. We use them to respond, investigate problems, and handle privacy requests. Please do not send health records, payment details, or other sensitive information unless necessary for your request.

Apple processes purchases made through the App Store. We do not receive your full payment card details from Apple.

For purchase verification, the App sends transaction information to HealthApp-operated servers, including the transaction identifier, product identifier, App Account Token, and Apple-signed StoreKit 2 transaction information in JWS format. We use it to verify purchases, prevent duplicate or fraudulent claims, determine subscription status, and provide or restore paid benefits.

4. Analytics, Diagnostics, Installation, and Attribution

Services Used

The App uses Google Firebase Analytics for App events, Firebase Installations for installation identifiers, and Firebase Crashlytics for crash and error diagnostics. It uses AppsFlyer for installation and campaign attribution, and the Meta Facebook SDK for supported App events and advertising measurement. Apple StoreKit is used for purchases.

Technical Information

Depending on the service, configuration, and permissions, information may include the CUID described below; AppsFlyer ID; Firebase App Instance ID; Firebase Installation ID; Facebook Anonymous ID; IDFA when authorized and available; IDFV; device model; operating system; App version; language; network information such as IP address; installation source; campaign information; sessions; feature interactions; and product, subscription, and purchase events.

Diagnostic information can include crash reports, non-fatal errors, stack traces, device state, timestamps, and technical context. We do not intentionally attach health-record contents, medication notes, raw camera frames, or raw optical sample arrays to diagnostic reports. Measurement-result analytics are a separate data flow described next.

Measurement-Result Events Sent to Firebase Analytics

The current App sends report-view and valid-report events to Google Firebase Analytics. Current event names include hr_meas_res_vw and hr_meas_real_report. When available, their parameters include:

- bpm: pulse in beats per minute;

- hrv: the HRV estimate, represented by RMSSD in milliseconds; and

- score: the recovery score on a 0–100 scale.

Unavailable results are not included as valid numerical values. Events can also include experiment assignments, such as sh2_measure, and technical event or attribution context. Firebase processes events in association with its App-instance and related service information.

These are health-related numerical values. They are not necessarily anonymous simply because your name is not attached. We use the events to understand measurement completion, report generation, feature usage, and reliability. They do not contain raw camera frames, raw optical sample arrays, your full health-history database, or medication notes.

Google/Firebase is a third-party recipient. This transfer is not an upload to a HealthApp-owned health-record analysis server. Explaining the transfer in this policy does not replace any separate consent required by law or platform rules.

Other Feature and Subscription Events

The App records interactions such as App opening, returning to the foreground, completing onboarding, starting a measurement, viewing a report, opening a subscription page, selecting a product, and completing a purchase. Depending on the event, parameters can include feature or entry-button category, experiment assignment, product identifier, price, subscription status, and installation or attribution context.

The App's current AppsFlyer and Meta event payloads do not attach the numerical pulse, HRV, or recovery-score parameters listed above. Some events nevertheless identify use of a health-related feature or the type of record added. A feature-use category is different from a numerical reading, but may still reveal health-related interests or activity.

Persistent CUID

The App creates or uses a stable identifier called a CUID. On iOS, it can be stored in Keychain and may remain across sessions and, depending on operating-system behavior, reinstalls. It is sent to HealthApp-operated APIs as healthappDeviceId to associate installation, service, security, and subscription requests.

The CUID is also set as the AppsFlyer customerUserID and is therefore sent to AppsFlyer. These identifiers refer to an installation or service context and are not necessarily anonymous.

Installation and Service Reporting to HealthApp

The App sends available identifiers to HealthApp-operated servers for installation reporting and service operation. They can include CUID, AppsFlyer ID, Firebase App Instance ID, Firebase Installation ID, Facebook Anonymous ID, IDFA when authorized and available, and IDFV.

First-party service events include lifecycle, onboarding, and subscription interactions. We use them for installation statistics, attribution, service continuity, entitlement management, fraud prevention, and product-operation analysis. The current client does not send the measurement-result numerical parameters described above to these first-party event endpoints for health-history analysis.

Advertising Attribution

AppsFlyer and Meta process permitted installation, device, campaign, and event information to measure advertising effectiveness. Uses that constitute tracking under Apple's rules require the applicable App Tracking Transparency ("ATT") authorization. Denying ATT limits authorized tracking and IDFA access; it does not disable every SDK or every analytics event. Section 6 explains the current App's controls.

5. Purposes of Processing

We use information for the following purposes:

- On your device, to record and display health information, estimate pulse and HRV, calculate supported wellness indicators, show charts and trends, manage reminders, and create supported exports.

- To read supported activity information from Apple Health when you authorize access.

- To understand measurement completion and report generation using the Firebase result events disclosed in Section 4.

- To measure App usage, onboarding, feature interactions, installation sources, advertising attribution, and subscription-page performance.

- To verify purchases, maintain membership status, restore paid benefits, and prevent fraud or duplicate claims.

- To investigate crashes and technical problems, respond to support and privacy requests, and protect the Service.

Local health calculations are separate from installation reporting, advertising attribution, subscription verification, and Firebase analytics. The latter can include the health-related result values explicitly disclosed above; they should not be treated as purely non-health technical information.

Camera-based estimates and derived indicators are for general wellness, not diagnosis or treatment. This policy does not authorize a use of sensitive information that is prohibited by applicable law or platform rules.

6. Permissions and Available Choices

Camera. You can allow, decline, or revoke camera access in iOS settings. Without access, the fingertip camera feature is unavailable. Other available features can still be used. Revocation does not erase prior records or analytics.

Apple Health. Access is optional and can be managed through Apple's Health and privacy controls. The current integration reads supported steps, active energy, walking/running distance, and workout information. It does not synchronize your logged blood glucose, blood pressure, or fingertip measurement records with Apple Health. Revoking access stops future authorized reads; previously imported activity information must be managed separately using available controls.

Notifications. You can manage notification permission in iOS settings. Disabling notifications affects reminders but does not delete your records.

ATT and Advertising Identifiers. You can manage ATT in Settings > Privacy & Security > Tracking, where available. The App accesses IDFA only when authorized and available. ATT permission is not the same as consent to process health information and does not replace any additional consent required by law.

Firebase Analytics. The current App does not provide an in-App switch that disables Firebase Analytics. Denying ATT does not by itself stop the measurement-result events disclosed in Section 4. Camera permission, ATT, local deletion, and requests to delete analytics data are separate controls or actions.

For questions or requests concerning processing, contact lorenalici@icloud.com. A privacy request is not itself an automatic technical switch in the App. We will explain the available actions and handle applicable rights as described in Section 10.

7. Storage, Security, Retention, and Deletion

Local Health Records

Raw camera frames and temporary optical samples are used during measurement and are not retained as raw recordings. Saved estimates, report information, and manually entered histories are kept on your device unless removed through available controls or loss of App data.

Settings > Data > Clear All Data clears local heart rate, blood glucose, and blood pressure history and resets related settings. Labels may vary by language. It should not be treated as erasing every type of data associated with the App. Medication or activity records, exported files, information in Apple Health, and copies held by recipients must be managed separately using the relevant controls.

Clearing local data does not delete information already received by Firebase, AppsFlyer, Meta, HealthApp-operated servers, or Apple. It does not cancel a subscription.

First-Party Installation and Purchase Records

HealthApp-operated servers retain installation-linked technical and service records while needed for the purposes described in this policy. Transaction records may also be retained to administer purchases, prevent fraud, resolve disputes, or meet accounting, tax, or other legal obligations. Retention for a legal obligation is limited to the information and period required.

The CUID may remain in Keychain after the App is deleted. Uninstalling is not a request to delete server-side records associated with that identifier.

Firebase, AppsFlyer, and Meta

Firebase Analytics events, including measurement-result parameters, are retained under the retention settings of the applicable Google Analytics property and Google's service terms. Aggregated reporting may remain after user-level or event-level data expires. Crashlytics diagnostics are subject to the relevant Firebase service's retention and deletion practices.

AppsFlyer and Meta retention depends on their services, configuration, applicable partner requirements, and privacy terms. We do not represent that clearing data in the App deletes information from these services. We use applicable provider controls or request mechanisms when handling a verified request concerning data we control.

Support and Privacy Requests

Support messages and attachments are retained while needed to respond, investigate issues, maintain necessary security records, or meet legal obligations. Do not include unnecessary sensitive information in a support message.

Email lorenalici@icloud.com to request deletion of information handled by us. We may need limited information to verify the request and identify the relevant installation, events, or transactions. We process verified requests within applicable legal deadlines, subject to lawful retention requirements. We cannot promise deletion of records independently controlled by Apple, another provider, or a recipient you selected; we will explain any relevant limits.

Security

We use reasonable safeguards appropriate to the information handled. Protect your device with a passcode and keep its software updated. No storage or transmission method is completely secure. We provide security-incident notices when required by applicable law.

8. Sharing and Disclosure

We do not sell or rent your health records. This does not mean that no health-related information is sent to third parties: the current App sends the Firebase measurement-result values described in Section 4.

Google/Firebase receives analytics, installation, and diagnostic information, including the available pulse, HRV, and recovery-score parameters in the identified result events.

AppsFlyer and Meta receive the relevant identifiers, technical information, attribution data, and supported App events described above. The current App does not attach the identified numerical measurement results to their event payloads, but health-feature interaction categories can still be included.

HealthApp-operated services and their infrastructure providers handle installation-linked service records, technical events, and purchase verification. These are not a cloud backup or remote-analysis service for your full health history.

If you export a report, share a file, or send health information to support, the selected recipient or service receives what you choose to send. Copies held by another app, email service, storage provider, or recipient are governed by that party's practices. Apple Health access described in this policy reads supported activity information; it is not a general two-way health-record synchronization feature.

We may disclose information in our possession where required by law or valid legal process, or when reasonably necessary to address fraud, security incidents, or legal claims. If a merger, acquisition, or business transfer affects information we hold, applicable notice, consent, and privacy requirements continue to apply.

9. Third-Party Privacy Information

Google Firebase and Google Analytics

Recipient: Google. Services: Firebase Analytics, Firebase Installations, and Firebase Crashlytics. Information includes App-instance or installation identifiers, usage and subscription events, technical diagnostics, and the measurement-result parameters described in Section 4. Purposes include usage analysis, measurement-flow evaluation, installation services, and reliability.

Privacy information:

https://firebase.google.com/support/privacy

https://policies.google.com/privacy

AppsFlyer

Recipient: AppsFlyer. Information can include CUID as customerUserID, AppsFlyer ID, authorized and available advertising identifiers, device and network information, installations, sessions, attribution results, and supported App events. Purposes include installation measurement, campaign attribution, and fraud prevention.

Privacy information:

https://www.appsflyer.com/legal/privacy-policy/

Meta Facebook SDK

Recipient: Meta. Information can include Facebook Anonymous ID, permitted identifiers, device and network information, supported App events, product or subscription interactions, and campaign information. Purposes include App-event measurement and advertising attribution.

Privacy information:

https://www.facebook.com/privacy/policy/

Apple

Apple provides App Store purchases, StoreKit transaction information, device permissions, and the optional HealthKit integration. Apple processes information under its own terms. HealthApp receives the transaction information and authorized activity information described in this policy, not your full payment card details.

Privacy information:

https://www.apple.com/legal/privacy/

Provider privacy notices explain their practices; linking to them does not replace HealthApp's obligations concerning information it collects or controls.

10. Your Choices and Privacy Rights

You can review records using available App controls, clear the supported local histories, manage camera, notification, tracking, and Apple Health permissions, and choose whether to export or share information.

The current App does not provide a user-created login account or an account-deletion screen. For requests concerning installation-linked service records, analytics information, purchases, or support records handled by us, email lorenalici@icloud.com.

Clearing local data, uninstalling the App, revoking a permission, and requesting deletion of remote records are different actions. None should be assumed to perform all of the others. Local deletion and uninstallation do not cancel an Apple subscription.

Depending on applicable law, you may have rights to access, correct, delete, or receive a copy of personal information; restrict or object to processing; withdraw consent; appeal a denied request; or complain to a privacy authority. We will not unlawfully discriminate against you for exercising applicable rights.

We may request limited information necessary to verify and locate the relevant records and will respond within applicable legal deadlines. We cannot remotely erase records stored only on your device. Withdrawal of consent does not affect processing that was lawful before withdrawal. We will explain any lawful limits to a request, including required retention of transaction or security information.

11. Children and Teenagers

HealthApp is not intended for children under 13. We do not knowingly collect their personal information through our services. If you believe a child under 13 has provided information to us, contact lorenalici@icloud.com so we can investigate and take appropriate action.

Users aged 13–17 must have parental or guardian permission and any additional authorization required by local law. Parents and guardians should supervise health tracking and information sharing. Records held only on a device must be managed on that device.

12. International Processing

Raw fingertip camera frames and temporary optical samples are processed locally, not uploaded. Other information sent to the services described here, including the identified health-related Firebase events, technical identifiers, attribution data, transaction records, and support messages, may be processed outside your country of residence.

Where applicable law requires safeguards for international transfers, the relevant requirements apply. Contact us for information about the processing arrangements relevant to your request.

13. Changes to This Policy

We may update this policy when features, practices, or legal requirements change. We will update the date above and provide appropriate notice of material changes. Where new processing requires consent, we will obtain it before that processing begins. Continued use does not replace consent required by law.

14. Contact Us

HealthApp Support

Email: lorenalici@icloud.com

Suggested subject: Privacy Request - HealthApp

Terms of Service:

https://sites.google.com/view/health-app0