Obhasa Privacy Policy

1. About This Policy

This Privacy Policy explains how Obhasa handles information, including the optional Google Health private beta, including separately selected experimental insights, where available. Google Health features described here apply only to builds that include that beta.

Obhasa is a general-wellness application provided by Chan Ho Pang.

This policy describes Obhasa's current features and data practices. If the app's features or data practices change, this policy may be updated as described below.

2. Information Obhasa Accesses

Obhasa reads information from Apple Health only after you authorize access.

The current implementation requests read access to:

• heart information, including Heart Rate, Walking Heart Rate Average, Resting Heart Rate, Heart Rate Variability (HRV SDNN), and associated source, device, motion-context, and algorithm metadata when Apple Health provides it;
• Respiratory Rate;
• Sleep Analysis, including available sleep-stage information;
• activity information, including Active Energy, Resting Energy, Exercise Time, and Steps;
• Workouts, including available workout-effort information;
• Mindful Sessions; and
• State of Mind records.

Obhasa requests permission to write only State of Mind records. That permission is requested when you explicitly choose Save to Apple Health in Body Activation Beta. Obhasa does not otherwise write, modify, or delete Apple Health information.

You control which requested Apple Health data types Obhasa is permitted to access.

If you contact Obhasa for support or privacy questions, the developer may also receive information that you choose to provide, such as your email address, message, screenshots, device information, or other troubleshooting details.

Please avoid sending health exports, medical records, or other sensitive information unless it is necessary and specifically requested.

If your build includes Google Health Connect & Audit beta, you can optionally authorize Google Health access using your Google account. Obhasa requests read-only access to health metrics and measurements, sleep, and activity and fitness. With the separate insights confirmation, it queries Daily HRV (RMSSD), resting heart rate, sleep and available stages, sleep respiratory rate, daily heart-rate ranges, total and active energy, steps, activity minutes, recorded workouts and today’s hourly activity from Google/Fitbit wearables. Returned records may include dates, processing details, workout summaries and source/device metadata where supplied. Obhasa does not request Google profile, email, location or write permissions, and does not request exercise GPS routes or account identifiers. You can grant only some requested permissions; features needing missing permissions remain unavailable.

3. How Obhasa Uses Health Information

In the current version, Obhasa uses authorized Apple Health information to provide general-wellness features, including:

• HP and HP Signals;
• personal baselines and trends;
• Sleep Recharge;
• Sleep Deficit Load;
• Sleep Rhythm and estimated sleep-cycle information;
• daily activity and workout summaries; and
• Body Activation Beta, which presents timestamped physiological observations and optional State of Mind context.

Body Activation Beta does not diagnose or measure psychological stress or emotion. Its Settled, Activated, and Highly Activated descriptions compare compatible HR and HRV SDNN observations with compatible prior-day observations. The feature can display today and the previous six calendar days, including gaps where no eligible observation was available. Missing time is not treated as Settled, and the current implementation does not calculate activation duration.

If you choose to save a State of Mind entry, Obhasa uses the pleasantness, feelings, and associations you select to create that record in Apple Health. You can associate it with a selected eligible Body Activation observation from the current day, including a clearly labelled retrospective moment, or save it for the current moment without creating a physiological correlation. The State of Mind record remains separate from sensor-derived Body Activation and is not used to train or personalise the Body Activation model.

Obhasa may also use source and device information associated with Apple Health samples within the app to help select consistent sources, interpret personal history, and avoid duplicated or mixed readings.

Obhasa is intended for general wellness purposes.

Its information and insights are not medical advice, diagnosis, treatment, or a substitute for professional medical care.

Google Health is optional. Connecting lets you inspect daily heart-rate variability (RMSSD), resting heart rate, and sleep from Google/Fitbit wearables in the Audit screen. Connecting does not change your selected data source. If you separately choose Google Health and confirm “Use experimental insights,” Obhasa reads up to 78 civil dates of these measurements directly from Google to calculate experimental HP and Sleep Recharge and display up to 30 dated results. Without this additional choice, the Audit query covers today and the previous 14 dates for HRV, resting heart rate and sleep. With insights selected, additional charts and workouts cover up to 30 civil dates, and hourly activity covers today. These extra readings do not change the experimental score model.

