BaroGuard: Wear OS Barometer Privacy Policy

# BaroGuard: Wear OS Barometer Privacy Policy Last updated: August 26, 2026 BaroGuard is a standalone Wear OS barometer published by Quazmoz / Quinn Favo. ## Summary BaroGuard reads the built-in barometric pressure sensor on supported Wear OS watches and keeps its app data locally on the watch. The app does not use a BaroGuard account system, developer-operated backend, internet access, location access, advertising, in-app analytics, or cloud sync. ## Data stored locally BaroGuard may store the following app data locally on the watch: - Atmospheric pressure readings and timestamps. - Local pressure trend history and chart data retained for supported history windows. - Pressure unit preference, including kPa, hPa/mbar, inHg, or mmHg. - Pressure calibration offsets, reference values, modes, and calibration timestamps. - Optional pressure-alert threshold or custom threshold, time window, direction, cooldown, quiet-hours schedule, and capped local alert records. - Estimated-altitude reference settings and unit preference. - Wear OS Tile, watch-face complication, graph-window, retention, onboarding, and other app preferences. - Cached local values used by the Tile and watch-face complications. This information is used only to provide BaroGuard features on the watch. ## Pressure sensor, altitude, and vertical speed BaroGuard uses the watch barometer while the app is active to show live pressure, local trends, approximate pressure-derived altitude, and optional foreground-only vertical-speed sessions. Vertical-speed session measurements are processed while the session is active in the foreground. Sessions stop when BaroGuard leaves the foreground or pressure readings stop. BaroGuard does not retain permanent vertical-speed workout/session history. Pressure-derived altitude and vertical-speed values are approximate references. They can change because of weather pressure, calibration, watch hardware, sensor behavior, altitude changes, and environmental conditions. ## Tile and watch-face complications BaroGuard provides a cache-backed Wear OS Tile, its configurable complication provider, and dedicated Pressure, Pressure Trend, and Pressure Change complication providers. These surfaces read cached local settings and pressure/history data. They do not start continuous background pressure sampling and do not transmit pressure readings to the developer. ## Optional pressure alerts and notification permission Pressure alerts are optional and off by default. If the user enables informational pressure-change alerts, BaroGuard evaluates locally recorded foreground pressure history using the configured preset/custom threshold, time window, direction, cooldown, and quiet-hours schedule. On Android versions that require notification permission, BaroGuard may request POST_NOTIFICATIONS only after the user enables pressure alerts. Denying notification permission does not block the rest of the app. Quiet hours suppress informational notification delivery during the selected local-time window. They do not start background monitoring or change pressure collection behavior. Pressure alerts describe locally measured pressure changes. They are not weather forecasts, storm warnings, emergency alerts, or medical notifications. ## CSV export BaroGuard can create a CSV export of retained pressure history when the user explicitly requests it. The export is written to private app cache and presented through Android's system sharing flow so the user chooses the destination. BaroGuard does not automatically upload exports to a developer server. Once a user sends or saves an export with another app or service, that destination handles the file according to its own privacy practices. ## Network, accounts, advertising, and analytics BaroGuard does not use: - Internet access for app functionality. - A BaroGuard account or developer backend. - Developer cloud sync. - Advertising or advertising SDKs. - In-app analytics or developer telemetry SDKs. - Location. - Microphone or camera. - Contacts or calendar. - Health/body sensors. - Advertising ID. - Play Billing or in-app purchases in the current app code. Google Play, Android, and Wear OS independently process technical information required for app distribution, installation, updates, platform security, notifications, Tiles, and complications under their own policies. ## Backup and deletion BaroGuard disables Android backup and device-transfer extraction for its app-local data. Users can clear pressure history and alert history where available, clear BaroGuard storage in Wear OS settings, or uninstall the app to remove local app data. Because BaroGuard has no developer account or backend, there is no BaroGuard server-side account record to delete. ## Accuracy and safety BaroGuard is informational only. It is not a certified weather station, weather forecast service, storm warning system, emergency alert service, medical tool, professional altimeter, certified variometer, or aviation instrument. ## Changes This policy will be updated when BaroGuard materially changes its permissions, storage, networking, SDKs, or data handling. ## Contact For privacy questions or support, contact Quazmoz@vivaldi.net.