Skip to Content
FeaturesPrivacy, Support, And Diagnostics

Privacy, Support, And Diagnostics

Status: Current implemented behavior and support policy. Audience: Users and contributors. Implementation: features/settings, diagnostics-gated settings, local support docs. Navigation: Screen.SettingsDebugDiagnostics in diagnostics builds, Settings support links. Related: Feature map, Privacy, Support.

OpenVitals is designed as a local-first Health Connect app.

For the standalone privacy reference, see Privacy. For support-oriented questions, see FAQ.

Privacy Model

OpenVitals does not require:

  • An OpenVitals account.
  • OpenVitals cloud sync.
  • OpenVitals analytics.
  • Ads.

Health data is read from and written to Health Connect on device. OpenVitals stores local preferences such as widget order, goals, reminders, calibration, and display choices.

Internet Boundary

The app does not need app-level internet access for normal health features. Offline map packs, imports, widgets, and Health Connect reads are handled locally.

Diagnostics

Diagnostics surfaces help users and maintainers understand local issues without sending health data automatically. They can include app version information, debug build separation, import reports, logs, and crash-report email drafts.

Settings and project metadata can point users toward support and community resources such as Zulip, Codeberg, or donation links.

Health Disclaimer

OpenVitals insights are wellness context. Scores, readiness estimates, cardio load, Body Energy, and sleep explanations are not medical diagnosis or treatment advice.

RemindersFeature Map