Health iAge Privacy Policy

1. Privacy at a glance

• Health Age calculations run on your iPhone.
• The App requests read-only access to selected Apple Health information and does not write to Apple Health.
• The App does not require or create a Health iAge account.
• The App has no developer-operated backend for HealthKit samples, Health Age results, or health history.
• App-managed health information and derived results are stored on your devices and can be deleted from within the App.
• The App uses consent-controlled Firebase Analytics, Crashlytics, and Performance Monitoring for limited product interaction, crash, and performance data. Firebase does not receive your HealthKit samples or Health Age results.
• The App contains no advertising SDK, does not use IDFA or IDFV, does not personalize advertising, and does not track you across other companies' apps or websites.
• Apple processes subscriptions and purchases through StoreKit and the App Store.

2. Apple Health information

You decide which available read permissions to grant through Apple's system interface. The App may request read access to the following categories when supported by your device, operating-system version, region, and available HealthKit data.

Profile and eligibility

• date of birth, used to determine chronological age and supported-age eligibility;
• biological sex, when available, used only for local routing and applicability checks; and
• wheelchair-use and activity-move-mode settings, when relevant to local interpretation.

The App does not infer, default, or clamp age or biological sex.

Activity, exercise, and workouts

• step count, exercise time, move time, stand time, stand hours, flights climbed, push count, active and basal energy;
• walking, running, cycling, swimming, wheelchair, rowing, paddling, skiing, skating, and other supported distance, speed, cadence, power, effort, and workout summaries;
• supported traditional and functional strength-training workouts; and
• supported workout-route-derived features.

If you authorize Workout Routes, route coordinates are processed only in memory to derive limited workout features and are immediately discarded. Route coordinates are not persisted by the App.

Sleep, heart, respiratory, and recovery signals

• sleep analysis and supported sleep stages;
• VO₂ max, resting heart rate, heart rate, walking heart rate, heart-rate recovery, and heart-rate variability (SDNN);
• respiratory rate, oxygen saturation, wrist temperature, supported breathing-disturbance data, and other supported overnight or recovery signals; and
• supported cardiovascular events, blood-pressure summaries, electrocardiogram metadata, and heartbeat-series summaries.

The App does not retain ECG voltage waveforms. High-frequency heart-rate readings are reduced to compact local summaries and individual readings are discarded after aggregation.

Body and mobility measurements

• height, weight, body-mass index, body-fat percentage, lean body mass, and waist circumference; and
• walking steadiness, six-minute walk distance, walking speed, step length, asymmetry, double-support percentage, and stair ascent or descent speed.

Wellness and personal context

• daylight, mindfulness, State of Mind, environmental and headphone audio exposure;
• supported nutrition, hydration, caffeine, alcohol, and dietary nutrient information;
• menstrual-cycle, pregnancy, lactation, contraception, fertility, reproductive, and supported symptom context; and
• supported metabolic, pulmonary, hearing, scored-assessment, sport, and other non-clinical HealthKit information used for local coverage, quality, eligibility, or personal context.

Clinical Health Records and FHIR records are not requested or read. Medication concepts, dependent medication-dose events, and vision prescriptions require separate per-object authorization and are not requested, queried, cached, or used by the current App version.

The App does not persist free-form HealthKit text, route coordinates, questionnaire answer sets, medication names, complete dose strings, ECG voltage waveforms, or exact sensitive-event times.

Apple does not allow apps to reliably distinguish denied read access from the absence of matching Health data. The App may therefore describe either situation as “no data or access limited.” You can change Health permissions at any time in the Health app or iPhone Settings.

3. How Health information is used

Authorized information is processed locally to produce wellness outputs such as:

• an estimated Health Age and age gap;
• a Health Age trend and Health Age Trend Ratio;
• coverage and quality indicators;
• factor contributions based on recent personal trends;
• reversible Today signals; and
• a versioned five-level local state reference.

The Health Age Trend Ratio is a descriptive same-version trend ratio. It is not a physiological aging rate or a prediction of future aging.

The state reference is a static local engineering reference. It is not a percentile, rank, leaderboard, external calibration, or comparison with real Health iAge users, and it does not affect the Health Age calculation.

These outputs are general-wellness estimates. They are not medical advice, diagnoses, treatments, disease detection, measures of cellular or biological age, predictions of lifespan, or statements of medical accuracy.

4. On-device storage and retention

The App stores the information needed to operate locally on your devices. Current technical limits include:

• up to 180 days of retained canonical source samples, depending on the type and its approved local retention rule;
• approximately 35 days of hourly aggregates;
• up to 72 hours of five-minute inference inputs and transferred Watch motion summaries;
• up to five years of compact daily or closed-week summaries for supported normalized and catalog data; and
• up to five years of compact daily and calculation-versioned closed-week Health Age history.

