Privacy Policy
Last updated: 30 August 2026
HydroPulse estimates your hydration needs from data that stays on your watch. There is no account, no advertising SDK and no product analytics.
Summary
We do not sell data, run ads, or track what you do in the app. Two things leave the device, and neither carries your health data: an anonymous weather lookup (coordinates only, no account or device identifier), and a crash report if the app fails.
Data we process
| Data | Purpose | Where it is stored | Sent off-device? |
|---|---|---|---|
| Heart rate (watch sensor) | Estimate exertion for the hydration model | On-device memory only, not persisted long-term | No |
| Steps, active calories, exercise state | Distinguish activity from rest | On-device memory only | No |
| Approximate (coarse) location | Look up local temperature and humidity | Not stored; used transiently for the weather call | Yes — coordinates only, to Open-Meteo (open-meteo.com), with no account or device identifier |
| Weight, age, biological sex, resting and maximum heart rate, sweat profile, pregnancy or nursing status | Personalise the hydration model | Locally on-device (Android DataStore) | No |
| Water intake log (amount and timestamp) | Show history and feed the hydration ledger | Locally on-device (Room database) | No |
| Crash reports: stack trace, device model, OS version, app version, and a Firebase installation identifier | Diagnose and fix crashes | Sent on next launch after a crash; not stored in the app | Yes — to Firebase Crashlytics (Google). Contains no heart rate, no activity, no water log and no location |
Crash reporting
HydroPulse uses Firebase Crashlytics (Google) so that a crash can be diagnosed and fixed. When the app fails, it sends a stack trace along with the device model, OS version, app version and a Firebase installation identifier — an identifier for the app install, not for you.
A crash report never contains your heart rate, your activity, your water log, your profile or your location. It describes the failure, not the user.
Crashlytics is governed by Google’s Firebase privacy documentation. Reports are retained for a limited period and then deleted.
What we do not do
- No account creation, no login, no advertising identifiers.
- No advertising SDKs, and no product or usage analytics — nothing records which screens you open or how often you use the app.
- No backend of ours — the only network calls are the weather lookup and, after a failure, a crash report.
- No sale or sharing of personal data with third parties.
Health data
Heart rate and activity data are sensitive under Google Play’s health and fitness data policies. HydroPulse uses this data solely to compute the in-app hydration estimate, does not transmit raw heart-rate or activity data anywhere — crash reports included — and does not use it for advertising or profiling.
Permissions requested, and why
- BODY_SENSORS — read heart rate for the exertion component of the model.
- ACTIVITY_RECOGNITION — detect steps and exercise sessions.
- ACCESS_COARSE_LOCATION — look up local weather. Precise location is never requested.
- POST_NOTIFICATIONS — deliver hydration reminders.
All four are optional. Declined, the app keeps working with sensible defaults for the components it can no longer sense.
Data retention and deletion
All personal data — profile, water log, ledger — lives in local app storage on your watch. Uninstalling the app deletes it. There is no server-side account or profile to delete, because none exists. The one exception is crash reports, which sit with Firebase Crashlytics under Google’s own retention period; write to the address below to have any relating to your installation removed.
Children’s privacy
HydroPulse is not directed at children under 13 (or the relevant age of digital consent in your jurisdiction) and does not knowingly collect data from them.
Changes to this policy
Material changes are reflected here with an updated date above, and shipped alongside an app release note.
Contact
Questions about this policy can be sent to support@gethydropulse.com.