1. Scope and current status
The product is intended for adults to record and review personal health information. It does not diagnose, recommend treatment or provide emergency medical monitoring. The app is in development and has not launched on the App Store.
Live ads and charging are disabled in the current development build. A separate ad test connects to Google for official test ads only after its network notice and your explicit agreement. Development and local purchase tests make no real charge.
The following sections describe implemented data paths and the advertising and purchase design that is not yet active. This policy and store disclosures must be checked and updated before those services launch.
2. Your on-device journal
Entered and imported measures, readings, units, measurement times, time zones, contexts such as fasting or after a meal, labels, notes and sources are stored in a local database. Language and unit preferences and reminder plans are also stored on the device.
The app has no health account, cloud journal sync or operator backend for receiving health records. It does not upload your journal to the operator. Sample data uses a separate in-memory journal and is not added to real history.
The app uses iOS local data protection. Your device, system backups and file destinations you choose have their own security and backup settings. This does not mean exported files receive additional app-level encryption.
3. Apple Health and permission
Apple Health is optional. The app reads only supported measures you select and are allowed to access, to organize records and charts locally. It does not write, modify or delete Apple Health source data, or use health data for ad targeting.
Change read access in Apple Health or the iOS health privacy settings. Deselecting a measure in the app changes future sync selection; it does not revoke permission at system level.
Revoking read access does not automatically remove previously imported local history. No returned data can mean no records, limited access or no permission; the app cannot determine from an empty result whether you denied access.
4. Access, deletion and retention
You can review records, export information and confirm deletion of a manual record in its details. Imported Apple Health originals are read-only in this version, with no separate control to clear imported copies.
When the system supplies an explicit source deletion event, a later sync removes the corresponding local import and annotations. Revoking access or receiving an empty query does not clear history. The app does not delete Apple Health source data.
The local journal remains until removed with the available controls or by choosing Delete App in iOS. Offload App keeps documents and data and does not clear the journal. Apple Health source data, saved or shared files, system backups and store transactions are managed separately.
The operator cannot remotely retrieve or delete health records that exist only on your device. You may contact the operator about access, correction, deletion or other privacy requests. Support correspondence and website service metadata must be handled in their respective systems under applicable requirements.
5. Export, backup and sharing
A report can include full readings, units, times, sources, labels, notes and charts for your selected period. A full backup covers the whole journal independently of report filters. Available outputs include PDF reports, CSV and JSON data as appropriate.
Export and backup files have no app-level encryption and can contain sensitive health information. Review contents, recipients and storage before saving or sharing. Cloud storage, email or other apps you choose handle files under their own rules.
The app cleans up its own temporary exports, but not copies you save or share. Backups exclude notification plans, Apple Health query state and purchase entitlements. A health backup cannot grant Pro access.
6. Reminders
With your permission, iOS local notifications provide a general prompt to record. Their content does not include readings, post-meal contexts or notes. Reminder plans stay on the device.
Pause, edit or delete a plan in the app, or change permission in iOS notification settings. Reminders are not medical alerts and delivery at a particular time is not guaranteed.
7. Advertising and privacy choices
Live advertising is disabled. The planned free version uses Google Mobile Ads and the User Messaging Platform for banners and related privacy choices. Only the separate test tool currently requests official test ads after explicit agreement.
Advertising services may process IP addresses and approximate location, device identifiers, ad views and interactions, performance, crash and diagnostic information for advertising, security and related services. Non-personalized advertising can still involve this information; it does not mean an ad SDK processes no data.
Health readings, selected measures, fasting or post-meal contexts, measurement times, notes, sources and health-record identifiers are not sent to advertising services or used for ad targeting.
The test tool allows you to stop and withdraw test permission. The app then stops initiating loads and removes the banner, although requests already sent may finish. Verified Pro access stops app-initiated ad loading and removes banners; it does not delete information a provider previously retained lawfully.
8. Pro and Apple store services
Pro is designed as a one-time purchase for permanent ad removal, without a subscription. Logging, Apple Health import, charts, full export, backup and restore are the same in Free and Pro. No release product is configured in the current development build and it makes no real charge.
After launch, Apple store services handle purchases, payments and transactions. The app uses those services to verify, restore and update access. The operator does not receive payment-card details. Health records are not purchase credentials. Local test transactions do not become release purchase credentials; refunds or revocations trigger access checks.
9. This website and Cloudflare
This static website is planned for Cloudflare hosting, delivery and security services. Its source includes no analytics, tracking pixels, third-party fonts, external scripts, login or health-data upload form.
Visiting still makes network requests to the host. Cloudflare may process IP addresses, browser or device request information, request time and address, and network or security logs to deliver, route and protect the site. Website access does not involve zero data processing.
Service metadata retention depends on the actual Cloudflare configuration and policies. The website does not automatically send the health journal on your device to Cloudflare. External links and your chosen email client have their own policies.
10. Email support
If you send a support email, the operator and its email service process your sender address, message, voluntary attachments and delivery metadata to answer and handle your request. The website has no support form and does not automatically attach your health journal.
Please provide only your app and iOS versions, steps to reproduce the issue and necessary context. Avoid identity documents, full medical histories and unredacted health screenshots. A full health journal is not required for support.
Support correspondence should be retained only as needed to handle the request and meet applicable obligations. Contact the operator about access, deletion and retention of correspondence. The actual email service and retention arrangements must be confirmed before publication.
11. Providers, regions and changes
Depending on features you use, Apple, Google, Cloudflare, email services and recipients you choose may each process information related to their service. Locations and rules can vary by service and region. Using these services does not automatically upload the local health journal.
This policy does not establish regulatory or store approval in any region. Launch regions, relevant choices and service configuration need to be checked against actual arrangements before release.
Material changes to data paths, providers or features require this page and its effective date to be updated, with notice where appropriate. Use the contact address on this page for privacy questions.