Obhasa Support

Contact Support

For questions, feedback, or help with Obhasa, contact:

Please avoid sending raw Apple Health exports, complete health histories, medical records, account credentials, or other unnecessary sensitive information.

Reporting a Problem

When reporting a problem, please include useful non-sensitive information such as:

• what happened;
• what you expected to happen;
• steps that reproduce the problem;
• the approximate date and time of the issue;
• your iPhone model;
• your iOS version;
• your Obhasa version and build number, if available; and
• when relevant, the Apple Health source device or app associated with missing or unexpected information.

Screenshots can be helpful when you are comfortable sharing them.

If additional information is genuinely needed to investigate an issue, support will explain what information would be useful before asking you to provide it.

The current version of Obhasa does not include analytics or crash-reporting services, so clear reproduction steps and device/version information can be especially helpful when diagnosing a problem.

Apple Health Permissions

The current implementation requests read access to:

• heart information, including Heart Rate, Walking Heart Rate Average, Resting Heart Rate, and Heart Rate Variability (HRV SDNN);
• Respiratory Rate;
• Sleep Analysis, including available sleep-stage information;
• Active Energy, Resting Energy, Exercise Time, and Steps;
• Workouts and available workout-effort information;
• Mindful Sessions; and
• State of Mind records.

Obhasa asks for State of Mind write permission only if you explicitly select Save to Apple Health in Body Activation Beta. It does not write other Apple Health data types.

If expected information is missing:

1. Confirm that Apple Health contains a recent compatible measurement from an eligible source device or app.
2. Review Obhasa's read permissions using the Apple Health app or Apple's Health and privacy controls in iOS Settings.
3. Return to Obhasa and reconnect or refresh after changing permissions or after new Apple Health information becomes available.

If a State of Mind check-in is not saved, review Obhasa's write access for State of Mind and try again. Previously saved records can be managed or deleted in Apple Health.

For privacy reasons, Apple does not always provide apps with enough information to distinguish between unavailable read access and the absence of an accessible Apple Health sample.

As a result, Obhasa may sometimes show information as unavailable without being able to identify the exact reason.

Google Health Private Beta

If your build includes this beta, open Data source → Review Google Health connection (also available through About → Beta integrations). Read the connection disclosure, continue to Google, and sign in with the account holding your Fitbit/Google Health data. Review the health metrics, sleep and activity/fitness read permissions. Grant the streams you want to use; missing permissions limit only the dependent features. Connecting alone does not select Google insights.

To use experimental Google HP and Recharge, return to Data source, select Google Health, tap Use, and review the separate insights disclosure. Confirm “Use experimental insights” to fetch up to 78 civil dates for up to 30 dated results. Cancel keeps the existing source and does not expand the query. Activity and Workouts use permitted Google data when Google is selected; Body Activation continues to use Apple Health.

Allow the additional activity and fitness read permission to see Google energy, steps, activity minutes and recorded workouts. Existing grants need an explicit reconnect/permission review; cancelling consent keeps the current session. Missing activity access does not disable permitted physiology or sleep. OAuth authorization does not itself prove a linked Google Health profile or API access; follow the specific account-linking/access prompt.

Sync compatible Google/Fitbit wearables first. API availability does not guarantee each device reports each metric. Missing/off-wrist intervals are not zero. Stage-less sleep may still provide Total Sleep; full activity minutes require complete reported intensity levels. Workout kcal is total energy; active duration is not elapsed time and no effort is inferred. Every metric retains its own query/fetch time. These added displays do not alter the existing experimental score model.

The Google model is experimental and unvalidated. It assumes eight hours of sleep need, does not learn biological sleep need in this revision, and does not assess respiratory stability. HP needs positive RMSSD and RHR, supported personal-history references and eligible sleep inputs. Recharge can remain available without physiology inputs. Unknown initial sleep load and missing historical sleep remain model scenarios; a numeric output is shown only when all supported scenarios round to the same integer. “Unavailable” is not zero or a low score. Google scores are not interchangeable with Apple scores.

For the private beta, your Google account must be eligible for the project's Google Testing audience. A TestFlight invitation alone does not make that account eligible. Ask the beta organizer to confirm the account if authorization is blocked.

