Privacy Policy

2.1 Information you provide

Onboarding and personalization data. During onboarding, and whenever you later edit it in Settings, you provide:

• Age (the app supports ages 13–100)
• Sex (male, female, or “prefer not to say”)
• Body weight
• Activity level, exercise frequency, and optionally typical workout duration
• Typical environment (e.g. cool, hot, humid)
• Your motivation for using the app, your estimated current intake, how often and when you tend to forget to drink, your usual drinking pattern, and your commitment level
• Your unit preference (metric or imperial)

This information is used to calculate a recommended starting hydration goal and to personalize wording inside the app. The calculation is a fixed, deterministic formula that runs on your device. No artificial intelligence or external service is involved, and the result is a wellness recommendation — not medical advice (see Terms of Use §11).

Hydration data. Each time you log a drink, the app records the amount (in millilitres internally), the exact timestamp, the local calendar date, and which container preset you used, if any.

Containers. Names and volumes of the containers you create.

Reminders. The reminder times you choose, whether each is enabled, whether reminders are on overall, and your quiet-hours settings.

Account information (only if you create an account). If you sign in, we receive from your chosen sign-in method:

• Your email address
• Your display name and profile photo URL, when your provider supplies them (Google and Sign in with Apple; email/password sign-up does not)
• A Firebase user ID that identifies your account

Your password is never stored or seen by us — email/password sign-in is handled entirely by Firebase Authentication, which stores credentials on Google’s infrastructure.

2.2 Information generated by the app

• Streak and consistency data — current streak, best streak, and the last date you met your goal.
• Daily, weekly, and monthly aggregates — computed on your device from the entries you logged. We never estimate or synthesize intake you did not log.
• Subscription status — whether an entitlement is active, whether it is a free trial, and its expiry date (see §6).
• App preferences and state — appearance mode (light/dark/system), whether onboarding is complete, whether the notification permission prompt has been shown, and whether an account has ever signed in on this device.

2.3 Information collected automatically

Drink Time does not include any analytics, attribution, advertising, or crash-reporting SDK. Firebase Analytics is not part of the app and is explicitly disabled in the app’s Firebase configuration. We do not collect an advertising identifier (IDFA/AAID), we do not present an App Tracking Transparency prompt, and we do not track you across other companies’ apps or websites.

The app reads your device time zone so reminders fire at the correct local time. This value stays on the device.

The following are collected automatically by third parties as part of providing their service, not by us directly:

• Firebase Authentication records sign-in metadata such as account creation time, last sign-in time, and the IP address of a sign-in request.
• RevenueCat, Apple, and Google process purchase and device information when you buy or restore a subscription (see §6).

2.4 Health and fitness data

Drink Time records hydration information you enter, along with the personal attributes listed in §2.1 that feed the goal calculation. Depending on where you live, some of this may be treated as health-related data.

Drink Time does not connect to Apple Health, Google Fit, HealthKit, or any other health platform, and does not read any data from them.

2.5 What we do not collect

We do not request or collect: location, camera or microphone access, photos, contacts, calendars, health-platform data, browsing history, or the contents of any other app on your device.

4.1 On your device (always)

The app stores locally:

• Your water entries, containers, and reminders — in a local SQLite database
• Your profile, streak, reminder settings, appearance, subscription status, and app flags — in the platform’s standard app preferences storage
• Your blocked-apps list and app-blocking settings, including (on Android) the package name, display name, and icon of each app you selected

Local data is protected by your device’s own operating-system protections and device encryption. The app does not add a separate layer of encryption on top of the local database, and it does not lock the app behind a passcode.

Local data is removed when you uninstall the app, when you delete your account in the app, or (for account-scoped data) when you sign out.

4.2 In the cloud (only if you sign in)

If you create an account or sign in, the app mirrors data to Cloud Firestore under a document keyed to your Firebase user ID. Specifically:

Synced to the cloud:

• Your email address and display name (as provided by your sign-in method)
• Your full personalization profile and daily goal
• Your streak state
• Your reminder settings, and each reminder time
• Every water entry (amount, timestamp, date, container link)
• Your containers (name, volume, order)

Not synced to the cloud — these stay on the device only:

• Your blocked-apps list and app-blocking settings
• Appearance mode and other device-level preferences
• Your cached subscription status

Firestore access is restricted by server-side security rules so that a signed-in user can read and write only their own documents. Firebase transmits data over encrypted connections (TLS) and Google encrypts data at rest on its infrastructure.

Synchronization runs in both directions while you are signed in: changes made on the device are pushed up, and changes present in the cloud are pulled down. When you sign in on a device that already has local data and your account also has cloud data, the app asks you whether to restore the cloud copy or keep the data on this device. Choosing “Restore” replaces the local entries, containers, and reminders with the cloud copy; choosing “Keep this device” overwrites the cloud copy with the local one.

If cloud synchronization fails — for example, you are offline — the app continues to work normally from local storage and retries later. Because the sync layer is best-effort, we cannot guarantee that every change reaches the cloud.

App blocking and your privacy

If you enable app blocking:

• On Android, an Accessibility Service checks the package name of the app currently in the foreground against the list you selected, entirely on the device. The service is configured so that it cannot read window content. Nothing it observes is stored beyond your own selections, and nothing is transmitted anywhere.
• On iOS, your selection is made in Apple’s own picker and stored as an opaque token that Apple does not let the app decode. The app can only ever learn how many items you selected — never which apps they are.
• Confirmations you make on the blocking screen (“I drank water”) are recorded locally and turned into a normal water entry the next time the app opens.

We never see, receive, or transmit which apps you block, how often you open them, or anything that happens inside them.

Deleting individual data

You can delete any individual water entry from the daily timeline, and you can delete containers and reminders at any time. When you are signed in, those deletions are also propagated to the cloud copy.

Signing out

Signing out clears your account-scoped data from the device — your profile, streak, reminder settings, and cached subscription status. Your cloud data is untouched and is available again the next time you sign in.

Deleting your account

Settings → Account → Delete account performs, in this order:

1. Stops cloud synchronization.
2. Deletes all of your Firestore data — every water entry, container, and reminder, plus your user document containing your email, display name, profile, streak, and reminder settings.
3. Detaches your account from RevenueCat.
4. Deletes your Firebase Authentication account.
5. Revokes the app’s Google OAuth grant, where Google was your sign-in method.
6. Clears your hydration data, profile, streak, reminder settings, and subscription state from the device, and returns the app to a fresh state.

For security, Firebase may require you to re-authenticate first; the app will prompt you and then retry.

Important limitations, stated plainly:

• If you signed in with Apple, deleting your account here stops Drink Time from using your Apple ID, but only you can remove the app from your Apple ID, in Settings → your name → Sign-In & Security → Sign in with Apple. The app explains this on the deletion screen.
• Deleting your account does not cancel your subscription and does not produce a refund. Subscriptions must be cancelled through your App Store or Google Play account (see the Terms of Use).
• Purchase records held by RevenueCat, Apple, and Google are not deleted by this flow.
• Deletion of cloud data is carried out on a best-effort basis. If a network or server error interrupts it, some records may remain; contact us at hello@zappsco.com and we will complete the deletion.
• Residual copies may persist for a limited period in our providers’ routine backups before being overwritten in the ordinary course.

You may also request deletion by writing to hello@zappsco.com.