Toba · Your information & choices

Privacy Policy

How Toba handles your information, including sensitive profile and verification data, and the choices available to you.

Last updated October 21, 2026

Who we are

Toba is operated by Jalebi LLC. In this notice, “Toba,” “we” and “us” mean Jalebi LLC. This notice covers tobadating.com, the Toba app and support interactions.

Toba is preparing for its public iPhone release. The app practices below apply when you use the relevant features, including during limited testing. Visiting this website does not create a dating profile or start a verification check.

For privacy questions, access requests or deletion requests, contact support@tobadating.com. You can also follow our account deletion instructions.

Information you provide

We collect information you enter or share to create and use your account. Some information is needed to operate the service; other profile answers are optional.

  • Account information: phone number, account identifier, first and last name, date of birth, gender and dating preferences. Your birthday is used to determine your age and eligibility.
  • Profile information: photographs, occupation, height, biography, prompt answers and the interests, family preferences, education, hometown, countries, lifestyle choices and relationship intentions you choose to add.
  • Faith-related information: your choice to join a Coptic dating community and any church-attendance or faith-related answers you provide. These can reveal your religious beliefs.
  • Interactions: likes, dislikes, matches, messages, photos shared in conversations, reactions and blocks.
  • Team updates: when you open a Toba team notification or team conversation, or follow a link in a team update, we record the action and time against your account. We use these records to measure how our updates are received and used.
  • Safety and support: reports, descriptions of a problem, reply email, relevant account details, correspondence and technical information you choose to include.

Sensitive profile information

Religion, dating preferences and some profile answers can be sensitive. Toba asks for your agreement to process and share the religious information you provide for introductions. Optional faith-related answers can be edited or removed. Membership in Toba can itself suggest a connection to the Coptic community.

Your profile is intended to be seen by other eligible Toba members. Shared-priority highlights compare answers members have chosen, such as relationship intentions or church attendance. They do not establish compatibility or verify a person’s beliefs.

You can withdraw consent for religious-data processing by deleting your account, or contact support@tobadating.com about your choices. Do not include another person’s private or sensitive information without permission.

Phone sign-in

Google Firebase provides phone authentication. The phone number you supply is sent to and stored by Google for authentication and for spam and abuse prevention across Google services. The sign-in flow may also use device, IP and app-verification signals. Your carrier’s messaging or data charges may apply.

Never share a one-time sign-in code with another member or with someone claiming to be support. See Google’s Firebase privacy information.

Location and technical information

With your device permission, the app obtains location coordinates to find nearby profiles and derive a city, region and country. Google’s geocoding service processes location for this purpose. Member-facing profiles show location labels and distance rather than the stored latitude and longitude.

We process app and device information, IP addresses, notification tokens, service logs and error information to deliver the service, maintain security and investigate failures. Support diagnostics may include your device model, operating system, app version, account reference, current screen and recent error.

You can manage camera, photos, location and notification access in your iPhone settings. Withholding a permission can prevent the feature that needs it from working. The current Toba configuration disables Firebase Analytics collection and Bugsnag crash-reporting initialization.

Disabling Firebase Analytics does not disable the technical data used by other Firebase services. Those services can send SDK and app-version, operating-system and device information to Google for service operation, diagnostics and understanding SDK adoption.

Live-selfie and facial verification

Before the live-selfie check, Toba asks for your explicit consent to Toba and Didit processing your selfie and facial biometric data. Didit checks liveness and compares facial characteristics with your main profile photo to help detect impersonation. Fraud checks can also compare faces with prior verification or blocklist records and evaluate device, IP and related risk signals.

This involves selfie images, liveness video or frames, facial measurements or templates, comparison results and verification records. Toba stores verification results and copies of relevant selfie images or liveness video in its own restricted cloud storage for verification and safety review. The current photo-check workflow does not request a government identity document and has audio recording disabled.

Authorized reviewers may inspect relevant evidence when a check needs review or a safety issue is investigated. Your verification selfie and video are not part of your member-facing profile. The visible verification status does not prove legal identity, age, religion, background, character or safety.

The current app requires a completed photo check before discovery and messaging. You may decline to start it, but those features will remain unavailable. Contact us to withdraw consent or request deletion of verification data. See how verification works.

We have opted the Didit organization used by Toba out of future model-training use of its verification data. This does not turn off operational verification or fraud checks and does not undo prior model updates. Didit explains its processing in its Verification Privacy Notice.

How we use information

  • Create, authenticate and maintain accounts; check eligibility; display profiles and find introductions based on preferences, location and information members share.
  • Deliver likes, matches, conversations and service notifications.
  • Measure the reach and use of Toba team updates, and understand subscription activity through purchase history and subscription analytics.
  • Check photo authenticity, reduce fraud, investigate reports and enforce community rules.
  • Review profile text, photos and messages for harmful content. The release being prepared includes automated content checks using Google Cloud Natural Language and Vision, alongside human review. Automated results can be wrong; contact support to request review of a restriction.
  • Confirm subscriptions, provide paid features, restore eligible purchases and respond to billing questions.
  • Answer support and privacy requests, diagnose problems, secure the service and meet applicable legal obligations.

