AquaStreak: Water Reminder  Privacy Policy

Effective date: 2026-06-18

1. Scope

This Privacy Policy describes how AquaStreak: Water Reminder ("AquaStreak", "we", "our", or "us") collects, uses, stores, and discloses information when you use the AquaStreak mobile application.

This policy describes the current behavior of the AquaStreak mobile app and the third-party processors used to operate account, subscription, analytics, ads, diagnostics, and reminder features.

The current production Play Store build uses Supabase for authentication and cloud sync, RevenueCat and Google Play for subscriptions, Firebase Analytics where analytics is enabled in the build, Sentry for crash reporting, Google AdMob for advertising on free-user surfaces, native Google Sign-In on Android for authentication, Expo local notifications for on-device reminders, and Open-Meteo for weather-based hydration recommendations.

2. Summary

AquaStreak is a wellness and habit-tracking app, not a medical or emergency service. The app can work locally on-device, but some features use third-party services:

• Supabase for account authentication, profile data, and premium cloud hydration sync.

• RevenueCat and the relevant app store for subscriptions and entitlement status.

• Firebase Analytics for product analytics events and user properties when analytics is enabled in the build.

• Sentry for crash reporting and operational diagnostics.

• Google AdMob for advertising on free-user surfaces.

• Native Google Sign-In on Android for authentication.

• Expo local notifications for on-device reminders.

• Open-Meteo weather endpoints to calculate optional weather-based hydration goal adjustments.

We do not sell your personal information. The app requests non-personalized ads only in code, but Google AdMob may still process device and advertising identifiers for ad delivery, fraud prevention, frequency capping, and reporting.

3. Information We Collect And Process

The table below describes the data categories actually present in the current app implementation.

4. Data We Do Not Intentionally Collect

Based on the current implementation, AquaStreak does not intentionally collect these categories as stored profile fields or analytics identifiers directly from the app code

• Contacts

• Photos or videos

• Audio recordings

• Precise location as a stored account/profile attribute or analytics field

• SMS or call logs

• Remote push tokens for a cloud push-notification service

• Payment card numbers or bank account information

Subscriptions are handled by the platform billing provider and RevenueCat. We do not receive your full payment card details.

For smart hydration recommendations, the app may request device location permission so it can fetch current weather conditions. Coordinates are used for the weather request only, are not persisted in the local weather cache, and are not sent to Firebase Analytics or Sentry.

5. How We Use Your Information

We use information to:

• create and maintain your account

• authenticate you by native Google Sign-In on Android

• store and display your profile and hydration preferences

• track daily hydration entries, streaks, and statistics

• calculate optional weather-based hydration goal recommendations and allow users to apply or dismiss them

• sync hydration history to the cloud for eligible signed-in premium users

• process subscriptions, restore purchases, and enforce premium access

• schedule and manage local hydration reminders

• measure product usage and feature performance through Firebase Analytics

• detect, diagnose, and fix crashes or operational issues through Sentry

• show non-personalized ads on free-user surfaces through AdMob

• comply with legal obligations and protect the security of the app and our users

6. When And How Data Leaves Your Device

6.1 Supabase

The app sends account and profile information to Supabase for authentication and account storage. If you are signed in and premium cloud sync is enabled for your account, the app also sends hydration day records to Supabase. In the current schema, those records can include:

• account email and user ID through authentication and profile tables

• optional display name

• daily hydration goal

• daily consumed total

• individual water-entry amounts and timestamps

6.2 RevenueCat and the app store

The app uses RevenueCat to fetch offerings, determine entitlement status, and restore or validate purchases. The relevant app store handles billing. AquaStreak does not process your full payment card information directly.

6.3 Firebase Analytics

When analytics is enabled for the build, the app sends product analytics events and user properties to Firebase Analytics. The app intentionally uses coarse fields such as bucketed water amounts, subscription tier, route names, message categories, onboarding steps, package types, and simple status flags rather than raw free-text user content. 

6.4 Sentry

