Privacy Policy

Glubbo Privacy Policy

Effective date: October 15, 2026. Operator: Vinclair Cloud. Contact: [email protected].

What Glubbo keeps on your phone

• Your water log: every drink you log (amount, drink type and time), your daily totals and your daily goal.
• What you enter during setup: weight, activity level, climate, wake-up time, bedtime and units.
• Your profile name and avatar, your reminder settings (style, how often, quiet hours), streaks, medals, tank level, the sea creatures you have met, your chosen buddy, tank theme and language.

All of this is kept in a database inside the app on your phone. If you do not sign in, it stays there: Glubbo has no server that receives a copy.

The home-screen widget shows today's water and can log a drink. It reads and writes the data on the same phone, and a drink logged from the widget is handled like any other drink.

If your phone's own backup (Google backup on Android, iCloud backup on iPhone) is turned on, the backup may include Glubbo's database from your phone, with your water log, goal and settings. Google or Apple keeps that backup under your account, and we cannot read it.

Signing in (optional)

You can use every feature of Glubbo without an account. On iPhone you can choose Continue with Apple or Continue with Google; on Android, Continue with Google. Sign-in runs on Firebase Authentication, a service of Google LLC. It receives your name, your email address and a sign-in ID from Google or Apple (and your profile photo if you use Google), and creates your Glubbo account. With Sign in with Apple you can hide your email, and Apple then gives a relay address instead.

While you are signed in, Glubbo saves a copy of your data in Cloud Firestore, a Google Cloud database, in the asia-southeast1 region (Singapore). The copy is linked to your account and holds your water log (amount, drink type, time and where in the app you logged it), your goal inputs (weight, activity level, climate, wake-up time and bedtime) and daily goals, your reminder settings, your profile name, avatar and buddy, your app settings (language, units, appearance, tank theme and sounds) and your progress (medals, streaks, the sea guidebook and your tank). It does not hold your email address.

The copy is there so your data comes back when you sign in on a new phone or after you reinstall Glubbo. The app's access rules let only your own signed-in account read or change it. Your account also links your Premium purchase to you, so you can restore it on another phone. Firebase keeps your sign-in session on your phone until you sign out.

Signing out first saves any drinks that are not in your account yet, then removes your Glubbo data from that phone. If some drinks cannot be saved (for example, because you are offline), Glubbo tells you before anything is removed. Your account and its copy stay, and your data comes back when you sign in again.

Reminders

Glubbo schedules its reminders on your phone, through your phone's notification system. There is no reminder server, and no notification token is sent to us or to anyone else. You can turn reminders off in Glubbo's Settings or in your phone's notification settings.

Health Connect (Android only)

On Android you can connect Glubbo to Health Connect in Settings. If you allow it, each drink you log in Glubbo (amount and time) is added to Health Connect on your phone. When you undo or delete a drink in Glubbo, the record Glubbo added is removed too. Glubbo asks only for permission to write water. It never reads anything from Health Connect.

Glubbo does not send Health Connect data to us or to anyone else, and it is never used for ads or analytics. You can remove Glubbo's access at any time in Health Connect's settings. Records Glubbo already added stay in Health Connect until you delete them there.

On iPhone, Glubbo does not connect to Apple Health. It does not read or write any Apple Health data.

Purchases

Premium is bought through the App Store or Google Play. They handle the payment, and we never see your card details. Our purchase service RevenueCat receives your purchase history and an app user ID (a random ID, or your Glubbo account ID if you are signed in), so the app knows whether Premium is active and can restore it.

Ads (free version only)

The free version shows one banner ad at the bottom of the main screens, served by Google AdMob. Premium users see no ads, and the ad service never starts for them.

To show and measure ads, Google receives your device's advertising ID (the Google advertising ID on Android; Apple's advertising ID on iPhone only if you allow tracking), your IP address (from which an approximate location is worked out), device and app information, and how you interact with the ads. The ad service does not receive your water log, your name or your email.

• Where the law requires consent (for example in the European Economic Area and the United Kingdom), Glubbo shows Google's consent form before any ad is requested. Google uses your choice to decide whether ads may be personalised. You can change your choice later in Settings > Ad privacy choices.
• On iPhone, Glubbo asks for tracking permission. If you say no, ads are not personalised, and the app works the same.
• Ads are limited to Google's "PG" content rating (suitable for general audiences with parental guidance).
• To limit ad tracking, delete or reset your advertising ID (Android: Settings > Google > Ads), turn off tracking (iPhone: Settings > Privacy & Security > Tracking), or buy Premium to remove ads.

