Account terms
Terms describe your account duties; this policy explains our data duties. The same account identifiers appear in both so privacy rights and account records stay connected.
LEGAL REFERENCE
Privacy Policy for Your Account
Live Baccarat, Aviator, cricket markets and slot rooms all create account signals, and this Privacy Policy explains how 2v game handles those details when you open an account...
Pakistan account dataPayment contextSecurity checksYour privacy choices
How We Handle Your Data
This Privacy Policy explains the data we collect, why we collect it, and how we use it when you access 2v game where local law permits. We collect account details you provide, device and browser signals, login records, transaction references, fraud-prevention checks, and messages you send to us. Payment context from JazzCash, Easypaisa, SadaPay and Raast is used to match your funding
or withdrawal request with your account record; we do not ask you to share wallet PINs with us. We keep data only for account operation, security, dispute handling, legal record needs, and service improvement tied to privacy-safe measurement. If we need extra consent for a specific use, we ask before using your data that way.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY CONTACTS
Contact Us About Privacy Rights
If you want to ask about this Privacy Policy, update account details, request access to your stored data, or question a transaction record, contact us through the channels inside your account area. We may ask for identity checks before sharing or changing data because privacy requests must protect the account owner, not expose the account to another person.
Team online
Privacy email
Send a privacy request from the email linked to your 2v game account. Include your account ID, the data question, and any payment reference you want us to check.
Live chat handoff
Chat can collect your privacy question and pass it to the data team. We avoid sharing full records in open chat until account checks are complete.
Account message
Use the message area after login when your request involves withdrawals, device access, or profile edits. This links the privacy request to your verified session.
POLICY CARE
How We Keep Policy Text Reliable
We write this Privacy Policy from our own operating flow, not as detached legal filler. The wording is checked against account creation, login security, payment matching, withdrawal verification, live table session records...
Process matching
Policy wording is tied to real account steps: profile creation, login checks, wallet references, withdrawal review, and chat contact. We avoid promises that our systems do not support.
Payment separation
JazzCash, Easypaisa, SadaPay and Raast references are used to confirm transaction ownership. Wallet passwords and PINs stay with your provider, not inside our account records.
Access logging
We record logins, device signals and security events so suspicious access can be investigated. Those records help us protect your account and answer privacy questions accurately.
Retention checks
Data is kept for account operation, dispute handling, security needs and lawful record periods. When data no longer serves those purposes, we remove or reduce it where possible.
Local wording
We use Pakistan payment names and supported-region wording so the policy matches your account journey. If access is limited by location, the privacy meaning stays clear.
Team access
Only teams with a work reason can view account records. Support, payments and security see the portions needed for their task, with internal checks on access.
PAGE ALIGNMENT
Same Privacy Logic Across Pages
Our Privacy Policy connects with the rest of the 2v game legal pages, so the same account terms, cookie rules, security wording and payment references do not conflict. This section explains how...
Cookie policy
Cookie wording covers browser storage and session signals. This Privacy Policy explains how those signals connect with login security, device checks and page measurement.
Security text
Security wording explains account protection steps, while this policy explains the data behind those steps. Login records, device clues and alerts are handled together.
Payment records
Payment pages mention transaction references. This policy explains why those references are stored, who may view them, and how they support account ownership checks.
Support records
Support pages show contact channels; this policy covers the data created inside those chats and messages. We keep request history to answer privacy questions.
Promo wording
Promo pages may require account checks. This policy explains the privacy side, including profile eligibility data, fraud-prevention signals and retention of related account records.
Region wording
Where local law permits, access wording may appear across pages. This policy keeps the privacy meaning clear when location, device or payment checks are used.
PAGE SIGNALS
Visible Privacy Markers On Page
This page is designed so privacy details are easy to check before you share account data. We show short markers for collection, use, security, retention, choices and contact...
Data categories
The policy separates profile data, device signals, transaction references, session...
Purpose labels
Each data group is linked to a clear purpose, such...
Choice points
Where a privacy choice is available, we state the path...
Contact block
The contact area tells you which channel to use for...
Retention marker
Retention wording explains why some records stay longer than a...
Region marker
Supported-region wording is included because location can affect access and...
Questions About Your Privacy Policy
We collect the details needed to create and run your account, including profile fields, login records, device signals, transaction references, session activity and support messages you send to us.
Payment references help us match JazzCash, Easypaisa, SadaPay or Raast activity with the correct account. They support withdrawal checks, dispute handling and fraud-prevention work without requiring wallet PINs.
Yes. Contact us from the email or logged-in account linked to your profile. We verify ownership before sharing data so another person cannot receive your account records.
Retention depends on the record type and purpose. Security events, payment references and dispute records may stay longer than basic session data where account protection or legal records require it.
We may share limited data with payment, security, hosting, analytics or support service partners when needed to run your account. They receive only the data needed for their task.
Device signals help us recognise account access patterns and detect unusual activity. We use them for security, session handling and fraud-prevention checks, not to expose your private device content.