Sababa

Privacy Policy

This policy explains what information Sababa handles when you use the app and website.

1. About Sababa

Sababa is operated by Uziel64. Privacy questions can be sent to [email protected].

2. Information you provide

Sababa accounts use an email address and password. You may provide a display name or nickname. The app assigns a persistent account identifier to each account. Sababa currently supports email-and-password sign-in; phone-number sign-in, guest accounts, profile-photo collection and other sign-in providers are not part of the account options described here.

3. Conversations and groups

Messages are stored remotely in Cloud Firestore under the relevant group conversation. A message can include its text, sender identifier, sender name, timestamp, and topic identifier. Group records include membership and group information; invitation records include an invite code, group identifier, creator, and an expiry timestamp.

Sababa does not currently provide end-to-end encryption. Network connections are protected using encryption provided by Firebase and HTTPS, but this is not the same as end-to-end encryption.

4. Topics, activities and plans

Topics and activities are stored in Cloud Firestore. Activity records can include a title, category, free-text area, creator and creator name, linked topic, proposed time options, participant interest identifiers, vote identifiers, and a creation timestamp. The current client computes leading times from vote counts rather than storing a separate winner.

5. Media and files

Where file sharing is supported by the installed Sababa version, images and PDF files may be uploaded to Firebase Storage. Associated message information can include a file link, name, type, size, caption and expiry time. Sababa does not promise that image metadata such as EXIF data is removed before upload.

6. Presence and technical information

When signed in to an active group, the app can publish a presence record to Firebase Realtime Database containing a display name and last-seen time. Presence is group-scoped, excludes the current user from the displayed participant summary, uses a five-minute stale threshold, and is removed through the configured disconnect lifecycle.

When push notifications are supported, Firebase Cloud Messaging registration tokens may be stored with the account's device records. Sababa does not use advertising SDKs, and no intentional collection of advertising IDs is part of the service. Firebase and platform services may process technical information as part of operating their services; their own terms and policies describe their provider-side practices.

7. Notifications

Where push notifications are supported, Firebase Cloud Messaging may receive notification data such as a sender name, group name, a shortened message or file notice, and identifiers needed to route the notification to the relevant group and message. Delivery depends on the installed version, device settings and network conditions.

8. Location and contacts

Sababa does not request device location permissions. An activity area such as “Dahab” is user-entered text, not device-location collection. Sababa does not use contacts permission, an address-book picker, phone-number matching or uploaded contact data.

9. How information is used

Information is used to authenticate users, show account and display-name information, provide group conversations, route topic and activity content, synchronize presence, deliver supported notifications, operate file sharing where enabled, and maintain the service.

10. Service providers and sharing

Sababa uses Firebase Authentication, Cloud Firestore, Firebase Realtime Database, Firebase Storage, Firebase Cloud Functions and, where notifications are supported, Firebase Cloud Messaging. These services process information on Sababa’s behalf to provide the app. Messages, group information, activity data, display names and presence may be visible to members of the relevant Sababa group as part of the product. Selling personal information is not part of the service, and Sababa does not use advertising SDKs.

11. Security

Sababa relies on Firebase Authentication and Firebase security controls, with encrypted network transport supplied by Firebase/HTTPS. No implementation can guarantee absolute security, and Sababa does not claim end-to-end encryption.

12. Retention and deletion

Sababa does not publish a general retention period for accounts, messages, groups, activities or presence. Invite records expire after seven days. Where file sharing is supported, uploaded chat files may have a short expiry and may be removed by an automated cleanup process.

Individual messages can be deleted from a conversation. “Hide my messages” is a local per-user preference and is not server-side deletion. Sababa does not currently provide automatic account deletion or a complete account-data erasure workflow inside the app.

13. Account and data deletion

There is currently no in-app “Delete account” control. Signing out does not delete an account or server-side data. To request deletion without reopening the app, email [email protected] or use the instructions on Delete account.

14. Children

Sababa is intended for people aged 13 and older. Sababa is not directed to children under 13. We do not claim COPPA certification or compliance. If you are under the applicable age to agree to these terms, do not use the service.

15. International processing

Firebase services may process information in countries other than your own. Sababa has not verified a specific data-residency commitment for this service.

16. Changes and contact

We may update this policy as Sababa develops. The effective date will be updated when a substantive change is published. For privacy questions, contact [email protected]. For deletion requests, contact [email protected].

Effective date: 18 September 2026