Google's own use of this data is described in How Google uses information from sites or apps that use its services.

Analytics

Glubbo uses Google Firebase Analytics to count how the app is used, so we can see which screens help people and which confuse them. It records events such as:

• which screen was opened;
• that a drink was logged, with the drink type and where it was logged from (a quick button, the log sheet or the widget), never the amount;
• that the daily goal was reached, that setup was finished, that a reminder was opened, that a streak shield was used, and that a progress card was shared;
• steps in buying Premium: the Premium page opened, a purchase started, finished or failed, with the plan and the store price;
• whether you have Premium, the app language, and what each ad view earned.

Firebase also collects standard information by itself: an app-instance ID, device model, operating system, app version, country, session times and the advertising ID where your phone allows it. Analytics never receives your name, email, weight, drink amounts or daily goal. There is no switch inside Glubbo to turn analytics off; you can reset or delete your advertising ID in your phone's settings, or uninstall the app.

Crash reports

When Glubbo crashes, Google Firebase Crashlytics receives a crash report: where in the code the crash happened, device model, operating system version, app version, the time, and a random installation ID. We use it only to find and fix crashes. A crash report never includes your name, email or water log.

Sharing and exporting

• Share a progress card: Glubbo makes a picture of the card and opens your phone's share sheet. The picture goes only where you send it.
• Export Data (in Settings): Glubbo makes a file with every drink you logged, your daily totals and your settings (daily goal, wake-up time, bedtime, weight, activity level, climate, units, language and reminder settings). It opens your phone's share sheet, and the file goes only where you send it.
• If you email us, we receive what you write and your email address, and use them to answer you.

Companies that receive data

• Google (AdMob ads, Firebase Analytics, Firebase Crashlytics): see the Ads, Analytics and Crash reports sections above.
• Google (Firebase Authentication and Cloud Firestore), only if you sign in: your sign-in details and the copy of your data described in Signing in. Google handles this data for us as our service provider.
• RevenueCat: your purchase history and app user ID.
• Apple and Google as app stores and sign-in providers: payments, and Sign in with Apple or Google if you use it, under their own privacy policies.

We do not sell your personal data. Your water log goes to no one else: only to your own account copy in Cloud Firestore if you sign in, and to wherever you send an export yourself.

Children's privacy

Glubbo is made for teens and adults. It is not directed to children under 13, and we tell Google that the app is not directed to children. If you believe a child under 13 has given us personal information (for example by signing in), email us and we will delete it.

Data rights and deletion

• Signed in: open Settings, tap your profile, then Delete Account. Glubbo may ask you to sign in with Google or Apple once more to confirm it is you. It then deletes your data copy in Cloud Firestore, then your sign-in account at Firebase Authentication (your name, email and sign-in ID), then all Glubbo data on this phone, and cancels its reminders. On iPhone, if you signed in with Apple, Glubbo also ends its access to your Apple ID.
• Sign Out removes your Glubbo data from this phone and keeps your account and its copy, so you can sign in again later.
• Not signed in: open Settings, tap your profile, then Erase Local Data. This erases all Glubbo data on this phone and cancels its reminders.
• Uninstalling Glubbo removes the data it kept on your phone. It does not delete your account; use Delete Account for that.

The app cannot delete records that other companies keep: purchase records at Apple, Google and RevenueCat (needed for billing, tax and restoring Premium), analytics and crash data at Google, and copies in your phone's own backup. To ask for access, correction or deletion of any data we or our providers hold, use the Delete Account page or email [email protected] from the email you used with Glubbo. We will delete what we can, except records the law requires us to keep.

Data retention

Data on your phone stays until you delete it in the app, erase it, sign out or uninstall Glubbo. Your account and its data copy in Cloud Firestore stay until you delete your account; when you delete a drink in the app, its amount and time are removed from the copy too. Purchase records are kept as long as billing, tax and refund rules require. Analytics and crash data are kept by Google for the period set in its Firebase settings and then deleted.

Security

Data that Glubbo sends to Google and RevenueCat travels over encrypted connections (HTTPS). Google encrypts your data copy when it is stored, and the app's access rules let only your own signed-in account read or change it. The data on your phone is protected by your phone's lock. No system is perfectly secure, so please contact us if you believe your data has been exposed.

Changes

We may update this policy as Glubbo changes. Material updates will be reflected on this page with a new effective date.