Consistent Data Definitions
The term 'personal data' means the same thing across this policy and our terms of service — no hidden re-definitions between documents.
At on777bet, your personal data belongs to you — and this policy sets out exactly how we collect it, why we use it, and how we keep it...
We collect the information you provide when you open an account — your name, contact details, and identity verification documents — alongside transaction records linked to payment methods you choose, such as JazzCash, Easypaisa, SadaPay, or Raast. We also collect device and session data automatically to keep your account secure and to detect unusual access patterns. This data is processed to fulfil
your account contract with us, to meet financial record-keeping obligations in supported regions, and to maintain the security of your account. We do not sell your personal data to third parties. Where local law permits, we may share data with licensed payment processors and identity verification services strictly to complete transactions you initiate.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We have built this privacy framework around the practical realities of operating a platform for Pakistan, including the local payment rails, account verification flows, and data handling that...
All personal data on your account is stored behind AES-256 encryption at rest. Access is limited to authenticated internal systems...
When you transact via JazzCash, Easypaisa, SadaPay, or Raast, your payment credentials never touch our servers directly — they pass...
Documents you submit for identity verification are held only as long as required for compliance in supported regions, then deleted...
We do not and will not sell your account data, browsing behaviour, or transaction history to advertisers, data brokers, or...
If this policy changes in a way that affects your rights, we notify you via the email on your account...
This policy is reviewed on a scheduled basis by our compliance team against the data handling requirements applicable to supported...
Our legal framework is designed so that each policy page — privacy, cookies, terms, and account rules — uses the same underlying data definitions and retention rules. This keeps your rights consistent...
The term 'personal data' means the same thing across this policy and our terms of service — no hidden re-definitions between documents.
Retention periods stated here align exactly with the account closure and data-deletion rules described in our terms, so there is no gap between what each document promises.
The privacy team contact details on this page are the same entry point referenced in our cookie policy and our terms — one team handles all data queries.
How JazzCash, Easypaisa, SadaPay, and Raast transaction data is handled is described consistently here and in our payment terms, with no conflicting instructions between the two.
What happens to your data when you close your account is described in both this policy and the account terms using the same timeline and the same deletion scope.
This privacy policy and our cookie policy share the same consent framework — withdrawing consent in one place applies across both documents simultaneously.
The advance-notice period we commit to before policy changes applies equally to this privacy policy, the cookie policy, and the terms — the same notice standard across all three.
This privacy policy is structured so you can find what matters to you quickly — whether that is how we collect data, your rights over that...
Sets out every category of data we collect, from account registration fields through to automatic device data, with a plain explanation of the legal basis we rely on for each category.
Explains specifically how transaction data flowing through local Pakistani payment rails is processed, tokenised, and retained — separate from your general account profile data.
Lists your right to access, correct, port, or request deletion of your data, with the specific steps to exercise each right and the timeframe within which we will respond.
Names the categories of third parties — payment processors, identity verifiers, infrastructure providers — that may handle your data, and the contractual limits we place on each.
Describes the technical and organisational measures we use to protect your account data, including encryption standards, access controls, and our internal breach response procedure.
States clearly how long each category of data is kept, when it is deleted, and what happens to any residual records after your account is closed in supported regions.