SipplyRecords on your device
You can use Sipply without an account. Water amounts and timestamps, daily goals and goal history, language/theme, reminder and notification preferences are stored in the app’s local storage. Progress and streaks are calculated from those entries.
Guest records are not uploaded as a Firebase account backup. Usage measurement may still operate in guest mode. Android may include local app data in device backups or device transfers, depending on your device settings. This is separate from Sipply account backup.
Accounts and cloud backup
If you create an account, Firebase Authentication processes your email (when provided), display name, provider account identifiers and authentication data. Google and Facebook also operate their own sign-in services when you use them. Sipply does not receive your social account password. Email/password credentials are sent securely to Firebase Authentication and are not included in water backups or Analytics events.
Automatic cloud backup is on by default for accounts and can be disabled in My account. Email/password accounts must verify their email before backing up. Google and Facebook use the same backup flow. Google Cloud Firestore stores your water entries and timestamps, daily goal and goal history, entry count, backup revision and update time under your account so you can restore on another device.
Turning backup off does not delete an existing cloud backup. Deleting your account removes it. Signing out is not account deletion.
Health Connect
Connecting is optional. With your permission, Sipply writes the amount and time of existing and new entries on this device to Android Health Connect. Edits and deletions are synced while sharing is enabled. Sipply only requests permission to write hydration data; it does not read health records from other apps.
Health Connect sharing does not enable cloud backup. The records backed up to Firestore are your original Sipply entries, not data read from Health Connect. You control which other apps may read exported entries through Health Connect permissions. Disabling sharing or deleting your Sipply account does not automatically remove previous exports; manage or delete them in Health Connect.
Health data is not used for advertising, ad profiling, sale or credit assessment.
Usage measurement and technical data
Google Analytics for Firebase processes app/screen opens, sessions, app version, device/OS information and resettable identifiers such as an app instance ID. Service providers also receive IP addresses with network requests. These measurements help us understand usage and problems.
Custom events include adding water, completing a daily goal, sign-in method and outcome, reminder/permission changes, finishing the guide and opening the coffee link. This includes events indicating use of the water tracking feature. Custom events do not contain your email, name, account UID, password, water amounts, goal amount or water entry history. The Firebase account ID is not set as the Analytics user ID.
Advertising ID collection and personalized advertising signals are disabled. Sipply does not display ads. Facebook Login sends account and technical connection information to Meta to provide your chosen sign-in flow. Automatic app event logging and advertiser ID collection are disabled in the app’s Facebook SDK. These settings do not remove account and security communication needed for sign-in.
Service providers and security
Google Firebase provides authentication and optional cloud backup; Google Analytics provides usage measurement; Google and Meta provide your chosen social sign-in. These services may process data outside Türkiye. We do not sell health records.
App-to-cloud traffic uses HTTPS. Firestore rules restrict backup access to the account owner. Local data is kept in Android app storage; you manage your device lock and device backups. Compressed cloud backups do not mean we provide app-specific end-to-end encryption.
The coffee link opens Buy Me a Coffee. That website and its payment provider process payment information; Sipply does not receive your card details. A click does not mean a donation was made. Linked services have their own privacy terms.
Retention and deletion
Local records remain until you delete the relevant profile or app data. Uninstalling the app does not delete the cloud account. Android device backups are managed separately in device backup settings. Account deletion removes your login account and cloud backup from active services. Provider backups and security logs follow the providers’ retention/deletion processes.
A deleted account cannot be accessed again. Creating a new account with the same email or social sign-in later does not restore the deleted records. Web deletion cannot remotely clear other devices’ local storage or Health Connect data. Remove inaccessible account profiles through Android app data settings.
Analytics uses separate app instance identifiers; deleting your account does not automatically delete those measurements. Our Analytics property is configured to retain event data for 2 months and user data for 14 months. New user activity resets the user-data retention period. Aggregate reports may remain longer. Send Analytics-related requests to support@sipply.app.
After deletion, a marker tied to the random Firebase account identifier is retained to prevent old sessions from recreating the cloud backup. It only indicates deletion status and contains no email, name, password, water entries or goals. This minimal security marker is retained without automatic expiry.
Your choices, requests and contact
You can separately disable cloud backup and Health Connect sharing, change Android notification permission and choose to delete your account. For information, correction and deletion requests under applicable law, contact support@sipply.app.
See account and data deletion steps. Updated policies and their effective dates will be published here.
Developer and contact
Sipply is developed by Emre Bilsel. For support and privacy questions, contact support@sipply.app. Official website: sipply.app.