Hydration Tracker privacy policy Effective September 8, 2026 Hydration Tracker helps you record water intake from a connected tracker and manual entries. This policy covers the app, its account service, and connected trackers. Data we process Your account uses an email address and an authentication credential managed by Firebase Authentication. We store water/refill amounts and times, tracker identifiers, device and firmware versions, pairing and sync status, and your settings. These data support account access, hydration history, device ownership, and synchronization. The phone keeps a local cache for offline use. A tracker keeps a bounded offline measurement log. Bluetooth and Wi-Fi Bluetooth pairs your phone with the tracker and transfers readings and setup commands. Your Wi-Fi name and password are sent securely to the tracker for direct synchronization. The account service does not receive your Wi-Fi password. Pairing and device-upload credentials control access to your tracker. Removing a tracker or deleting an account revokes its cloud access; physically reset the tracker to erase its local network configuration and measurements before transfer. Optional Health export If you enable export, we write water amount and time to Apple Health or Health Connect using the system permission you grant. We do not read your Health records. Export begins from the time you opt in for that account on that installation. You can turn off export in Settings or revoke permission in the system. Export retries may happen when the phone is unlocked or connectivity returns. Choose one Android phone for export if your phones use separate Health Connect stores. Stable record identifiers reduce duplicate writes within the same Health store. No advertising or analytics collection This build disables Firebase Analytics collection and advertising identifiers. We do not sell your data or use Health data for advertising. Operational cloud logs can include request metadata such as IP addresses, timestamps, and error information for security and reliability. We avoid logging hydration payloads and credentials. Storage, processors, and retention Firebase/Google Cloud process account and synchronized data to provide the service. Cloud hydration data are stored in the configured US region. Data remain until you delete entries, history, or your account. Local health records and pairing credentials are excluded from device cloud backups. Operational logs follow the configured service retention. Encrypted recovery backups may retain deleted data for up to seven days; recovery procedures must reapply account deletions before restored data can be used. Account-deletion cleanup starts immediately; interrupted jobs retry automatically. A minimal deletion receipt expires after seven days once cleanup completes. Your choices and deletion Settings provides history deletion and account deletion. Account deletion removes authentication, hydration history, device registrations and upload credentials. You can also sign in on our external account-deletion page to delete your account without installing the app. The account page is linked below. Other phones may retain an offline cache until they reconnect. Data you exported to Apple Health or Health Connect must be deleted separately in that app. Trackers require a physical factory reset to erase offline data. Security and limitations We use encrypted network connections, authenticated device access, protected local credential storage, and account access rules. No service can guarantee uninterrupted delivery or perfect measurement accuracy. Hydration estimates are for personal tracking and are not a medical diagnosis or treatment recommendation. Contact and policy updates Use the support contact listed with Hydration Tracker in your app store listing. Changes to this policy will appear here with a new effective date. The account-deletion option remains available in Settings and on the external deletion page.