Last updated: 1 June 2026
App: Water Intake (Android, package com.ackbiz.water_intake)
Contact:contact@ackplus.com
This policy describes what data the Water Intake app collects, how it's used, who it's shared with, and the rights you have over it. We've tried to keep it plain — if anything's unclear, email us.
TL;DR
- Everything you log in the app — water entries, daily goal, drink presets, reminder settings — stays on your phone. We never see it, upload it, or sync it anywhere.
- We do collect anonymous crash reports and aggregate usage stats (which screens are opened, what feature is tapped) via Google Firebase so we can fix bugs and prioritise the right features. These reports never include what or when you drank.
- There are no ads, no third-party advertising SDKs, no marketing pixels, no tracking across other apps.
- You can stop all of the above by uninstalling the app — there's no separate account to delete.
1. Data we collect
1.1 Data that stays on your phone (we never see it)
The app stores the following locally in a private SQLite database on your device:
- Every water entry (volume, drink type, timestamp, optional note)
- Drink presets you've created
- Your daily goal, wake / sleep window, reminder schedule
- Theme + accessibility preferences
- Onboarding state (whether you've completed setup)
This data does not leave your device. We have no copy of it. If you uninstall the app or wipe its data via Android Settings → Apps → Water Intake → Storage, it's gone permanently — there is no backup.
1.2 Data sent to Google Firebase (anonymous / aggregate)
We use two Firebase services so we can keep the app working well:
- Firebase Crashlytics — if the app crashes, Crashlytics sends a stack trace, your device model, OS version, and an auto-generated, resettable installation identifier. The crash report does not include your intake log, presets, goal, or any other content you entered.
- Firebase Analytics — counts events like "app opened", "entry logged", "settings changed", "screen viewed". These are aggregated with all other users' counts; we use them to see whether a new feature is being used, never to profile individuals. Analytics includes Android Advertising ID by default; if you've opted out of personalised ads at the Android system level, Firebase respects that.
We do not enable Firebase Remote Config, Firebase Messaging push notifications, or any other Firebase service beyond Crashlytics and Analytics.
1.3 Permissions the app requests
- Notifications (POST_NOTIFICATIONS) — required to deliver the hydration reminders you've scheduled. We do not send marketing notifications.
- Exact alarms (SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM) — required so reminders fire at the minute you chose rather than "around" that time. Used only for your own reminder schedule.
- Boot completed (RECEIVE_BOOT_COMPLETED) — required so scheduled reminders survive a phone reboot. Used only to re-register your reminder schedule.
- Internet (INTERNET) — required for crash reports, anonymous analytics, and our optional update check. The app does not make requests to any other server.
We do not request: location, contacts, microphone, camera, body sensors, accounts, calendar, SMS, call logs, files outside our own sandbox, or the Health Connect API.
2. Data we do not collect
To be explicit, we do not collect or process:
- Your name, email, phone number, or any other contact identity
- Precise or approximate location
- Photos, files, contacts, or messages
- Health data outside what you type into the app (and that stays on device — see §1.1)
- Browsing or app-usage data outside Water Intake itself
- Biometric or sensor data
- Children's data — see §6
3. How we use what we collect
The anonymous data described in §1.2 is used to:
- Diagnose and fix crashes
- Decide which features to invest in next
- Make sure the app works on the Android versions our users actually run
It is not used to:
- Show you ads
- Build a profile of you
- Train any AI or ML model
- Sell or rent to third parties
- Combine with data from outside the app
4. Who we share it with
- Google Firebase / Google LLC — receives the crash reports and analytics events described in §1.2. Google's processing of this data is governed by the Google Privacy Policy and Firebase's own terms.
- No-one else. We have no other processors, no ad networks, no attribution SDKs, no CRM, no email vendor connected to the app.
We do not sell or rent personal data to anyone, ever.
5. How long it's kept
- On-device data (§1.1) — kept until you delete it in the app or uninstall.
- Crashlytics data — Firebase retains crash reports for 90 days by default; we don't extend this.
- Analytics data — Firebase Analytics aggregate data is retained for 14 months by default; we don't extend this.
6. Children's privacy
Water Intake is not designed for, and is not directed at, children under 13. We do not knowingly collect data from children under 13. If you believe a child has used the app, contact us at contact@ackplus.com and we'll address it.
7. Your rights
Because intake data stays on your device, you don't need to ask us to access, correct, or delete it — you can do all of that directly in the app.
For the anonymous data Firebase processes (§1.2), you can:
- Opt out of personalised advertising IDs — Android Settings → Google → Ads → Delete advertising ID or Opt out of Ads Personalisation. Firebase respects this.
- Reset your installation identifier — clear app data via Android Settings → Apps → Water Intake → Storage → Clear storage.
- Stop all collection — uninstall the app.
If you are in the EU, UK, India (DPDP Act), or California (CCPA), you also have the right to ask us:
- Whether we hold personal data about you
- For a copy of that data
- To delete it
- To object to processing
Because we don't link Firebase data to your identity, fulfilling most of these requests means we don't have anything to send you — but we'll respond within 30 days either way. Email contact@ackplus.com with "Water Intake — DSAR" in the subject.
8. Security
- On-device data lives in the app's private storage, which Android restricts to the app itself.
- All network calls to Firebase are over HTTPS / TLS 1.2+.
- Crash reports are scrubbed of personally-identifiable strings before upload.
- We do not store any credentials, payment information, or government identifiers in the app.
We do not currently support encryption of on-device data with a user passphrase. If hydration data is sensitive for you, we recommend Android device encryption (default since Android 7).
9. International transfers
Firebase processes data in Google data centres which may be located outside India / the EU / the UK. Google's standard contractual clauses and adequacy decisions cover these transfers. See the Google Cloud privacy resources for details.
10. Changes to this policy
If we change what we collect, how we use it, or who we share it with, we'll update this page and bump the "Last updated" date at the top. For material changes, the next app update's release notes will call it out.
11. Not medical advice
Water Intake is a habit tracker, not a medical device. The default 2.4 L daily goal is a generic adult starting point — your real hydration needs depend on your weight, activity, climate, and conditions. If you have a doctor-prescribed hydration target (kidney disease, pregnancy, athletic training, etc.), follow their guidance, not the app's defaults.
12. Contact
- Email:contact@ackplus.com (subject: "Water Intake")
- Website:www.ackplus.com
We aim to respond to privacy questions within 7 days, and to data-rights requests within 30 days.