HYDRA Water tracker Get the app
Back to the journal

Hydra · The fine print

Privacy Policy

Last updated · October 27, 2026

AW Builds (“we,” “our,” or “us”) operates the Hydra mobile application (the “App”). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our App. Please read this policy carefully. By using the App, you agree to the collection and use of information in accordance with this policy.

This website. The Hydra site is a static page. It sets no cookies and uses no analytics or advertising. To show the premium prices in your local currency, your browser may ask ipwho.is for your country; that request includes your IP address and is handled under ipwho.is's privacy policy. We do not receive or store it. The country is kept in your browser for the session. If you choose a currency manually, the site remembers your choice in this browser and does not use the country lookup on later visits. If the lookup fails, the site uses your browser's language setting and then the international USD prices. Google Play shows the exact price and currency you will be charged.

1. Information We Collect

a) Information you provide

Your name, weight, phone number and profile picture are stored locally on your device and are never sent to any analytics service. We operate no server of our own that receives your data.

Your drink logs are also stored locally — in a private database on your phone. However, so that we can see how the app is used and where it breaks, some of what you log is also sent to Google Firebase Analytics as usage events: the millilitres of each drink, the drink type, the hour and day of the week, your daily goal, your streak length, and the names you give to your custom drinks. We do not send your name, your weight or your phone number to analytics. If you never turn on Google Drive Sync, no copy of your drink log exists anywhere but your phone.

b) Automatically collected information

When you use the App, certain information is collected automatically through integrated third-party services:

  • Analytics data: We use Google Firebase Analytics to collect usage data such as app opens, screen views, feature usage frequency, session duration, device type, the amounts you log, your daily goal as a user property, and the names of your custom drinks. This data is used solely to improve app performance and user experience. It does not include your name, weight, phone number or profile picture.
  • Crash reports: We use Firebase Crashlytics to automatically collect crash logs and diagnostic data. This helps us identify and fix bugs. Crash reports may include device state, operating system version, and stack traces, but do not contain personal data.
  • Product analytics & session recordings: Where permitted by your consent choices, we use Microsoft Clarity to understand how people interact with the App (for example, taps, scrolls, and anonymized session recordings). Screens containing sensitive information are masked before recording. In regions where you decline analytics or ad personalization (for example, via the consent prompt shown in the EEA/UK), no Clarity data is collected.
  • Advertising data: We use Google AdMob to serve advertisements, which may be mediated through partner networks such as Unity Ads. These services may collect and use device advertising identifiers, IP address, approximate location, and interaction data to serve personalized or non-personalized ads based on your consent choices.
  • Cloud backups: If you enable Google Drive Sync, your hydration data is stored only in your personal, hidden Google Drive AppData folder. We do not have access to these backups; they are strictly bound to your Google account and can be deleted by you at any time.

c) Location & weather data

If you grant location permission and enable weather-based adjustments, the App uses your device's location (coarse or precise, depending on what you allow) solely to fetch current local weather conditions from the OpenWeatherMap service. Your coordinates are sent directly from your device to OpenWeatherMap to retrieve the forecast that adjusts your daily hydration goal. We operate no servers and never receive a copy of your location. You can deny the location permission or disable weather adjustments at any time; the App remains fully functional without it.

d) Information from push notifications

The App uses Firebase Cloud Messaging (FCM) to deliver push notifications such as hydration reminders. To enable this, Firebase may associate a device token with your device. We do not use this token to identify you personally.

2. How We Use Your Information

We use the information described above for the following purposes:

  • To provide, maintain, and improve the App's functionality.
  • To deliver hydration reminders and push notifications.
  • To display advertisements via Google AdMob and its mediation partners.
  • To analyze aggregated, anonymized usage patterns to improve user experience.
  • To diagnose and fix technical issues using crash reports.
  • To process in-app purchases and manage subscription status through Google Play Billing.
  • To adjust your daily hydration goal based on local weather conditions (if location permission is granted).
  • To seamlessly create and restore automatic cross-device backups of your hydration data using the Google Drive AppData Scope (if enabled).

3. In-App Purchases & Subscriptions

Hydra offers optional premium subscriptions (Monthly, Yearly, Lifetime) processed entirely through the Google Play Store. We do not collect, process, or store any payment information. All billing is handled securely by Google. Please refer to Google's Privacy Policy for details on how payment data is handled.

4. Data Storage & Security

Your hydration data is stored on your device, in the App's private storage (an SQLite database and preference files that Android sandboxes so no other app can read them). We operate no servers that receive your personal data — but, as set out in section 1, some of what you log is also sent to Google Firebase Analytics as usage events, and crash reports go to Firebase Crashlytics. Those are the only copies that exist outside your phone, unless you turn on Drive Sync.

If you choose to use the backup/export feature, data is saved to a location you specify (e.g., local storage) or, with Drive Sync enabled, to your own hidden Google Drive AppData folder. We do not have access to your backups.

We implement commercially reasonable security measures to protect your information. However, no method of electronic storage or transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

5. Third-Party Services

The App integrates the following third-party services, each with their own privacy policies:

