Privacy Policy for Your z3 game Account
z3 game keeps this privacy policy close to the account flow: we collect the details needed to create your account, protect access, process Pakistani transaction records and answer...
How We Handle Your Privacy
Our privacy posture is built for Pakistan access where local law permits. When you create an account, we record identity fields you provide, login events, device signals, wallet references and support messages. JazzCash, Easypaisa, SadaPay and Raast details are kept as transaction records so we can match status, check withdrawals and answer disputes without asking you to repeat sensitive data in chat.
We do not sell your account record. We share limited data with service partners that host security tools, payment routing, customer support and fraud checks, and we keep those partners tied to the same purpose. If the law, a regulator or a payment rail asks for records, we respond only to the request scope and log what was supplied.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Routes for Privacy Requests
If you want to ask about your privacy rights, start with the channel linked to your account. We may need to confirm your phone, email or recent account activity before changing, exporting or deleting data. That check protects you from another person trying to control your account record.
Privacy desk
Ask us to explain what account data we hold, correct a field, or route a deletion request. Include your registered phone or email so we can match the account safely.
Chat transfer
Our chat team can pass a privacy query to a supervisor, but we will not ask for wallet PINs or one-time codes. Share only the details needed for the request.
Email trail
For access, correction or erasure requests, email lets us confirm identity and keep a written trail. We reply with the steps taken or the reason a record must remain.
How We Keep This Policy Reliable
We maintain this privacy policy as an operating document, not a static footer link. Our account, support, security and payment teams check it when product flows change. That...
Plain language
We write the policy in practical Pakistani English, with separate wording for account data, device logs and transaction records, so...
Local context
Where payment data is mentioned, we name Pakistani rails such as JazzCash, Easypaisa, SadaPay and Raast, because those records affect...
Security input
Our security checks cover login alerts, device changes and suspicious access patterns. The policy explains these signals so you understand...
Retention checks
We keep data only for account service, legal, security and transaction reasons. When a record is no longer needed, we...
Staff access
Support and operations staff see only the account fields needed for their task. Sensitive wallet details are masked where possible...
Change control
When we alter the policy, we update the date, adjust affected sections and keep older internal copies. Material changes are...
How Privacy Matches Other Pages
This policy works beside our account terms, cookie notice and transaction rules. Each page has a separate job, but the privacy wording stays consistent across them. When you...
| Account terms | The account terms describe your access duties; this policy explains the data behind those duties, including identity fields, login history and security checks linked to your profile. |
|---|---|
| Cookie notice | Our cookie notice explains browser storage in more detail, while this policy sets out why device and session signals are used for security, analytics and account continuity. |
| Transaction rules | Where transaction pages mention verification, this policy explains the personal data used for matching wallet references, checking payout requests and answering account-specific payment questions. |
| Promo board | If an offer requires account eligibility checks, this policy explains how we use your profile status, region and activity record without turning that data into a separate sales list. |
| Support pages | Support pages tell you how to reach us; this policy explains what chat logs, email threads and attachments may be stored when you ask for account help. |
| Security prompts | Login warnings and verification prompts are short on the screen, so this policy gives the fuller reason for collecting device signals and recent account activity. |
| Policy dates | Dates across legal pages help you see which wording is current. When privacy language changes, we align connected pages so the same data use is not described differently. |
Visible Markers Across This Policy
We designed the privacy page so you can scan it before opening an account and return to it later when a question comes up. The layout...
Scope chips
Short chips near the opening show the account and transaction areas covered by the policy, helping you spot whether the section relates to identity, wallet references or support.
Request routes
Contact cards list the privacy paths we accept, so you can choose chat for routing or email for access, correction and erasure requests that need a written trail.
Data categories
Section headings separate account details, device signals, transaction records and support messages. This makes the policy easier to scan when you are checking one data type.
Retention cues
Retention wording is placed beside the reason for keeping data, so you can see the link between security, legal needs, transaction checks and account support.
Local wording
Pakistan-specific wording appears where it matters, including supported regions and named rails. We avoid vague labels when a local record type needs a clear privacy explanation.
Update marker
The policy date and change wording show when privacy text has been adjusted. If a material change affects your account data, we flag it in the account flow.