Sync Fitbit with Google Health first, then refresh in Obhasa. Compare the same date, source and measurement; partial days, delayed sync, processing, permissions or timezone differences can affect results. Each metric has its own query and fetch time. A failed refresh retains earlier readings with their original provenance but does not present them as a new successful calculation. Retry the affected metric explicitly. Cancelling does not guarantee immediate transport termination; reconnect and disconnect remain unavailable until it returns.

History, consent, source selection and scores are session-only. After restart, Apple is selected and Google insights need confirmation again. Under Google's External / Testing configuration, refresh tokens for these permissions normally expire after seven days; reconnect when authorization expires or is revoked. A connection replacement requires reviewing the insights choice again.

While Google is selected, widgets have no health-score snapshot. Switching back to Apple requires fresh Apple publication; WidgetKit refresh timing is controlled by iOS. No Google numeric widget data is persisted.

Disconnect clears session data, attempts local token deletion and requests Google revocation. A reported secure-storage failure means deletion has not completed; retry and, if needed, remove Obhasa in Google Account connections. If remote revocation fails, remove Obhasa there to finish revocation. Disconnect before uninstalling because Keychain authorization items may remain after app deletion. Switching to Apple alone does not disconnect Google.

For support, include the build number, iOS version, steps, affected metric, selected date, approximate time and safe error category. Do not send passwords, authorization codes, tokens or raw API responses. Describe whether readings match without sending health screenshots unless needed and requested.

Missing Data

An unavailable value is not the same as a poor wellness status.

It means Obhasa did not receive enough usable information to calculate or display that particular value.

Possible reasons include:

• no recent compatible measurement;
• unavailable, denied, or revoked Apple Health permission;
• a change in source device or source app;
• device or Apple Health synchronization timing;
• unsupported or manually entered data being excluded where applicable; or
• insufficient personal history for a baseline or model.

Some personal baselines and insights require multiple valid days or nights of information before they become available.

Body Activation Beta

Body Activation Beta uses compatible HR and HRV SDNN observations to describe a past physiological moment as Settled, Activated, or Highly Activated relative to compatible prior-day observations.

It is not real-time monitoring and does not detect psychological stress, emotion, focus, illness, or intent. Always check the observation timestamp. Missing time is unknown rather than Settled, and Obhasa does not calculate daily, weekly, or monthly activation duration in this phase.

A Body Activation result can be unavailable because:

• fewer than seven compatible prior days are available;
• HR and HRV are not close enough in time;
• source or known-device information is incompatible;
• an observation overlaps a Workout, Sleep, or Mindful Session;
• Heart Rate motion context indicates activity;
• the latest usable observation is too old; or
• a required Apple Health query fails.

State of Mind hearts on the timeline are user-reported Apple Health records. Their timing can be viewed beside Body Activation observations, but proximity does not establish cause. State of Mind responses are not used to change the Body Activation tier.

Use the left and right arrows in Daily observations to review today and the previous six calendar days. Empty dates remain visible, and the two-hour strip distinguishes windows with eligible observations from completed windows without eligible data. Historical days are view-only.

When today contains an eligible Body Activation observation, select its chart point and choose Selected · [time] to record State of Mind for that moment, or choose Now to record the current moment. A selected observation more than two hours old is labelled Retrospective. Yesterday and older observations are not available for backfilling in this Phase 1A screen.

When no eligible Body Activation observation exists today, Obhasa still offers How do you feel right now? Saving it creates a current, unpaired State of Mind record in Apple Health. It does not create or imply a missing physiological observation.

Sleep Data

Sleep Recharge, Sleep Deficit Load, Sleep Rhythm, and estimated sleep-cycle views depend on sufficient Apple Health sleep information.

Sleep Rhythm additionally depends on adequate staged-sleep information.

When the available evidence is insufficient, Obhasa may leave a result unavailable rather than treating it as zero or interpreting it as a poor result.

The sleep-cycle information shown by Obhasa is estimated from available sleep data and should not be interpreted as a clinical measurement of sleep cycles.

App Version

When contacting support, please include your installed Obhasa version and build number if available.

Version and build information can help identify whether a problem relates to a particular release.

Do not send device identifiers, Apple account information, passwords, authentication codes, or other credentials.

Privacy

For information about how Obhasa handles information, Apple Health access, and Google Health beta, please see the https://obhasa.app/privacy.

For privacy questions, contact: