Terms connection
The terms set account rules, while this policy explains what data those rules may require. For example, verification duties may create records that are handled under this Privacy Policy.
LEGAL REFERENCE
How Your Privacy Is Protected
999dice keeps your account details, payment traces and support messages within a clear Privacy Policy built for Pakistan access where local law permits. Open your account when ready...
Account dataPayment recordsDevice checksSupport privacy
Our Privacy Position For Pakistan
This Privacy Policy explains how we collect, use, store and protect data linked to your 999dice account in supported regions. We may process identity details, contact data, device signals, login records, payment references and support messages so your account can be opened, secured, funded and maintained. Payment names such as JazzCash, Easypaisa, SadaPay and Raast appear here only to show the local
account context in which privacy checks happen. We do not sell your personal data. We share data only when needed for account operation, fraud checks, payment handling, security monitoring, legal duties or service providers working under our instructions. You can contact us to ask about access, correction or deletion, subject to account, safety and record keeping duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep This Policy Accurate
Our Privacy Policy is written from the way we run 999dice accounts, not from generic legal wording. We connect each clause to an actual account event, such as...
Operational wording
We describe data use around real account steps, including sign-in, identity checks, payment references and support messages. This helps you...
Regional context
Pakistan access is described with supported regions wording because availability can depend on local law. The Privacy Policy keeps that...
Payment clarity
JazzCash, Easypaisa, SadaPay and Raast are named only where payment privacy matters. We explain reference handling, verification needs and record...
Security checks
Device signals, login timing and account activity may be used to spot unusual access. The policy explains this security purpose...
Support handling
Support conversations can include personal details, so our policy covers how those messages are stored and used. We limit internal...
Change tracking
When the Privacy Policy changes, we update the page so you can read the current wording before using account features...
PAGE CONSISTENCY
Privacy Policy Across Our Legal Pages
Our legal pages work together, but this page stays focused on privacy. Account terms may explain use of the service, while this Privacy Policy explains data handling behind that use. If another...
Cookie connection
Cookie wording may describe browser storage, session tools and preference choices. This Privacy Policy connects that technical activity to account security, analytics and privacy rights in plain English.
Payment connection
Payment pages may explain how JazzCash, Easypaisa, SadaPay or Raast appear in your account flow. This policy explains how related references are processed and protected.
Security connection
Security wording may cover passwords, device checks and account alerts. This Privacy Policy explains the personal data used for those checks and why that handling is necessary.
Support connection
Support pages may show how to contact us. This Privacy Policy explains how your support messages, attachments and case history are stored, accessed and used to resolve requests.
Promotions connection
If a promotion requires eligibility checks, this policy covers the data side of that process. We focus on records, account status and lawful processing rather than promotional wording.
Account closure connection
Closure pages may describe ending account access. This Privacy Policy explains which records may remain after closure for legal, payment, security or dispute handling reasons.
VISIBLE CONTROLS
Privacy Layout You Can Read
We place key privacy controls where you can find them before sharing extra details. The page separates collection, use, sharing, retention and rights so you do not need...
Plain section labels
Each part of the Privacy Policy uses direct headings so...
Local examples
Pakistan payment references are shown as examples when they explain...
Rights pathway
Access, correction and deletion requests are grouped together so you...
Sharing limits
The sharing section states when service providers, payment partners or...
Retention wording
Retention is explained by record type, such as account, payment...
Update markers
Policy changes are shown through visible page updates and account-facing...
Privacy Questions Before You Join
We may collect account details, contact data, login records, device signals, payment references and support messages. The exact data depends on how you use the account and what checks are required.
Payment references can connect to your account, so they count as personal data in many cases. We use them for funding checks, withdrawal verification, dispute handling and security monitoring.
No. We do not sell your personal data. We share data only for account operation, payment handling, safety checks, service support, legal duties or providers working under our instructions.
Send a privacy request through the contact path and include your account email. We may verify account control before releasing records, then provide the response allowed by applicable duties.
Yes, you can ask us to correct inaccurate account details. Some fields may need proof or extra checks, especially where payment records, identity checks or security logs are involved.
Retention depends on the record type. Account, payment, support and security records may be kept for different periods because legal duties, dispute handling and fraud prevention needs can differ.