Privacy Policy
This page explains personal data collection, use, sharing, storage and privacy requests connected with your 2g bet account, device activity and local payment references.
LEGAL REFERENCE
Privacy Policy for your account
2g bet keeps this Privacy Policy close to your account flow, so you can see what data we collect, why we use it, and how Pakistan payment records...
Account dataDevice checksJazzCash contextRaast records
How we handle your data
This Privacy Policy explains how 2g bet collects and uses data when you create an account, enter the lobby, contact us, or use local rails where local law permits. We collect details you provide, technical signals from your device, session activity, and transaction references linked with JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We use that data to keep access stable, process account
requests, verify payout steps, answer privacy questions, detect misuse, and meet legal duties that apply in supported regions. We do not sell your personal data. If we use service partners, we share only what they need to perform the requested task under account-security controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Checks behind this policy
We write this Privacy Policy from the way our account systems actually work. The same checks used for sign-in, wallet records, support messages and payout verification shape the wording here, so the...
Account data mapping
We map each data field to a purpose, such as account access, identity checks, payment reference matching or support handling, before we describe it in this Privacy Policy.
Payment record separation
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are treated as transaction records, not chat content or marketing preference data, which keeps handling clearer.
Access control
Only assigned staff can view account records needed for support, verification or security work. Wider access is restricted through role controls and logged system activity.
Device signal use
We use device and session signals to protect sign-ins, spot unusual access, maintain lobby stability and respond to account disputes raised by you.
Partner checks
When service partners help with hosting, messaging or payment processing, we limit shared data to the task and expect matching privacy and security controls.
Policy refresh
We check this Privacy Policy when account flows, support paths or local payment handling changes, then update page wording so you can read the current position.
PAGE ALIGNMENT
Privacy stays aligned across pages
This Privacy Policy works with our account terms, cookie wording and promo rules without replacing them. Each page answers a different privacy question: what we collect, how tracking works, how account rules...
Cookie wording
Cookie wording focuses on browser storage, session tools, preference signals and measurement tags. It supports this Privacy Policy but stays limited to tracking technologies.
Account terms
Account terms explain rules for access, verification, balances and acceptable account use. Privacy points inside those terms should be read with this page.
Promo rules
Promo rules may mention eligibility checks, account status and reward records. Those checks still rely on the data handling described in this Privacy Policy.
Support records
Support pages explain how to contact us, while this Privacy Policy explains how we store, use and protect the messages you send.
Payment pages
Payment pages describe transaction steps, while this page explains the privacy handling for wallet references, confirmation data and payout verification records.
Security notices
Security notices may describe alerts or access checks. This Privacy Policy explains the personal data used to investigate those alerts and protect your account.
Visible privacy cues on page
We make privacy signals easy to spot before you enter personal details. Labels, short prompts and account-area reminders explain why a field is needed, how a...
Clear form labels
Account forms explain why we ask for contact details, identity fields or wallet references, so you can understand the privacy purpose before sending the entry.
Session alerts
If a login looks unusual, we may show an alert or request an account check. The related device signals are used for account protection.
Wallet reference prompts
When JazzCash, Easypaisa, SadaPay, NayaPay or Raast records are needed, prompts ask for reference details rather than unrelated personal documents.
Profile controls
Your account area lets you check key profile details and contact support for corrections when a name, phone number or email entry is wrong.
Message reminders
Support screens remind you not to send unnecessary screenshots or private wallet content. We ask for limited proof only when a request requires it.
Policy link placement
Privacy links appear near account and help areas, not only in the footer, so you can return to this page while making account decisions.
Privacy questions before you join
We collect account details you enter, contact data, device signals, session activity, support messages and payment references connected with JazzCash, Easypaisa, SadaPay, NayaPay or Raast.
We use your data to create and manage your account, keep access stable, match transaction references, answer support questions, verify payout requests and detect misuse.
No. We do not sell your personal data. When partners help with hosting, messaging or payment processing, we share only the data needed for that task.
Wallet references are stored as transaction records and linked to your account activity. We use them to confirm requests, resolve disputes and support payment checks.
Yes. Contact us if account details are wrong or outdated. We may verify that the request is yours before changing personal data on your profile.
We keep records for as long as needed for account support, legal duties, transaction checks, security investigations and dispute handling, then reduce or remove data where practical.