LEGAL REFERENCE

Privacy Policy for Your 8yyy Account

This Privacy Policy explains what we collect when you open or use an 8yyy account, why we need it, and how we protect it in supported regions of...

Account data usePakistan access wordingLocal payment contextSupport privacy
Explore Lobby Read FAQ
8yyy Privacy Policy for Your 8yyy Account

How This Policy Applies

This Privacy Policy applies when you access 8yyy where local law permits, create an account, browse the lobby, contact support, verify your profile, or use local Pakistani payment rails connected to your account. We collect only the details needed to run the account flow, confirm access, process withdrawals, protect sessions, answer service requests, and meet operational record duties. That may include your

name, phone number, login records, device signals, transaction references, support messages, and documents you send for account checks. We do not sell your personal data. Where service partners help us with hosting, security, payments, analytics, or support routing, we share only the fields needed for that task under controlled access.

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

CONTACT ROUTES

Privacy Help From Our Team

If you want to ask about your data, request correction, or understand why a document is needed, contact us through the account...

Account support chat Use the in-account chat for privacy questions tied...
Email privacy requests Email works for access, correction, and deletion questions...
Verification follow-up When a privacy request involves identity documents, we...
DATA CHECKS

How We Keep Policy Accurate

We treat this page as a live policy statement for our own service, not a generic legal page. Our team checks it against the account flow, Pakistan payment steps, support scripts, verification...

Account flow checked

We compare this policy with the screens you see while opening an account, logging in, verifying details, and requesting withdrawals, so the data categories described here match the actual fields collected.

Payment records mapped

JazzCash, Easypaisa, SadaPay, and Raast references are handled as account transaction records. We store the reference data needed for tracing, support, and reconciliation without adding unrelated personal details.

Support access limited

Support staff can view the account details needed to answer your request. Sensitive verification material is restricted to trained staff, and access is linked to the reason for handling the case.

Security logs explained

Login time, device type, IP range, and session signals help us detect account misuse. These logs are used for protection, troubleshooting, and access checks, not for unrelated profiling.

Partner sharing narrowed

Service partners receive only the fields needed to host pages, process payment references, route support, or keep account sessions secure. We do not let partners use your data for their own unrelated purposes.

Policy edits tracked

When this Privacy Policy changes, we update the page date in our publishing system and keep internal records of what changed, who approved it, and why the wording needed adjustment.

Consistent Privacy Across Our Pages

Your privacy rights should not change from one 8yyy policy page to another. We align this Privacy Policy with account terms, cookie wording, support handling, and verification practices...

Account terms link
Our account terms explain service rules, while this policy explains personal data handling. When the same action appears in both pages, we keep the privacy reason clear and separate from game or account rules.
Cookie wording match
Cookie text covers browser storage, session continuity, and measurement. This policy connects those tools to privacy purposes, such as keeping you logged in and understanding service errors across devices.
Verification language
Identity checks are described with the same limits across support and policy pages. We explain why proof may be needed, who handles it, and how long it remains useful for account control.
Payment record consistency
Local transaction references appear in account history and support cases. This policy explains their privacy treatment, including reconciliation, fraud checks, withdrawal handling, and record retention tied to your account.
Support transcript use
Support pages may show how to contact us, but this policy explains what happens to the messages. We retain transcripts to answer follow-ups, resolve disputes, and train staff on safer handling.
Security process wording
Security pages may mention login protection, while this policy explains the personal data behind it. Device and access signals are used to protect sessions and investigate suspicious activity.
Change handling
When a related page changes, we check whether this Privacy Policy also needs an update. That keeps your privacy reading aligned with the account experience you actually receive.
PAGE SIGNALS

Policy Layout You Can Read Fast

We designed this Privacy Policy so you can move quickly from summary points to practical rights and contact routes. The page highlights the data we collect, the purposes...

Plain section labels Each section uses direct labels so you can find account...
Short badges The badges near the page opening point to the main...
Local context shown Pakistan wording and local rails are included where they matter...
Rights placed clearly Access, correction, deletion, and objection requests are explained in practical...
Retention explained simply We keep personal data for as long as it is...
Contact paths visible Privacy contact routes stay close to the policy text, so...

Common 8yyy Privacy Questions

We collect account details, contact data, login records, device signals, payment references, verification material you provide, and support messages. Each category is linked to account operation, security, withdrawals, compliance duties, or service help.

We keep local transaction references so we can match account activity, trace failed or delayed requests, answer support queries, and reconcile records. We do not use those references for unrelated profiling or third-party promotion.

Yes. Contact us through your account if your name, phone number, or other profile details need correction. We may request proof when the change affects verification, withdrawals, or account ownership.

Retention depends on the record type. Session logs may be shorter, while account, transaction, verification, and dispute records may be kept longer where needed for security, operational checks, or legal duties.

Yes, but only for limited service tasks such as hosting, security monitoring, payment reference processing, analytics, and support routing. Partners receive the fields needed for their task and cannot use them for unrelated purposes.

Support conversations are attached to your account record and visible only to staff who need them for service handling. We use them to answer follow-ups, resolve disputes, and improve privacy-safe support responses.