Supported complex and sensitive types are reduced to the minimum eligible statistics or counts. The App does not persist route coordinates, free-form text, ECG voltage waveforms, questionnaire answer sets, medication names, complete dose strings, or exact sensitive-event times.

The App's local health cache and derived-report files use iOS Data Protection and are excluded from device backups in the current implementation. Health iAge does not upload those files to a developer-operated health-data server.

5. Apple Watch and Automatic Sleep Estimation

When Apple Watch features are available and used, the iPhone App sends a minimum derived display snapshot to the paired Apple Watch through Apple's device-to-device connectivity. That snapshot may include a display value, age-gap or trend direction, freshness, limited factor or Today summaries, state-reference information, and model/version information required by the Watch interface.

The Watch display payload does not include raw HealthKit samples, date of birth, biological sex, route coordinates, or detailed sleep, heart-rate, HRV, or other health readings. A complication is visible on the watch face by design, and anyone who can see your watch face may see the displayed result.

If you enable Automatic Sleep Estimation, the Apple Watch may use authorized Core Motion information. Raw motion readings are reduced on the Watch to five-minute counts, coverage, variance, jerk, and active-fraction summaries. Raw readings are not written to App storage or transferred. The summaries move only to the paired iPhone, remain on your devices, and are retained for no more than 72 hours. Apple-provided sleep records remain authoritative when available.

6. Sharing

The App may let you preview and share a derived Health Age summary through Apple's system share sheet. Sharing begins only when you select the share action and choose a recipient or destination. The intended share payload does not include raw HealthKit samples.

Once you share information, the recipient app, service, or person controls its copy under its own privacy terms. Review the preview and destination before sharing.

7. Subscriptions and purchases

Apple processes Health iAge subscription purchases, payment methods, transaction history, refunds, taxes, and subscription management through StoreKit and the App Store under Apple's terms and privacy policy.

The App receives Apple-provided product information, introductory-offer eligibility, and verified entitlement status needed to display plans and unlock features. The App does not operate its own payment server and does not send StoreKit transaction identifiers, prices, receipts, or payment information to Firebase.

Deleting local Health iAge data does not cancel a subscription or erase Apple's transaction records.

8. Firebase analytics and diagnostics

The App uses Firebase Analytics, Firebase Crashlytics, and Firebase Performance Monitoring, provided by Google, to understand whether product flows work, diagnose crashes, and improve responsiveness and reliability. Firebase is not used to calculate Health Age, build a health profile, advertise to you, or track you across other companies' apps or websites.

When Firebase collection is enabled

• For a new user whose App Store storefront is in the European Economic Area or United Kingdom, all three Firebase services remain disabled and Firebase is not initialized until the user chooses Share Analytics.
• For other storefronts, and when the App Store storefront cannot be determined, collection is enabled by default.
• Every user can turn Share Analytics on or off in Settings at any time.
• A saved refusal or approval remains in effect unless the user changes it or a future App version resets the consent policy and asks again.

Data Firebase may process

Health iAge does not set a Firebase user ID. The App does not send Firebase any:

• HealthKit sample or health value;
• Health Age or age-gap value;
• date of birth or biological sex;
• health-factor identity or contribution;
• detailed Health authorization state;
• StoreKit transaction identifier, price, receipt, or payment information;
• user-entered or free-form text;
• share payload; or
• user-facing or localized caught-error description.

The App does not attach custom Crashlytics logs, custom keys, or caught error objects. An automatically generated fatal-crash report can nevertheless contain technical exception names or reasons supplied by iOS or the runtime as part of the crash stack.

The App uses FirebaseAnalyticsCore. IDFA and IDFV collection, advertising storage, advertising user data, advertising personalization, Google Signals, Google Ads/AdMob links, and cross-App tracking are disabled. The App does not request App Tracking Transparency permission.

Firebase retention and user controls

• The Production Google Analytics property is configured for 14-month retention of user-level and event-level Analytics data. This setting does not control standard aggregated reports.
• Firebase states that Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal from live and backup systems.
• Firebase Performance Monitoring retains IP-associated events for 30 days and installation-associated or de-identified performance data for 60 days before beginning removal.
• Firebase installation identifiers may remain until a deletion request is made to Firebase; Google states that removal from live and backup systems may then take up to 180 days.

Turning Share Analytics off disables future Analytics, Crashlytics, and Performance collection by the App, resets local Analytics data, and deletes Crashlytics reports still waiting to be sent. It does not automatically delete telemetry already received by Google.

Because Health iAge has no account and does not expose a Firebase identifier as an account identifier, we may not be able to identify a particular user's previously received pseudonymous telemetry. Contact privacy@healthage.cloud about an applicable request. Google may process Firebase data on global infrastructure under its applicable terms and privacy policy. Additional service details are available in Firebase's privacy and security documentation.

9. Support communications

