Brilliant Hydration Privacy Policy

Last updated: July 30, 2026

Brilliant Hydration is designed to work without an account or developer-operated server.

Controller and contact

Brilliant Hydration is developed and provided by Lando Stock. For privacy questions or requests, contact lando.stock@gmail.com.

Data processed

The app processes daily water totals, daily targets, calendar dates, change timestamps, and local sync versions needed to prevent duplicate or stale restores. It does not collect names, email addresses, advertising identifiers, precise location, contacts, or unrelated health information.

Local storage and backup

The Pebble app stores hydration data and settings on the watch. The Pebble phone runtime and optional Android companion may keep up to 31 daily totals in private app storage so the watch can be restored after reinstallation. Depending on the user’s Android backup settings, Android may include the companion’s private database in a cloud backup only when encrypted backup is available. Local device-to-device transfer may also include this data.

Brilliant Hydration does not operate a cloud account, analytics service, advertising service, or remote data server.

This local processing is necessary to provide the tracking, history, correction, backup, and restore functions requested by the user. The developer does not receive this local hydration data.

Update checks

The Android companion checks the public Brilliant Hydration repository on GitHub for a newer release at most once every 24 hours while the app is used. Users can also start a check manually. The request contains the installed app version and standard network information required for an HTTPS connection. It does not contain hydration data, watch data, device identifiers, or account information.

Update checks are sent directly to GitHub, not to a Brilliant Hydration server, and are subject to GitHub’s Privacy Statement. GitHub receives the network request as an independent service provider and may process standard connection data, including outside the European Economic Area, as described in that statement.

The legal basis for the update request, where the GDPR applies, is the developer’s legitimate interest in informing users about security fixes and compatible releases (Article 6(1)(f) GDPR). The companion checks on launch and when the user requests a manual check. It does not run a background update service while the app is closed.

Health Connect

Health Connect integration is optional and disabled until the user enables it. The Android companion requests only hydration read and write permissions.

When enabled, Brilliant Hydration writes the daily water total to Health Connect. For recovery, it reads only hydration records created by Brilliant Hydration itself. It does not read hydration from other apps and does not request any other health category.

Health Connect stores and shares data according to the user’s Health Connect settings and permissions. Turning off synchronization in Brilliant Hydration stops future writes. Existing records remain under the user’s control in Health Connect, where they can be viewed or deleted.

Where GDPR consent requirements apply to this optional on-device health-data processing, enabling the feature and granting Android’s hydration permission provides consent under Articles 6(1)(a) and 9(2)(a) GDPR. Consent can be withdrawn at any time without affecting earlier lawful processing.

Brilliant Hydration does not sell personal data. It does not send hydration data to the developer or to advertising or analytics companies. If the user enables Health Connect, Android makes the data available only according to the permissions the user grants to health apps.

Retention and deletion

The 31-day limit applies only to the local Pebble recovery history in the companion. It does not delete older records from Health Connect. Records written to Health Connect remain available according to the user’s Health Connect retention and auto-delete settings. Brilliant Hydration only removes one of its Health Connect records when the corresponding daily amount is deliberately corrected to zero.

Removing the Pebble app clears its watch storage. Removing the Android companion clears its local app storage, subject to Android’s system backup and restore behavior. The developer does not retain update-check connection data; GitHub applies its own retention rules. Health Connect records can be deleted from Health Connect’s data management screen.

User choices

Users can:

use the Pebble app without Health Connect
pause Health Connect synchronization in the companion
revoke Health Connect permissions in Android settings
inspect or delete synchronized records in Health Connect
remove either app to clear its local storage

Rights

Where the GDPR applies, users may request access, correction, deletion, restriction, portability, or object to processing. Because the developer does not receive or hold hydration records, most such requests are fulfilled directly on the user’s watch, phone, Android backup settings, or Health Connect. Requests concerning GitHub’s own processing should also be directed to GitHub.

Users may lodge a complaint with the data protection authority responsible for their place of residence, work, or the alleged infringement. There is no automated decision-making or profiling.

Source code and public releases are available at github.com/landostock/brilliant-hydration.