Who receives information

Other members receive the profile information and messages you share through Toba. Staff with authorized support or moderation access may review relevant account information, messages, reports and verification evidence. Conversations are not end-to-end encrypted; relevant content can be processed for delivery and safety review.

Toba uses separate app infrastructure from Jalebi’s dating community. A Toba account is not automatically published as a Jalebi dating profile. Jalebi LLC operates both services and may use shared personnel and service providers.

We may disclose information when legally required, to respond to valid legal process, or where necessary and lawful to protect people’s safety or the service. We do not publish support reports as member content.

  • Google Firebase and Google Cloud: authentication, databases, media storage, backend processing, notifications, geocoding and content-safety services.
  • Didit: live-selfie verification, facial comparison and related fraud prevention.
  • Apple: app distribution, Apple Account billing, purchase management and any TestFlight services you use.
  • RevenueCat: subscription transactions, entitlement processing and subscription analytics linked to a Toba account identifier. Toba’s current configuration does not send optional profile attributes such as name, phone number, age or gender to RevenueCat.
  • Website, network and email providers: hosting, domain services, routing and delivery of communications. Website services include Vercel hosting and Cloudflare domain services; support messages are handled through email providers.

Subscriptions and payment information

If you purchase Toba Plus through the App Store, Apple handles payment. Toba and RevenueCat process purchase history, product, transaction and subscription status to grant or remove access, handle billing questions and provide subscription analytics. Toba does not receive your full payment-card details from Apple.

Deleting a Toba account does not cancel an Apple subscription or erase Apple’s transaction records. Cancel separately in your Apple Account. Apple and RevenueCat describe their own processing in their privacy notices: Apple and RevenueCat.

Retention and deletion

Account and profile information remains stored while your account exists, unless it is removed or corrected. Account deletion hides the profile, closes conversations and starts cleanup of account, media, conversation, report and verification data. Cleanup continues in the background after sign-out and includes deletion requests to relevant providers.

Verification records from Toba’s existing beta are held in Didit with no automatic fixed expiry. The separate Didit setup prepared for Toba’s public release currently uses Didit’s default retention period of two years. In that production setup, facial biometric templates are deleted with the associated verification session rather than kept after its deletion. The retention periods for public release are still under review; these are the settings currently in place, and we will update this notice if they change.

Toba has not set an automatic time-based expiry for the selfie images and liveness evidence it stores in its own cloud storage. These copies can remain until deletion is carried out. Didit’s retention setting does not delete copies stored separately by Toba.

Didit’s Biometric Data Retention and Destruction Policy separately applies purpose-based and applicable statutory limits to the biometric data it holds, including where a general verification-record setting has no fixed expiry.

Deletion can require additional work where provider records, safety restrictions, support emails or unresolved processing remain. We retain the limited request information needed to complete and verify that work. Relevant records may also need to be retained to meet a legal obligation or resolve a specific dispute. Provider backups and legal records may not disappear at the same time as the active account.

We cannot erase copies another member independently saved outside the service. Removing the app, signing out or cancelling a subscription does not delete your Toba account. See Delete your account for the steps and limitations.

This website

This website does not have a sign-up form, advertising pixels or optional analytics. It does not store your interactions with the example conversation prompt. Fonts and images are served as website assets.

Hosting and network providers can process technical request information, such as an IP address, browser information, requested page and request time, to deliver and protect the site. Opening an email link uses your own email application; your message is sent only when you send it. External links take you to services with their own policies.

See the Vercel Privacy Notice and Cloudflare Privacy Policy for their processing.

International processing and security

Toba’s backend uses cloud infrastructure in the United States. Service providers and support systems may process information in other countries, where privacy laws can differ from those where you live. Information may be accessible to authorities under applicable law.

We use access controls and other technical and organizational measures intended to protect information. No internet service can guarantee that unauthorized access or data loss will never occur. Protect your device and sign-in codes, and avoid sending sensitive information through support email.

Your choices and requests

You can edit available profile fields, manage device permissions, block or report members, manage an Apple subscription and request account deletion. Depending on the law that applies, you may also have rights to access or obtain a copy of information, correct it, request deletion, withdraw consent, object to or limit certain uses, and complain to a privacy regulator.

Email support@tobadating.com with the subject “Toba privacy request.” We may need to verify your connection to the account before disclosing or changing information. Do not send passwords, sign-in codes, payment-card details or identity documents in your first email. If you disagree with our response, you can ask us to review it.

Adults only and policy updates

Toba is for people aged 18 and older. Children must not create an account. If you believe a person under 18 is using Toba, report the account in the app or contact support. Our Child Safety Standards explain prohibited conduct and reporting.

We will update this notice when our practices change and update the date above. Where required, we will provide additional notice or obtain consent before a materially different use of your information.