If you contact support, we receive the contact details, message content, and attachments you choose to provide. This is separate from the App's on-device health processing and Firebase telemetry. Please do not send Apple Health screenshots, raw health values, medical information, Health Age or age-gap values, payment-card information, passwords, Apple Account credentials, verification codes, device passcodes, or StoreKit transaction identifiers.

We use support communications to respond to your request, operate and secure the service, comply with legal obligations, and establish or defend legal claims. Depending on applicable law, this processing may be based on performing our agreement or taking steps you request, our legitimate interests in providing and protecting the service, compliance with law, or consent where required.

We retain support correspondence only for as long as reasonably necessary for those purposes, taking account of the nature of the request, security needs, applicable limitation periods, and legal-retention duties. Email, hosting, security, and professional-service providers may process these communications for us under contractual or confidentiality obligations. They are not permitted to use support information for their own advertising.

10. Information we do not use for the launch service

The current App does not:

• create a Health iAge user or guest account;
• operate a developer backend for HealthKit samples, Health Age results, or health history;
• sell Apple Health data or derived Health Age results;
• use Apple Health information for advertising, credit, employment, or insurance decisions;
• use IDFA, advertising personalization, or cross-App tracking;
• send health values or Health Age results to Firebase; or
• compare you with a database of real Health iAge users.

Apple may independently process App Store transactions, platform diagnostics, and other Apple-service information under Apple's policies and your device settings.

11. Your choices and controls

Apple Health permissions

Review or change Apple Health permissions in the Health app or iPhone Settings. Removing access does not delete source information from Apple Health.

Automatic Sleep Estimation

Turn Automatic Sleep Estimation on or off in You → Settings → Apple Watch. You can also change Motion access through Apple's system settings. Turning it off stops new App-managed Watch motion summaries; Apple Health sleep records are unaffected.

Share Analytics

Turn Firebase collection on or off using Share Analytics in You → Settings. The consequences of turning it off are described in Section 8.

Delete local health data

Use You → Settings → Apple Health → Delete local health data. After confirmation, the App clears its managed health cache, reports, and history, returns to onboarding, and makes derived Watch displays unavailable when connectivity permits.

This action does not delete source information from Apple Health, automatically revoke Apple Health permissions, cancel a subscription, or erase Apple transaction history. You may need to complete Health authorization again before new results can be calculated.

Delete the App

Deleting the App removes its local App container according to iOS behavior. It does not delete source information from Apple Health or cancel an App Store subscription.

Subscription controls

Use Restore Purchases or Manage Subscription in the App. Apple controls billing, cancellation, refund eligibility, and transaction records.

12. Children and age-related boundaries

The adult Health Age estimate is supported only for ages 18 through 79 inclusive. Users aged 14 through 17 may receive a limited youth-wellness experience but do not receive an adult Health Age, age gap, Health Age Trend Ratio, younger/older result, state reference, share conclusion, Watch age, or complication age. Unsupported or unknown ages do not receive an adult estimate.

Health iAge is not intended for children under 14. Where local law requires parent or guardian authorization for use of the App, Apple Health access, or a purchase, that authorization must be obtained through the applicable Apple and family-account controls.

If you believe a child sent personal information to support without appropriate authorization, contact privacy@healthage.cloud so we can review and, where required, delete it.

13. Security and international processing

We minimize data movement and use Apple platform protections for local files. Firebase encrypts data in transit, and applicable Firebase services encrypt supported data at rest. No method of storage or transmission is completely secure.

Firebase telemetry and support communications may be processed in countries or regions other than where you live, depending on the locations of Google, us, and our service providers. Where applicable law requires transfer safeguards, we use legally recognized safeguards or rely on another lawful transfer mechanism.

Protect your device passcode, control who can view your iPhone and Apple Watch, and review destinations before sharing.

14. Your privacy rights

Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of, or portability of personal information we hold, and to object to or withdraw consent for certain processing. Withdrawing consent does not affect processing already lawfully completed. You may also have the right to complain to your local data-protection authority.

Because HealthKit information and Health Age history are stored only on your devices and are not associated with a Health iAge account, we generally cannot access, export, correct, or delete that local information for you. Use the controls described in Section 11.

To make a request about information we hold, contact privacy@healthage.cloud. We may need to verify that the request relates to you, and legal exceptions may apply.

15. Changes to this policy

We may update this Privacy Policy when the App, law, or our practices change. The effective and last-updated dates identify the current version. Where required, we will provide notice of material changes.

A future health-data backend, account, cloud history, advertising capability, new telemetry category, or materially different Health data use will require this Privacy Policy and the App Store privacy disclosures to be reviewed before release.

16. Contact

Application provider: AI Negotiator Technology Limited Privacy requests: privacy@healthage.cloud General support: service@healthage.cloud Support page: https://support.healthage.cloud/ Terms of Use: https://terms.healthage.cloud/