Privacy Policy for your 4qqq account
4qqq records the data needed to open your account, protect access, process JazzCash, Easypaisa, SadaPay and Raast requests, and keep your lobby history accurate where local law permits...
How our Privacy Policy applies
This Privacy Policy applies when you create or use a 4qqq account from supported regions in Pakistan, browse the lobby, speak with support, or ask us to process a transaction through a local rail. We collect only the details needed for account access, security checks, transaction tracing, support replies, and legal record keeping. That may include your name, mobile number, device data,
payment reference, session activity, and messages you send to us. Where local law permits, we use these records to keep your account available, detect unsafe access, confirm payments, answer privacy requests, and maintain accurate audit trails. We do not sell your personal data to data brokers.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy contact paths for you
Your privacy questions should reach the team that can check account records, not a generic mailbox. We keep separate paths for data access requests, correction requests, account security concerns, and payment-record questions. When you contact us, we may ask for a matching mobile number or transaction reference so we can confirm the account before sharing or changing anything.
Privacy inbox
Send account-data questions to our privacy inbox with your registered mobile number and a short request. We verify the account first, then reply with the record type we can access or amend.
Live chat handoff
If you start in live chat, ask for a privacy handoff. The chat team records your request, removes unrelated lobby comments, and moves the case to staff trained on personal-data handling.
Security escalation
For account access concerns, tell us what changed, when it happened, and which device was used. We compare session records before taking action on privacy or correction requests.
How we keep this policy accurate
We write this Privacy Policy from the way 4qqq actually operates: account creation, payment matching, live table sessions, sportsbook activity, device security, and support history. Our internal checks focus on whether each...
Operational input
Policy wording is checked against account, support, security, and payment workflows, so descriptions match the data we handle when you access casino tables, slots, sportsbook markets, or wallet records.
Local rail mapping
JazzCash, Easypaisa, SadaPay and Raast references are mapped as transaction records, not marketing labels. We explain why each reference may be stored and who can see it internally.
Access controls
Staff access to personal data is limited by role. Support can see what is needed for your case, while deeper security or transaction logs require a separate internal permission check.
Change tracking
When we change this Privacy Policy, we keep an internal change log showing what was adjusted, why it changed, and which account or payment process required clearer wording.
Retention checks
We keep records only for account operation, payment tracing, security, support, and legal needs. When a record is no longer required, it is removed or anonymised through scheduled routines.
Clear language
We avoid legal phrasing that hides the point. Each clause should tell you what we collect, why we use it, when we share it, and how you can ask about it.
How related pages stay aligned
The Privacy Policy does not sit alone. It connects with cookie settings, account terms, promotion rules, security messages, and payment pages, but it remains the place where we...
Policy layout you can scan
We designed this Privacy Policy so you can find the point quickly on mobile or laptop. The visible elements separate collection, use, sharing, storage, security, and...
Summary strip
A short summary appears near the start so you can see the main data uses before reading deeper clauses about account access, payment matching, security checks, and support history.
Local chips
Pakistan rail chips identify where payment references may appear in our records. They help you connect privacy wording with JazzCash, Easypaisa, SadaPay and Raast activity.
Purpose blocks
Each purpose block separates why data is collected from how long it may be kept. This avoids mixing account security, transaction tracing, support replies, and legal record duties.
Rights panel
The rights panel explains how you can ask to access, correct, or remove certain records. It also flags when legal retention may prevent immediate deletion.
Security labels
Security labels mark clauses about device checks, login records, access controls, and fraud detection. You can see which data protects access rather than serving another purpose.
Contact card
A contact card repeats the privacy route so you do not need to search the page. It tells you what to include before we release or change account data.