The app uses Sentry for crash reporting and diagnostics. Sentry is configured to disable default personally identifiable information and to sanitize event payloads before sending them. Sensitive keys such as email, access tokens, session tokens, and similar values are redacted by app code before events are sent.

6.5 AdMob

The free version of the app displays banner and interstitial ads using Google AdMob. The current implementation requests non-personalized ads only. Even with non-personalized ad requests, Google may process device and advertising identifiers, app interaction metadata, and related diagnostic information for ad delivery, fraud prevention, reporting, and frequency management.

6.6 Local notifications

The app schedules hydration reminders as local notifications on your device. The current implementation does not register a remote push token with a push-notification backend. If you receive or open a local hydration reminder, the app may log a Firebase Analytics event containing only the reminder message category and whether the reminder was received in the foreground or opened from the notification tray.

6.7 Open-Meteo weather requests

When smart hydration goals are enabled, the app requests weather data from Open-Meteo over HTTPS to calculate a recommended hydration goal adjustment. Depending on your configuration, the request can be based on device location permission or a manually entered fallback city. The app stores only weather-derived recommendation state needed for the feature (such as weather tiers and notification deduplication keys), does not persist precise coordinates in the local weather cache, and does not send coordinates to analytics or diagnostics providers.

7. Sharing And Disclosure

We may disclose information in these circumstances:

• to service providers that help us operate the app, including Supabase, RevenueCat, Google services used for Analytics, Sign-In, AdMob, Sentry, and Open-Meteo for weather recommendations

• when required by law, regulation, legal process, or governmental request

• to protect the rights, safety, security, or integrity of AquaStreak, our users, or others

• as part of a merger, financing, acquisition, reorganization, or sale of assets, subject to applicable law

We do not sell your personal information.

8. Retention

We retain data for as long as needed to provide the app and comply with legal obligations.

• Local on-device data remains until you remove it in the app, sign out, clear app storage, or uninstall the app.

• Account, profile, and synced hydration records remain in our backend until they are deleted through account deletion or a verified support request.

• Verified backend deletion requests are currently handled through manual operator tooling and may generate a limited internal audit record that tracks the request outcome, operator identity, completion time, and provider follow-up status without storing the deleted hydration payloads or raw auth secrets.

• Subscription, analytics, ad, and diagnostic providers may retain data according to their own retention schedules and contractual terms.

Because AquaStreak does not provide a dedicated in-app account-deletion screen, deletion requests should be sent to namadaapps@gmail.com.

9. Your Choices

You can:

• choose whether to create an account or use account-linked features

• use Google sign-in on the Play Store build

• manage notification permissions at the device level

• change reminder settings, quiet hours, and hydration goals inside the app

• enable or disable Smart Hydration, apply or dismiss weather-based goal suggestions, and set a manual fallback city when location permission is denied

• manage or cancel subscriptions through the relevant app store account settings

• edit or delete hydration entries locally in the app

• request deletion of backend account data by contacting namadaapps@gmail.com

If you do not want Firebase Analytics or Sentry telemetry to be used, the practical control is not to use a version of AquaStreak where those services are enabled, because the app does not currently expose an in-app analytics toggle.

10. Security

We use reasonable technical and organizational measures designed to protect information handled by the app. Examples in the current implementation include:

• secure session persistence using SecureStore on supported device builds

• authenticated backend access through Supabase with Row Level Security requirements

• limited client-writable profile fields

• event sanitization and redaction before Sentry transmission

• avoidance of raw personal data in Firebase Analytics custom events

• HTTPS-only weather API usage and no persisted coordinate storage in the local weather cache

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Children

AquaStreak is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact namadaapps@gmail.com so we can investigate and take appropriate action.

12. International Processing

Our service providers may process data in countries other than the one where you live. By using the app, you understand that your information may be processed in other jurisdictions subject to applicable law and the safeguards used by those providers.

13. Changes To This Policy

We may update this Privacy Policy from time to time. When we do, we will update the effective date at the top of this policy. Material changes may also be communicated through the app, store listing, or another appropriate channel.

14. Contact

If you have questions, privacy requests, or deletion requests, contact:

• Email: namadaapps@gmail.com