LEGAL REFERENCE

Privacy Policy for your y99game account

y99game links privacy controls to your account flow, payment checks and support records, so you can see how your details are used before you open an account. This...

Account data usePakistan privacy contextPayment record handlingSupport access checks
Explore the Lobby Read FAQ
y99game Privacy Policy for your y99game account

How we handle account data

This Privacy Policy sets out how we collect and use your data when you access y99game from supported regions in Pakistan. We record the details you provide during account setup, login checks, payment matching and support contact. We also keep technical signals such as device type, browser data and security logs to protect account access and spot unusual activity. JazzCash, Easypaisa, SadaPay,

NayaPay and Raast references may appear in receipts or verification trails because they help us match a request to the correct account. We do not sell your personal details. We share data only with service partners who help run access checks, payment routing, fraud screening, support handling or legal requests where local law permits.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP ROUTES

Contact paths for privacy requests

Privacy requests need the right account match before we act. That protects you from someone else trying to view or change your stored details. Use the same phone number or email linked to your y99game account when you contact us, and include only the data needed for the request.

Team online

Privacy email

Email us from the address on your account and tell us which privacy point you want checked. We match the request to your profile before sharing or correcting stored account data.

Live chat handoff

Chat support can confirm what data is needed for account access, payment tracing or identity checks. For privacy changes, we move the case to the team that handles stored records.

Account centre

Inside your account centre, privacy prompts show where contact data, security settings and payment receipts sit. You can ask us to correct fields that no longer match your documents.

POLICY CHECKS

How our policy stays reliable

We write this Privacy Policy from the way y99game actually runs accounts in Pakistan. The policy is checked against account access, payment matching, support practice and security logging, so the wording reflects...

Account flow mapping

We map each privacy clause to a real account step, including joining, login, identity checks and password resets. That keeps the policy tied to actions you can recognise inside y99game.

Payment rail matching

Our privacy wording includes JazzCash, Easypaisa, SadaPay, NayaPay and Raast because those rails create receipts and trace references we may need when you raise a payment query.

Security log purpose

We explain security logs because they help us protect your account, detect suspicious access and investigate failed login attempts. The logs are kept only for operational and legal needs.

Support script alignment

Our support scripts use the same privacy wording as this page, so you get consistent answers when asking about stored data, correction requests or account access checks.

Regional wording

We use Pakistan-specific examples and include supported regions wording because privacy rights and access can depend on local law. We avoid claims that do not match our actual service setup.

Change tracking

When data handling changes, we adjust this policy and keep an internal change record. That helps our team answer why a privacy clause was added or amended.

Privacy wording across related pages

Your privacy rights should not change from one page to another. We keep account, cookie, terms and contact pages aligned with this Privacy Policy, so the same data...

Account terms
Our account terms refer back to this Privacy Policy when they mention identity checks, login security or stored profile details. That prevents mixed wording about why account data is collected.
Cookie page
Cookie wording stays separate, but it uses the same naming for device signals, browser data and session checks. That helps you connect privacy choices with actual site behaviour.
Support page
The support page mirrors our privacy contact routes, including email and chat handoff steps. You should not be asked for extra personal details beyond what the request needs.
Security page
Security content matches this policy on password resets, suspicious access checks and log retention. When we explain protection steps, we keep the privacy impact clear and narrow.
Payment help
Payment help uses the same language for JazzCash, Easypaisa, SadaPay, NayaPay and Raast receipts. We separate transaction tracing from unnecessary personal data collection.
Promotion terms
Where a promotion needs account eligibility checks, the wording points back to this Privacy Policy. We explain which profile or transaction fields may be checked for that purpose.
Contact forms
Our contact forms ask only for details needed to answer your request. Privacy wording near each form links the reason for collection to the support action you choose.

Privacy page elements you can use

This page is built so you can scan privacy rights without reading every clause at once. The layout separates collection, use, sharing, storage and contact choices...

Plain language blocks

We break policy wording into short blocks that explain one privacy action at a time. That makes collection, storage and sharing easier to follow on mobile screens.

Local context chips

Chips for JazzCash, Easypaisa, SadaPay, NayaPay and Raast show where payment receipts may connect to privacy handling without turning the section into a transaction help page.

Request prompts

Privacy prompts tell you what to include when asking for access, correction or deletion. We ask for account matching details only after checking the request purpose.

Retention cues

Storage wording explains why certain records are kept for security, accounting or legal needs. We avoid vague wording and connect retention to the process that creates the record.

Sharing boundaries

Partner sharing is described by purpose, such as payment routing, fraud screening or support handling. We do not frame sharing as open access to your personal details.

Update marker

The policy includes change wording so you know when privacy handling has been amended. If a change affects your choices, we aim to make the impact clear.

Privacy questions before you join

We collect the details needed to create and secure your account, such as contact data, login records, identity checks and payment references. Extra data is requested only when needed for a specific account or support action.

JazzCash, Easypaisa, SadaPay, NayaPay and Raast may create receipts or transfer references tied to your account. We use those references to trace payments, confirm requests and resolve account queries.

Yes. Contact us through the email or chat route linked to your account and explain what needs correction. We may ask for matching proof before changing personal details to protect your account.

No. We do not sell your personal details. Data is shared only with service partners needed for account operation, payment routing, security screening, support handling or lawful requests where local law permits.

Retention depends on the record type. Security logs, payment receipts and support cases may be kept for operational, accounting or legal needs, then reduced or removed when they are no longer required.

Use the email address or chat route linked to your y99game account. State whether you want access, correction or deletion, and include only the details needed for us to match the request safely.