6. Permissions

This list covers every permission in the merged manifest — what actually ships, including the ones the advertising, billing, biometric and Firebase libraries add on Hydra's behalf. The permissions that need your say-so are requested at the moment you use the related feature, and saying no leaves the rest of the App working.

  • INTERNET: Required for ads, analytics, crash reporting, remote configuration, weather lookups, the in-app update check, and Drive backup. Hydra has no server of its own to talk to.
  • ACCESS_NETWORK_STATE: Added by the Unity Ads SDK behind the AdMob mediation, so the App can check whether the device is online before it attempts a network call.
  • Location (ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION — optional): Used only to fetch local weather for goal adjustments. Denied by default; the App works fully without it.
  • POST_NOTIFICATIONS: To send scheduled hydration reminders.
  • Alarms & reminders (SCHEDULE_EXACT_ALARM): To fire hydration reminders at the times you schedule, even in Doze mode. Android treats this as a special access you can review and revoke in system settings.
  • DETECT_SCREEN_CAPTURE: Declared, but not currently used. The Insights screen hides itself with Android's secure-window flag instead, so no screen content is captured or transmitted. It is listed here for completeness.
  • Storage read (READ_EXTERNAL_STORAGE, Android 12L and below only): Declared and requested on those versions, but not currently used — the App writes its exports to its own app-specific folder and never reads your shared storage.
  • RECEIVE_BOOT_COMPLETED: To reschedule reminders after device restart.
  • VIBRATE: To provide haptic feedback on user interactions.
  • USE_BIOMETRIC and USE_FINGERPRINT: Added by AndroidX Biometric. Used only if you turn on the app lock, so the App can ask for a fingerprint or face before it opens.
  • WAKE_LOCK: Added by the Firebase measurement libraries, held briefly so a background job is not interrupted.
  • FOREGROUND_SERVICE: Added by WorkManager and the AndroidX libraries. Hydra itself never starts a foreground service.
  • ACCESS_ADSERVICES_TOPICS, ACCESS_ADSERVICES_ATTRIBUTION and ACCESS_ADSERVICES_AD_ID: Added by Google Mobile Ads and the Unity Ads SDK for the Privacy Sandbox, so ads can be selected and measured without your advertising identifier.
  • com.google.android.gms.permission.AD_ID: Added by the advertising SDKs. This is the device advertising identifier, used to serve and measure ads. It is reset when you clear your Play services data, and Google's consent form controls whether ads are personalised.
  • com.android.vending.BILLING: Added by Google Play Billing, so the App can check and charge for the Premium plans. Google handles all payment details; the App never sees them.
  • com.google.android.c2dm.permission.RECEIVE: Added by Firebase Cloud Messaging, so the App can receive push notifications, including campaigns sent from the Firebase console.
  • com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE: Added by the Firebase measurement libraries so the App can learn how it was installed. Google Play binds this service; the App cannot call it.
  • com.awbuilds.hydra.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: An app-defined signature permission generated by the AndroidX libraries, so their internal broadcast receivers cannot be triggered by other apps. It grants the App nothing and is invisible to you.

Hydra does not request camera, microphone, contacts, phone-call, SMS, media-library or background-location permissions, and it does not write to Health Connect — that feature is not implemented and is not exposed anywhere in the App.

6b. Data You Export

Three ways, all of them yours. CSV exports every logged drink from Settings. JSON backup is the same snapshot the Drive sync uploads. PDF exports your insights report. Each file is written to a location you choose and then handed to the share sheet; once you have sent it somewhere, handling it is entirely up to you and whoever you sent it to.

7. Children's Privacy

The App is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has provided us with personal data, please contact us so we can take appropriate action.

8. Your Rights & Choices

Your data is on your device and your control of it is immediate. You also have rights over the copies that reach third parties:

  • Delete your data: Use the “clear all data” option in the App's settings (or clear the App's storage / uninstall the App) to permanently erase your hydration logs, custom drinks and preferences, and to wipe the queued cloud backup.
  • Withdraw consent: Ads and analytics personalization are governed by the consent prompt shown where required by law (e.g., GDPR/EEA and UK). You can change or withdraw your choices at any time via your Android “Privacy” → “Ads” settings, or by clearing the App's storage so that Google's consent form is shown again; declining stops personalized ads and stops Clarity collecting anything.
  • Location: Deny or revoke the location permission at any time; weather-based adjustments simply stop.
  • Cloud backups: Delete your Drive AppData backup from the linked Google account's Drive storage at any time, or revoke the App's Drive permission from your Google account's third-party apps page.
  • Advertising identifier: Reset it by clearing your Play services data, or turn off ad personalisation in Android's Privacy settings.
  • Third-party data: For data collected by third-party services such as Firebase, Clarity, AdMob and OpenWeatherMap, please refer to their respective privacy policies for information on how to access, manage, or delete that data.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated “Last Updated” date. We encourage you to review this page periodically. Continued use of the App after changes constitutes acceptance of the updated policy.

10. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy, please contact us at:

Email: awbuilds.support@gmail.com

Read the Terms of Service