Sipling Privacy Policy

Effective date: September 29, 2026

Sipling is operated by Nathaniel Daswani. Contact contact@nathanieldaswani.com about privacy or support.

Information used by Sipling

Sipling creates a guest account with Firebase Authentication. We use its account identifier to save your progress and connect related app features. You can choose a display name and a name for your Sipling.

We store drink records, timestamps, daily hydration goals and progress, selected preferences, lagoon decorations, outfits, Treasure Tides season progress and rewards, friend relationships, invitations, and social interactions such as Good Vibes, gifts, challenges, blocks, and reports. This information supports the features you use and helps prevent invalid or duplicate rewards and abusive interactions.

The goal questionnaire's detailed answers are stored in the app's device preferences in this version. The selected daily goal is saved with your account. Sipling does not read or write HealthKit data.

Service providers and purchases

Sipling uses Google Firebase Authentication, Cloud Firestore, Cloud Functions, App Check/App Attest, and Firebase Hosting. These services process data needed to operate and protect the app. Firebase SDKs also declare collection of technical diagnostic information. Service requests and backend logs may contain account or request identifiers needed for operation and troubleshooting.

Apple processes in-app purchases. Sipling checks purchase entitlements through StoreKit. When you claim a Plus-track Treasure Tides reward, the app sends Apple-signed app and transaction proof to our backend to confirm that Plus is active. Purchase verification information is associated with the reward request while it is processed and may remain in service records if processing does not complete. We use it to validate access and prevent duplicate or invalid rewards. We do not receive your payment-card details. Apple's purchase records and subscription management are separate from Sipling's guest account.

We also use RevenueCat for purchase validation, subscription support, and subscription analytics. Our server forwards verified Apple purchase notifications to RevenueCat, and imports available Apple purchase history. This can include product and transaction identifiers, purchase and expiration dates, trial status, renewals, cancellation and refund information, and price, currency and storefront information supplied by Apple. This reporting can operate for an existing purchase even if your installed app does not contain the RevenueCat SDK.

App versions with RevenueCat reporting enabled also synchronize Apple purchase records with RevenueCat using a randomly generated customer identifier. SDK requests can include technical information such as app and operating-system versions and network information. We do not send your Firebase guest-account identifier, profile name, hydration records, room, friend list, or advertising identifier to RevenueCat. A pseudonymous purchase identifier is not a guarantee of anonymity; it can link a purchase across renewals and restores. See RevenueCat's privacy policy for information about its processing.

Sharing with friends and your devices

Accepted friends can see the profile and progress used by shared features. Your sharing choices control access to your room, and social controls let you limit interactions or block someone. Information you send to another user may be visible to that recipient while it remains in the service.

The app shares a progress snapshot with its widgets and your paired Apple Watch. The Watch can temporarily queue drink logs until a connection is available. Hydration reminders are scheduled on your device.

Support messages

If you email us, we receive your email address and the information you choose to include so we can answer your request. Avoid including sensitive information that is not needed to explain the issue. Contact us if you want to request removal of support correspondence.

Advertising and tracking

This version does not contain advertising or a cross-app advertising tracking flow. We do not use your hydration data for advertising. RevenueCat is used to understand Sipling purchases and subscriptions, not to target advertisements.

Retention and deletion

Account data remains available to operate your guest account until removed through the app's deletion flow. You can request account deletion in Settings → Your data. An accepted request runs on the server even if your connection is interrupted.

The deletion process removes the guest authentication account and associated profiles, hydration records, preferences, inventory, Treasure Tides state and requests, social records and memberships from the active app database. Other users retain their own accounts and earned rewards. A minimal account-identifier deletion marker and a separate, unguessable completion receipt remain so delayed events cannot recreate deleted data and the app can confirm completion. They do not contain your name, drinks, or room content.

RevenueCat purchase records are separate from your Firebase guest account and are not automatically erased by that guest-account deletion. They are retained for subscription support and reporting unless removed. To request access to or deletion of those records, email contact@nathanieldaswani.com with the subject “Sipling purchase data request.” Include the subscription support reference shown in Settings → Your data if available, or the Apple order reference from your receipt. Do not send your Apple password or full payment-card details. We may request limited purchase information to verify that the records belong to you before removing them from RevenueCat. Future purchases, restores, or continuing Apple subscription events can create new purchase records.

Operational logs are separate from active app records. Our current Cloud Logging configuration retains default service logs for 30 days and required audit logs for 400 days. These records may outlast account deletion. Provider-controlled audit and operational records are not erased by the in-app account deletion request.

Deleting your guest account or a RevenueCat customer record does not cancel an Apple subscription or erase Apple's billing records. You can manage subscriptions through your Apple account. Purchase reporting is held in RevenueCat in addition to Firebase; we do not keep separate backups of your hydration or guest-profile data outside Firebase.

Your choices and contact

You can change your name, goal, reminders, and social preferences in the app, and correct or remove drink entries through history. You can request account deletion without first cancelling a subscription. There is currently no email/password sign-in or supported guest-progress recovery on a new installation.

For questions or privacy requests, contact contact@nathanieldaswani.com. This policy will be updated when the app's data practices change.