Effective date: October 6, 2026. Operator: Sparkish. Contact: alarmcrew.support@gmail.com.
This policy covers AquaTick for Android and its Wear OS companion, package com.benghak.aquatick. The iOS policy covers the separate iPhone and Apple Watch app. AquaTick is a personal hydration log, not a medical service.
Records on your device
You can log water without creating an account. Hydration amounts, dates and times, goals, reminders, cup presets, selected photos, and appearance settings are stored in the app’s private Android storage. Photo selection uses Android’s picker. Photo processing happens on the device; original cup photos are not uploaded to AquaTick’s cloud backup. Android automatic app-data backup is disabled.
Widgets and progress notifications display your current-day progress according to your settings. Anyone who can see your home or lock screen may see this information. An exported JSON backup is a separate file saved through Android’s file picker; you control its storage and sharing.
The optional subject-cutout tool uses Google ML Kit on the device. Input photos and segmentation results are not sent to Google by ML Kit. Its SDK can contact Google for model or compatibility updates and send API performance and usage metrics. See ML Kit’s privacy information.
Optional Google sign-in and cloud backup
When Android cloud sync is available and you choose to enable it, Firebase Authentication processes your Google sign-in, account email, and Firebase user identifier. We use that identifier to isolate your records and the email for account support. No Google Drive access is requested. An active Android Pro entitlement is required to synchronize; an existing account can be deleted without buying Pro.
Cloud backup sends the selected account’s hydration records, amounts, dates and times, time zone, record source, cup and drink metadata, cancellation state, and sync metadata to Firebase Firestore. This can include records imported from Health Connect when you also enable that feature. Existing local records are included when you choose to move them into the cloud account. Cup photo files, goals, reminder settings, and cup presets are not part of this cloud backup. Android cloud sync does not transfer records to or from iOS.
Firestore authorization uses the authenticated account and server-verified Android subscription status. Firebase App Check and Play Integrity may process app and device attestation information to protect the service. Cloud availability depends on the installed release and service configuration.
Health Connect and Wear OS
Health Connect is optional. After you enable it and grant Android’s hydration read and write permissions, AquaTick imports current-day hydration records into your log and writes AquaTick entries to Health Connect. Cancelling an AquaTick entry can remove its corresponding AquaTick-written Health Connect record. AquaTick does not request other health categories or use Health Connect data for advertising, sale, or credit, employment, or insurance decisions.
You can revoke permissions and manage Health Connect records in Android’s Health Connect settings. Revoking access, deleting the app, or deleting a cloud account does not automatically erase records already stored in Health Connect or copies in an exported backup.
A paired Wear OS app receives today’s progress, quick-log and undo commands, cup information, and photo thumbnails through Google Play services Data Layer. Depending on connectivity, transfer can use Bluetooth or Google’s relay service. A companion cache can remain on the watch; manage the watch app’s data separately. See Google’s Data Layer documentation.
Purchases and advertising
Google Play processes payment. RevenueCat processes app customer identifiers, purchase and subscription information, and device and app information to provide Pro access and restoration. AquaTick does not receive your payment card number. Google Play subscriptions and Android Pro are separate from iOS purchases. Google Play and RevenueCat may retain transaction information under their own policies and legal obligations.
Free use may include Google Mobile Ads, including banners and a rewarded ad you choose to watch to unlock a cat skin. UMP obtains applicable advertising choices; ad requests follow its request-allowed status. Google’s SDK can process IP-based approximate location, device and advertising identifiers, app interactions, and diagnostics for advertising, fraud prevention, and measurement. Valid Android Pro access removes in-app ads. Advertising data is separate from AquaTick’s hydration log; health records, cup photos, and account emails are not supplied as advertising targeting fields. See Google Mobile Ads data disclosures and Google’s Privacy Policy.
Product analytics and crash diagnostics
Release builds use Firebase Analytics and Amplitude to understand app actions and improve the product. Custom events contain the action, screen context, outcome, and limited categorical settings. A successful cup creation includes its configured capacity in mL, capacity label, and drink type; this describes the cup, not a drink you consumed. Fourteen categorical profile values describe subscription, onboarding, notification, cloud, unit, and cup-count states. We do not put actual consumed amounts, goals, hydration dates, custom cup names, photos, searches, email, Firebase account IDs, or RevenueCat purchase IDs in custom analytics events or profiles.
A random identifier stored privately on this Android installation is shared with Firebase Analytics and Amplitude. Amplitude also uses a separate random device identifier. These identifiers do not come from your Google account or health records and can change after app-data deletion or uninstalling. The active Amplitude user identifier and Firebase app-instance identifier can also be provided to RevenueCat for purchase attribution. Provider-generated app, device, operating system, language, interaction-time, and session information can be processed.
Amplitude’s automatic collection is limited to sessions. Advertising ID, App Set ID, carrier, coordinates, IP-based location collection, automatic screen, element, and network tracking, Session Replay, and SDK diagnostic reporting are disabled in Amplitude. Its project uses the US region. Firebase Analytics has its own automatically collected technical information; these Amplitude restrictions do not describe every other SDK. Crashlytics independently processes crash traces, installation identifiers, and device/app information to diagnose faults. See Firebase’s privacy information and Amplitude’s Privacy Notice.
Retention, deletion, and your choices
Local data remains until you remove it through the app or Android’s app-data controls. Cloud records and cancellation metadata remain while the account exists, until you delete the account or request deletion. Cancelling a hydration entry alone can leave cancellation metadata used to synchronize your devices.
Use the in-app cloud-account deletion control or the account and data deletion page. Verified server deletion removes the Firebase Authentication user, Firestore profile, hydration records, and account-linked sync and RevenueCat metadata. In-app deletion also clears that account’s cache and pending sync work on the current phone. An external request cannot remotely clear every phone, watch, exported file, Health Connect record, or subscription.
To prevent stale work from recreating a deleted account, a server-only marker retains the Firebase identifier, deletion time, expiry time, and blocked sync generation. It contains no email, hydration records, or RevenueCat customer identifier. Its configured retention is 90 days, followed by daily cleanup, normally about 90–91 days. If account or orphaned-data deletion fails, the marker remains until deletion and verified cleanup succeed. Third-party backup, security-log, analytics, and purchase retention follows the providers’ policies; cloud deletion is not a claim that those separate records disappear immediately.
We do not sell personal data. You can request access, correction, or deletion by contacting support; we verify ownership before disclosing or deleting account data. Do not email passwords, sign-in tokens, payment credentials, or health records unless needed for a specifically agreed support request. Support processes your email and voluntarily supplied details to answer your request. Service providers can process information outside your country. Internet services use encrypted transport, but no service can promise perfect security.
Updates and contact
We update this policy when the Android app’s data practices change and revise the effective date. For privacy questions or requests, contact alarmcrew.support@gmail.com. Read the Android terms or visit Android support.