These scores use a separate, unvalidated model, including an assumed eight-hour sleep need. They do not measure your biological sleep need, assess respiratory stability, or represent scores interchangeable with Apple Health. Missing or ambiguous data can prevent a score. A failed refresh preserves earlier readings with their original query and fetch time, but does not treat them as a newly successful calculation. Google HRV (RMSSD) remains separate from Apple Health HRV (SDNN). Google data is not written to Apple Health. Activity and recorded workouts use permitted Google data when Google insights are selected; Body Activation remains explicitly sourced from Apple Health. Workout energy means total energy during the session. Resting energy may be labelled as derived from comparable total minus active energy; it is not a separately observed Google resting-energy measurement.

4. Current Data Processing and Transmission

In the current version of Obhasa, authorized Apple Health information and derived wellness results are processed within the app on your device.

The current production app has no developer-operated backend that receives your Apple Health information or derived wellness results.

Obhasa currently has:

• no Obhasa account system; optional Google account authorization for Google Health beta;
• no analytics SDK;
• no crash-reporting SDK;
• no advertising SDK;
• no App Tracking Transparency, IDFA, or other tracking implementation;
• no third-party runtime SDK; and
• no Obhasa cloud-sync implementation.

As a result, the developer does not currently receive your Apple Health information or derived wellness results through the app.

These statements describe the current version of Obhasa. They are not a promise that the app's architecture or features can never change.

If a future version materially changes how information is processed, transmitted, stored, or shared, the relevant disclosures and this Privacy Policy will be reviewed and updated before release.

Google handles sign-in and consent on its authorization screen. Obhasa sends authorization, token exchange/refresh, health-data read, and revocation requests directly to Google over HTTPS. Those requests include the authorization information and query parameters needed for the selected operation. Google operates its service under its own terms and privacy practices. This authorization does not create an Obhasa account.

There is no developer-operated Obhasa backend receiving your Google Health readings or authorization tokens. This beta does not upload Apple Health information to Google. The developer does not receive Google Health readings through the app.

5. Local Storage and Retention

The current version of Obhasa stores your appearance preference locally using standard iOS application storage.

To support the Obhasa Home Screen widget, the app also stores a small derived status snapshot in a shared app-group container on your device. Depending on available information, this snapshot may include HP, Sleep Recharge, daily energy summaries, the start, end, and duration of the latest sleep session, an estimated sleep-cycle count, calculation dates, and internal model-version identifiers. The snapshot is replaced when Obhasa publishes an updated status and is protected using iOS file protection.

Obhasa does not currently create a persistent local database containing raw Apple Health samples, Body Activation observations, State of Mind records, or a complete derived wellness history. Apart from the local widget snapshot described above, fetched samples and calculated dashboard state are held for the current app session.

Apple Health remains the system of record for Apple Health information accessed by Obhasa and for any State of Mind record you explicitly save through Obhasa.

Deleting Obhasa removes information stored within Obhasa's local app and shared app-group containers, including the widget snapshot, but it does not delete health information stored in Apple Health or information managed by the apps and devices that contributed those records.

Because the current version has no Obhasa account or developer backend, there is currently no server-side Obhasa account or server-side health-data record maintained by the developer for you to delete.

Information you voluntarily provide when contacting the developer may be retained for as long as reasonably necessary to respond to your request, maintain appropriate support records, or comply with applicable obligations.

Google Health readings, derived scores, API audit entries, insights consent and source selection remain in memory for the current app session. A new app session starts with Apple Health selected. You must select Google insights again to fetch the longer history. Disconnecting, replacing the connection or detecting an expired/revoked grant clears the affected session readings and insights consent. Authorization tokens, their expiry, and granted scopes are stored in this device's Keychain, accessible only while the device is unlocked and not synchronized through iCloud. The beta does not keep a persistent Google Health history database or a Google Health widget snapshot.

