Privacy Policy For 6666r Accounts
This Privacy Policy explains how 6666r collects, uses, stores and protects details connected with your account in Pakistan. We keep the wording practical, so you can understand what...
How We Handle Your Personal Details
We collect details you provide during account creation, including your name, contact details, date of birth where required, chosen currency and access credentials. We also receive technical records such as device type, browser data, IP address, session activity and security events. When you use JazzCash, Easypaisa, SadaPay or Raast, payment confirmation and transaction references may be shared with us by the relevant
service so we can match activity to your account. We use these details to provide access, process account requests, detect suspicious activity, answer support messages and meet applicable legal duties. We retain records only for as long as needed for these purposes or where a lawful retention period applies. Access may depend on supported regions and local law. You can contact us
to ask about access, correction or deletion, subject to legal and security limits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Practical Controls Behind This Policy
We wrote this policy around the actual points where account details move through 6666r. Access records help us recognise unusual sign-ins, support teams see only what their work requires, and transaction references...
Session records
We record device, browser and access events to identify unusual sign-ins, support account recovery and investigate security alerts. These records are used for protection rather than casual profiling.
Identity checks
A request involving account data may require matching contact details or additional verification. This step protects your records from disclosure to a person who cannot show account control.
Payment references
JazzCash, Easypaisa, SadaPay and Raast may return confirmation references for reconciliation. We do not ask you to share a wallet PIN, password or secret security code.
Access control
Internal access is limited according to work needs. Account, security and support records are handled through controlled systems, with activity checks intended to reduce unauthorised viewing.
Retention practice
We keep records for service, safety and legal purposes, then remove or anonymise them when the applicable need ends, unless a lawful obligation requires longer storage.
Policy changes
If our handling changes materially, we will update this page and adjust the effective wording. Continued account access after an update means you should read the revised terms.
What Stays Consistent Across Our Policies
This page sits alongside our other legal pages, but its subject remains personal data and privacy. The points below show how we keep wording consistent when a rule...
| Same account identity | Privacy requests are tied to the same account identity used for access support, so we can distinguish a genuine request from an unrelated message or attempted takeover. |
|---|---|
| Same regional check | Data handling can vary where local law permits access only in supported regions. We assess location signals and legal requirements before confirming a service-related request. |
| Same security threshold | A request for sensitive records receives stronger checks than a general question. This protects your account while still giving you a clear route to ask about stored details. |
| Same payment boundary | We may use payment references to match account activity, but wallet passwords, PINs and secret codes remain with your payment provider and should not be sent to us. |
| Same support trail | Messages about privacy may be retained as case records so we can follow the request, confirm the outcome and show how an account-related decision was reached. |
| Same correction route | If a stored detail is inaccurate, contact support with the relevant account marker. We check the request, update eligible records and explain any lawful reason for keeping the original. |
| Same policy access | You can return to this page from the legal area of 6666r. We aim to keep the wording readable, current and connected to the way our account systems operate. |
Key Features Of This Privacy Layout
We arranged this page so the privacy points you are most likely to need appear in a useful order. The opening sets the scope, the legal notice explains...