← Health2You legal home

Health2You Privacy Policy

Chips Studio · Last updated: 2026-08-20

Health2You is designed as a local-first wellness app. This policy describes what data the app uses and what is not collected by Chips Studio.

Health Data

Health2You can read selected Apple Health / HealthKit data only after you grant permission. This may include sleep, time in daylight, steps, active energy, exercise time, workouts, HRV, resting heart rate, height, and body mass.

Apple Health data is read only on device. Health2You processes this information on your device to generate sleep rhythm summaries, local rhythm scores, trend views, 10-day plans, and report exports.

Settings and Profile Information

Preferences and optional profile information you enter—such as display name, app mode, language, appearance, reminder choices, height, weight, age, health goal, and sleep targets—are stored in app-managed local storage. They are used to personalize on-device presentation and calculations. The current app code does not send them to a Chips Studio server.

Local Reports and Automatic Generation

Successful reports are saved as derived summaries in the app's Application Support container so the latest report and report history can be reopened after relaunch. These summaries do not contain raw HealthKit sample arrays, raw sleep segments, HealthKit source names, or raw category values. Reports are not silently evicted because of a count limit; you can delete individual reports or clear the history in the app.

On the first eligible launch or foreground of a local calendar day, Health2You can attempt to generate that day's report using the existing on-device report pipeline. It stores local lastAttempt and lastSuccess timestamps together with matching attempt/success local civil-day identifiers. The timestamps support the 30-minute failure cooldown. Each identifier stores only the yyyy-MM-dd civil-day value computed with the calendar/timezone active when the event occurred; it does not store a location or timezone name. A successful automatic report—or an existing successful manual report whose analysis end falls on today—satisfies today's freshness and suppresses an automatic duplicate. Permission denial, unavailable data, or failure may retry after the cooldown. Manual report generation remains unrestricted and is not replaced by this process.

Report access is not tied to subscription status. Expiration or revocation of Pro does not hide or delete locally saved reports and does not disable report export. Deleting an individual history item or clearing history removes those archived entries; the separate clear-latest control removes the latest snapshot. None of these controls deletes or changes data in Apple Health.

Report Exports

Export files are created in the app's Caches container only when you choose an export action. History reports can be exported as Markdown or native PDF; the latest-report export center supports Markdown, PDF, JSON, and CSV; date-range sleep export supports CSV and JSON.

Health2You does not upload exported files. A cache file may remain until it is overwritten or removed by the operating system, and a copy sent to a destination you choose in the system share sheet is governed by that destination's privacy practices.

Apple Watch, Widget, and Notifications

The iPhone and Apple Watch may exchange a reduced snapshot through Apple's WatchConnectivity framework. The Watch app stores the latest snapshot in its shared App Group so the Watch widget/complication can render without running the full iPhone analysis. This snapshot can include derived sleep/rhythm summaries, display source names, targets, settings, and update timestamps. Raw HealthKit sample arrays and raw category records are not placed in the App Group or widget timeline.

Optional local rhythm and Watch battery reminders use Apple's notification system. The app stores bounded local battery level/timestamp and alert-delivery/deduplication records needed for freshness checks, retry, cooldown, and duplicate prevention. These records are not uploaded to Chips Studio.

Local Storage and Device Backups

The data described above is stored in app-managed containers on the iPhone or paired Apple Watch. Depending on Apple platform behavior and your device backup settings, local app data may be included in an Apple-managed device backup. This is separate from collection by Chips Studio. User-initiated exports may also be copied to destinations outside Health2You.

What Chips Studio Does Not Collect

The current Health2You app code does not send Chips Studio:

Accounts, Ads, Analytics, and Tracking

Health2You does not require an account.

Health2You does not include ads.

Health2You does not include analytics.

Health2You does not include a third-party crash-reporting SDK or remote health-data service.

Health2You does not use third-party tracking.

Subscriptions

Health2You Pro subscriptions are handled by Apple through StoreKit. Subscription purchase and billing information is managed by Apple. Health2You uses StoreKit transaction status to unlock Pro features.

Medical Disclaimer

Health2You is for wellness and lifestyle reflection only. It is not medical advice, diagnosis, or treatment. It does not provide medication, supplement, or melatonin recommendations. If you have health concerns, consult a qualified healthcare professional.

Contact

Support contact: hideinicloud@icloud.com

Support page: Health2You Support