The core hydration log stays local
Hydration records, daily goals, bottle model, cap state, studio lighting, text logo, and bottle pose are used to restore app state and remain on the current device. Hydrate Lab does not upload the core hydration log to the membership backend or describe the product as cloud history sync.
Clearing app data or uninstalling the app affects the local record on that device. Understand that lifecycle before taking action.
Service boundary: Google login, sessions, and membership snapshots belong to account and subscription services. They do not mean the hydration log has been uploaded or can be restored across devices.
What does membership process?
If you use Google login or membership features, the service processes account identifier, name, email, and avatar, plus the session, membership, and purchase verification information required for those services. Google Play handles subscription transactions; RevenueCat and Cloudflare Worker/D1 support membership according to the privacy policy.
How can I control or delete data?
- Clear local hydration records from the app Settings.
- Signing out, clearing app data, or uninstalling does not cancel a Google Play subscription.
- To delete the server account and associated sessions, identity mapping, and membership snapshot, submit a request through the developer contact on the app listing.
For the full scope, retention, and account deletion process, read Privacy and Delete account. For help, visit Support.