Privacy page and account terms
The terms page sets what your account may do; this page sets what we do with your details. Where both mention verification, terms carry the rule and this page carries the record.
This page sets out how cineb bet collects, uses and stores the details tied to your account. You will find what we hold, why we hold it, who...
This policy describes how we treat personal details when you use cineb bet where local law permits. Because privacy rules differ between supported regions, some parts of this page may apply to you differently than to someone signing in from another province or country. Where a jurisdiction sets stricter standards for storage, consent or deletion, we follow that standard for your account.
Where a rule is narrower, the lines below explain what we still do. We hold the same core commitments everywhere: we collect only what an account needs, we tell you which records we keep, and we name the payment rails that pass settlement details back to us. Nothing here removes a right your region already gives you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your data should never sit unanswered. Our support desk handles privacy requests through live chat in the lobby, email sent from your registered address, and a phone line during Pakistan business hours. Tell us which detail you want changed, corrected or removed, and we confirm the outcome in writing.
Open your account, sign in, and the chat widget sits in the corner of every page. Privacy requests raised there reach a person within minutes during Pakistan daytime.
Write from the email tied to your account so we match the request without asking for extra proof. Attach nothing sensitive; our reply comes back in writing for you.
Call between 9am and 9pm Pakistan time, seven days a week. A team member confirms which records we hold, explains a consent question, or logs a correction while you wait.
Confidence here comes from things you can check, not from slogans. Our privacy copy names the records we store, the third parties that process payments, and the retention...
We name the rails that move money for Pakistan accounts: JazzCash, Easypaisa, SadaPay, NayaPay and Raast. A reference reaches the...
Every category of record carries a shelf life. Sign-in logs, payout confirmations and chat threads each follow a fixed period...
We write for readers, not lawyers. Headings name the topic, sentences stay short, and any term we introduce is defined...
You sign in with your own credentials and sessions expire on a timer. An unfamiliar device gets an extra check...
If a stored detail is wrong, tell support and we correct or annotate it. You can ask for a copy...
Privacy standards shift between regions. Where your area sets a stricter bar for consent, storage or deletion, we apply that...
Our policy pages are written to sit together. The privacy page covers how we handle personal details, the terms page covers account rules, and the payout pages cover settlement. Where two pages...
The terms page sets what your account may do; this page sets what we do with your details. Where both mention verification, terms carry the rule and this page carries the record.
Payout pages explain settlement timing and confirmations. Here we explain why a transaction reference reaches our processor, how long the confirmation line sits on your profile, and when it clears.
Support pages list channels and hours. This page adds the data side: what a chat thread stores, which agent comments stay attached to your account, and how a closed request is kept.
Headings that describe shelf life use identical wording across pages, so a period quoted here matches the period printed beside your payout history on file.
Consent statements appear on the pages that collect details, and their meaning stays the same everywhere. When wording changes, the portal shows the updated sentence before you continue.
Every policy page points to the same support channels and the same signed-in ticket queue, so a request opened from any page lands in one place rather than two.
Each policy page carries a revision date. When we change wording the date moves and the portal flags the updated paragraph, so you can see what shifted since you last agreed.
Everything you need to judge our data handling sits on one screen. The scope comes first, regional carve-outs follow in the middle, and request routes close...
The opening paragraph states which cineb bet services this policy covers and which details fall inside it. You see that boundary before you scroll, so you know if the rest applies to you.
A short block explains what you agree to when you open an account and how to change your mind later. Its wording matches the consent screen you tap during sign-up.
Rows pair record types with the period we keep each one. Sign-in history, payout confirmations and chat threads each appear as their own line, readable without legal training.
The partners that touch account data appear as labelled chips, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so every party in a settlement is visible at a glance.
The closing block names the channels for a data request, the hours they run in Pakistan, and what we need from you to match a ticket to your account.
A dated stamp in the footer records when the wording last changed. Compare it with your own records if you want to see exactly what moved between two readings.