1. Who provides Health iAge
Health iAge is provided by AI Negotiator Technology Limited, an organization in China. Privacy questions and requests can be sent to privacy@healthage.cloud.
2. Apple Health information we request
You decide which available read permissions to grant through Apple's system interface. The current version may request:
- Date of birth, to determine chronological age and supported-age eligibility.
- Biological sex, when available, for supported age- and sex-specific target ranges. Missing values are not inferred.
- Available health types covering activity and workouts, sleep, cardiorespiratory fitness, recovery and vital signs, mobility, and body composition, plus optional context and data-quality signals described in the app and Apple's permission sheet.
Health iAge does not write data to Apple Health. Because HealthKit does not reliably distinguish denied read access from a lack of matching samples, the app may describe either situation as “no data or access limited.”
3. How the information is used
The selected information is used on your iPhone to produce an estimated Health Age, age difference, Today signals, longer-term trends and trend ratio, data coverage, and modeled factor contributions.
The method combines your own recorded patterns with supported target-reference ranges. It has not been externally calibrated to a population and does not rank you against other users. These outputs are wellness estimates—not diagnoses, cellular or biological age measurements, lifespan predictions, or statements of medical accuracy.
4. On-device storage and retention
Health iAge uses tiered on-device retention: raw retained samples for approximately 180 days, intraday aggregates for 35 days, and daily or weekly health aggregates for up to five years. Derived report history is bounded to 840 hourly points, 1,830 daily points, and 265 weekly points; weekly factor-attribution history is bounded to 53 points.
Optional sleep estimation keeps reduced sensor-evidence summaries for up to 72 hours and inferred sleep sessions for approximately 180 days. Raw accelerometer readings are not stored by Health iAge, and raw heart-rate samples are not retained in the persistent health cache.
App-managed health-data cache and derived report files use iOS Data Protection and are excluded from device backups in the current implementation. Health iAge does not upload these files to a developer-operated server.
5. Apple Watch and complications
If you use the Apple Watch features, the iPhone app sends a minimal derived snapshot to the paired Apple Watch using Apple device-to-device connectivity. It may contain a display value, direction, freshness, and model/reference version.
The Watch payload does not contain raw Apple Health samples, date of birth, biological sex, or detailed sleep, heart-rate, or HRV values. Complication values are visible on the watch face you choose.
6. Sharing
Health iAge may let you preview and share a derived summary through Apple's system share sheet. Sharing occurs only when you initiate it and choose a destination. The intended share payload does not include raw Apple Health samples. The recipient's terms and privacy practices apply after sharing.
7. Subscriptions and purchases
Apple processes Health iAge subscription purchases, payment methods, transaction history, refunds, and subscription management through StoreKit and the App Store. The app receives Apple-provided product details, introductory-offer eligibility, and verified entitlement status needed to show plans and unlock features.
Deleting local Health iAge data does not cancel an Apple subscription or erase Apple's transaction records.
8. Analytics and diagnostics
Health iAge uses Google's Firebase Analytics, Crashlytics, and Performance Monitoring to understand product flows, diagnose crashes, and improve reliability. New users whose App Store storefront is in the EEA or United Kingdom are asked before Firebase is initialized. Known storefronts elsewhere default to collection enabled; if the storefront cannot be determined, Firebase remains disabled until the user chooses Share Analytics. Every user can turn Share Analytics on or off in Settings.
Depending on the service, Firebase may receive a pseudonymous App, installation, or session identifier; coarse country-level location derived from network information; device, operating-system, App-version, locale, carrier/network, and App-state information; allow-listed product-interaction and purchase-flow tokens; crash stacks and technical exception information; and startup, refresh, StoreKit-flow, or network performance measurements.
Health iAge does not set a Firebase user ID or upload Apple Health samples or values, Health Age or age-difference results, birth date, biological sex, health-factor identity or contribution, detailed Health authorization state, StoreKit transaction IDs, prices, receipts, share content, free-form text, or user-facing/localized caught-error descriptions. It does not attach custom Crashlytics logs, keys, or caught errors. An automatic fatal-crash report can contain technical exception names or reasons generated by iOS or the runtime.
Firebase is used only for product analytics and App functionality. Health iAge uses FirebaseAnalyticsCore and disables IDFA and IDFV collection, advertising storage and personalization, Google Signals, Google Ads/AdMob links, and cross-App tracking. The App does not request App Tracking Transparency permission.
The Production Analytics property is configured for 14-month user/event-data retention; that setting does not govern standard aggregated Analytics reports. Firebase states that Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal, while 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 can remain until deletion is requested from Firebase, after which removal may take up to 180 days.
Turning Share Analytics off stops future Analytics, Crashlytics, and Performance collection, resets local Analytics data, and deletes unsent crash reports. It does not automatically erase data already received by Google. Because Health iAge has no account, we may not be able to identify a particular user's earlier pseudonymous telemetry. See Firebase's privacy and security information and Google's Privacy Policy.
8A. Optional offers and price-drop notifications
If you turn on “Offers and price drops” in Notifications settings, you agree to receive promotional notifications about Health iAge+ offers and price reductions. This is separate from Apple Health permissions, subscription-service reminders, and Share Analytics. It is not enabled by an older notification preference or by allowing notifications in iPhone Settings alone.
To deliver these messages through Google Firebase Cloud Messaging and Apple Push Notification service, the app registers a messaging token. Our notification service stores an opaque installation identifier and credential hash, an encrypted messaging token, the consent version and time, notification permission status, preferred language, time zone, and a limited subscription state (active, inactive, or unknown). We use subscription state to avoid sending acquisition offers to active subscribers. No Apple Health samples, Health Age results, demographics, receipts, or StoreKit transaction identifiers are sent to this service or used to select marketing recipients.
You can withdraw this consent at any time by turning off “Offers and price drops” in Notifications settings. The app unregisters for remote notifications, requests deletion of the Firebase messaging token, and removes its delivered offer notifications. When the cancellation reaches our service, it immediately disables marketing and removes the stored messaging token. If offline, the app retains the cancellation locally and retries synchronization when reopened. Messages already accepted by platform delivery services may still be in transit.
Devices whose status has not been updated for 30 days are excluded from campaigns. Backend maintenance removes installation records and campaign delivery records older than 90 days without an update. Delivery records contain only the installation identifier, campaign identifier, attempt time, and service result needed to prevent duplicates and diagnose delivery. Google and Apple also process necessary delivery information under their own policies. We do not combine these records with third-party advertising data or health data.
9. Support communications
If you contact service@healthage.cloud, we receive the contact details and message content you choose to provide. This is separate from the app's on-device health processing. Please do not send Apple Health screenshots, raw health values, medical information, passwords, verification codes, payment-card information, 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 is based on performing our agreement or taking requested pre-contract steps, our legitimate interests in providing and protecting the service, compliance with law, or consent where consent is 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. We may use email, hosting, security, or professional-service providers to process these communications on our behalf under appropriate contractual or confidentiality obligations. We do not permit them to use the information for their own advertising.
10. Information we do not use for the launch service
- No Health iAge account or developer health-data backend.
- No advertising SDK, IDFA, advertising personalization, or cross-App tracking.
- No health values, Health Age results, demographics, transaction IDs, free-form text, or share content in Firebase telemetry.
- No sale of Apple Health data or derived Health Age results.
- No use of Apple Health data for advertising, credit, employment, or insurance decisions.
- No comparison with a database of real Health iAge users.
Apple may process App Store transactions, platform diagnostics, and other Apple-service information under Apple's policies and your device settings.
11. Your controls
You can change Apple Health permissions in the Health app or iPhone Settings. The app's “Delete local health data” control clears Health iAge reports/history and its local Apple Health-derived cache, returns the app to onboarding, and makes derived Watch displays unavailable when connectivity permits.
This does not delete source data from Apple Health, revoke Apple Health permissions automatically, cancel an Apple subscription, or erase Apple transaction history. Deleting the app removes its local app container according to iOS behavior.
12. Age-related boundaries
The adult Health Age estimate supports ages 18–79 inclusive. Ages 14–17 may receive limited youth wellness guidance but do not receive an adult Health Age, age gap, trend ratio, or younger/older result. Unsupported or unknown ages do not receive an adult estimate.
13. Children and younger users
Health iAge is not intended for children under 14. Users aged 14–17 receive only the limited youth experience described above. Where local law requires parental 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 has sent personal information to our support address without appropriate authorization, contact privacy@healthage.cloud so we can review and, where required, delete it.
14. Security, international processing, and your rights
We minimize data movement and use Apple platform protections for local files, but no storage method is completely secure. Because launch health information is stored only on your device, we generally cannot access, export, correct, or delete it for you.
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.
Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of, or portability of personal information that 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.
To exercise a privacy right, contact privacy@healthage.cloud. We may need to verify that the request relates to you, and legal exceptions may apply. Health iAge may be offered internationally, subject to App Store availability and applicable law.
15. Changes and contact
We may update this policy when the app, law, or our practices change. The effective date above identifies the current version. A future health-data backend, account, cloud history, advertising, new telemetry category, or materially different Health data use will require a new review.
Privacy requests: privacy@healthage.cloud
General support: service@healthage.cloud