Selecting Google clears the existing Apple widget snapshot and suppresses health-score widget publication. No Google measurements or scores are saved for widgets. A protected, backup-excluded marker containing no health measurements or account identity records that widget publication is suppressed. Switching back to Apple removes the marker and requires a fresh Apple snapshot; operating-system widget refresh timing can vary.

Deleting the app may leave Keychain authorization items. Disconnect Google Health before uninstalling and, if needed, remove Obhasa's access in Google Account connections. Disconnecting or uninstalling Obhasa does not delete health records held by Google, Fitbit, or Apple Health.

6. Apple Health and Google Health Permissions

You control whether Obhasa can read each requested Apple Health data type and whether it can save State of Mind records.

You can review or revoke Obhasa's access using Apple's Health and privacy controls in the Apple Health app or iOS Settings. Exact menu names may vary depending on your version of iOS.

Revoking access prevents future authorized reads or writes by Obhasa. It does not delete information already stored in Apple Health. State of Mind records previously saved through Obhasa can be reviewed, managed, or deleted in Apple Health.

For Google Health beta, you choose which of the requested permissions to grant on Google's consent screen. If you decline a permission, the corresponding readings cannot be retrieved. Connect or Reconnect starts Google authorization; returning to the app can refresh an existing connection without opening a new login screen.

Disconnect Google Health clears session readings and audit entries, attempts to remove local authorization tokens, and asks Google to revoke access. If secure storage reports a deletion failure, deletion has not completed; follow the displayed error, retry, or remove Obhasa in Google Account connections. If network revocation fails, remove Obhasa in your Google Account connections to finish revocation. You can also revoke access through Google Account controls. Previously stored records in Google Health are unaffected.

Cancelling Google's authorization screen before connection replacement preserves the existing session. Switching back to Apple is not a disconnect. Cancellation does not guarantee an in-flight transport stops immediately; reconnect and disconnect wait until the operation has returned. Both read permissions and separate in-app confirmation are required to enable experimental insights.

7. Third-Party Websites and References

Obhasa includes user-selected links to Apple resources, methodology sources, and research references.

Selecting one of these links may open a website operated by a third party. Those websites operate under their own terms and privacy practices.

Obhasa does not append your Apple Health information or derived wellness results to these reference links.

The current app does not embed third-party analytics, advertising, crash-reporting, or other runtime SDKs.

Obhasa does not currently share information obtained from Apple Health or derived wellness information with third parties.

If a future feature requires sharing information obtained from Apple Health, that feature will be subject to appropriate user permission, disclosure, and applicable platform and legal requirements.

Google Health beta communicates directly with Google to authorize access and retrieve your own readings. It does not send those readings to an Obhasa server or other recipients. Obhasa does not append your Google Health readings to reference links. Information you voluntarily send to support is received by the developer; avoid including unnecessary health records or credentials.

8. Advertising, Marketing, and Tracking

The current version of Obhasa contains no advertising or tracking implementation.

It does not request App Tracking Transparency permission or access the advertising identifier.

Information obtained through Apple Health or Google Health is not used for advertising, marketing targeting, or similar services and is not sold to advertising platforms, data brokers, or information resellers.

If Obhasa introduces advertising in a future version, information obtained through Apple Health or Google Health will not be used to target or serve those advertisements.

Obhasa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Health information is used only for the user-facing audit and separately selected experimental insights described here; it is not sold, used for advertising, credit or lending decisions, or used to train generalized AI models. The developer does not routinely access your Google Health readings.

9. Changes to This Policy

This Privacy Policy may be updated when Obhasa's features, legal obligations, or data practices change.

When an updated policy is published, the effective date and, where appropriate, the Privacy Policy Version at the top of this page will be revised.

Material changes to data practices will be reviewed before the related app version is released.

10. Contact

For privacy questions, requests, or other questions about this Privacy Policy, contact: