Access
Ask what personal data connected with your account we hold, why it is used and, where applicable, which service category receives it.
This Privacy Policy explains how 666xc collects, uses, stores and protects details connected with your account, browsing activity and support requests in Pakistan. It also sets out how...
We collect details you provide when creating or maintaining an account, such as your name, contact details, date of birth, login credentials and selected account preferences. We may also receive technical data, including device type, browser details, IP address, session activity and security events, to keep account access working and identify unusual sign-ins. If you request a transaction through JazzCash, Easypaisa, SadaPay
or Raast, we process the payment reference, status and limited verification details needed to reconcile the request; we do not need your full wallet password. We use this data to provide account services, answer support messages, prevent misuse, meet applicable legal duties and improve page performance. Access is limited to staff and service partners who need it for those purposes. Retention depends
on the account relationship, legal duties, dispute handling and security needs. Where local law permits, you may ask about access, correction, deletion or restriction of your personal data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our privacy approach is built around practical controls that affect your account every day. We separate login activity from payment references, limit internal access by work need and use verification when a...
We may record sign-in time, device signals, IP address and security outcomes. These records help us detect unusual access, investigate account messages and protect your profile from activity that does not match your normal pattern.
When a local wallet request is made, we use the reference, amount, status and related account details needed to match the request. We do not ask for your JazzCash, Easypaisa, SadaPay or Raast password.
A request to change sensitive details or release account data may require identity checks. The exact step depends on the request, the account record and signals suggesting that additional protection is needed.
Some technical, messaging, hosting or payment functions may be handled by service partners. We expect them to process relevant data only for the assigned service and to apply suitable confidentiality and security controls.
We retain records for as long as needed for account operation, dispute handling, legal duties, fraud prevention or security review. When a record is no longer needed, our processes are intended to remove or anonymise it.
If this policy changes in a material way, we may place an updated notice in the account area or use a contact route linked to you. The date at the top of the current policy shows which wording applies.
Privacy requests can concern different kinds of records, so we handle them according to their purpose and practical effect. A request about contact details is different from a request about security logs...
Ask what personal data connected with your account we hold, why it is used and, where applicable, which service category receives it.
Tell us when a name, contact route or profile detail is inaccurate. We may confirm the change before updating the account record.
You may ask for removal where retention is not required for legal, security, dispute or account-service reasons.
You may ask us to limit a particular use while a concern about accuracy, purpose or legal basis is being considered.
Where applicable, you may object to a data use based on your circumstances. We will assess the request against the purpose and local rules.
If processing relies on permission, you may withdraw it for future use. Earlier processing may remain lawful where another basis applies.
We may request account or identity details before acting, helping prevent a personal data request from being sent to the wrong person.
The privacy page is arranged to make the policy easier to use on a phone or desktop. We place the purpose first, then explain account records, local wallet...