Privacy Policy
This page covers what personal data 6dd collects, why we use it, how long we keep it and which contact route you can use for privacy requests.
LEGAL REFERENCE
How We Handle Your Privacy
6dd keeps your account data, payment records and device signals under a clear Privacy Policy before you open an account. Read it to see what we collect, why...
Account dataJazzCash recordsDevice checksPakistan support
Our Pakistan Privacy Posture
This Privacy Policy explains how 6dd handles personal data linked to your account, wallet activity, security checks and support messages in supported regions where local law permits access. We collect only the details needed to run your account, confirm payment activity, protect login sessions and answer your requests. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive transaction references, account
names, time stamps and status updates from the payment flow. We do not sell your personal data. We keep records for operational, legal, fraud-control and dispute needs, then reduce or remove them when they are no longer needed. You can ask us to check, correct or remove eligible data through the privacy contact paths on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CARE CHECKS
How We Keep Policy Careful
Our Privacy Policy is written around the way 6dd actually handles account flows in Pakistan. We check the wording against login steps, payment receipts, support handling and security logs, so the page...
Account mapping
We map each policy point to a real account step, such as joining, logging in, changing details or asking support for help. That keeps the wording tied to actual data handling.
Payment references
JazzCash, Easypaisa, SadaPay and Raast records are described as transaction references, not full banking profiles. We use them to confirm account activity, resolve mismatches and handle disputes.
Session safety
Device, browser and location signals help us spot unusual access attempts. The policy explains this use in plain language, so you know why a login may need extra checking.
Limited access
Personal data is available only to teams that need it for account support, payment checking, security control or legal handling. Internal access is logged and kept within defined work duties.
Record retention
Some records must stay for dispute, fraud-control and legal reasons, even after you ask for removal. The policy separates removable data from records we must keep for a defined period.
Plain English
We write privacy terms in clear Pakistani English, with examples from the 6dd account flow. If a term affects your data rights, we aim to explain it without legal padding.
PAGE ALIGNMENT
Aligned Across Legal Pages
Our legal pages work together, but this Privacy Policy stays focused on data handling. If another page explains account rules, cookie choices or service terms, this page explains the personal data behind...
Cookie terms
Cookie wording should match this policy by explaining browser storage, analytics tags and session controls. Privacy rights remain here, while cookie choices sit with the browser tools.
Terms page
Terms may cover account conduct, service access and rule acceptance. This policy links those actions to data use, such as identity checks, login records and support history.
Promo rules
When offer pages need account checks, this policy explains the personal data used to confirm eligibility, prevent duplicate use and keep records for support handling.
Payment notices
Payment pages may show transaction steps, but this policy explains which references 6dd receives from JazzCash, Easypaisa, SadaPay and Raast during account checks.
Security wording
Security pages may describe passwords and device checks. This policy explains the related data handling, including login signals, risk flags and limited access by internal teams.
Support records
Support content may explain how to reach us. This policy explains what happens to chat logs, email threads and account messages after your privacy request is handled.
Privacy Page Layout Highlights
We built this page so you can scan the privacy terms before opening your account. The layout separates collection, use, sharing, retention and contact rights, then...
Clear section order
The policy starts with data collection, then moves through use, storage, sharing and contact rights. This order helps you follow the account data journey without jumping between legal blocks.
Account examples
Each main privacy point uses a 6dd example, such as login checks, wallet references or support messages. That keeps the policy practical instead of abstract legal wording.
Local wording
Pakistan payment names and account flows appear where they matter. You can see how JazzCash, Easypaisa, SadaPay and Raast records fit into the privacy process.
Rights area
Your access, correction and removal options are grouped together so you can act quickly. We also explain when a record cannot be removed straight away.
Security cues
Security wording is placed near the data points it protects, including login records and device signals. This helps you understand why certain checks happen on your account.
Contact prompts
Privacy contact routes sit close to the policy text they support. If a paragraph raises a question, you can choose chat, inbox or email without searching elsewhere.
Privacy Questions Before You Join
We collect account details, contact data, login records, device signals, payment references and support messages. The exact data depends on how you use your account and which checks apply in supported regions.
Payment references help us match JazzCash, Easypaisa, SadaPay or Raast activity to your account. We use them for account crediting, withdrawal checks, dispute handling and fraud-control records.
No. We use personal data to operate your account, protect access, process support requests and meet legal duties. We share data only where service delivery, security checks or lawful requests require it.
Yes. Contact us through your account inbox, chat or email with the details that need correction. We may verify your login or payment reference before changing account records.
Retention depends on the record type. Support messages may be kept for service history, while payment and security records may stay longer for dispute, fraud-control or legal handling.
We use session checks, device signals, access controls and internal logging to protect account data. If a login looks unusual, we may ask for extra confirmation before allowing changes.
Open your account inbox or contact support by chat or email. Include your account name and enough detail for us to locate the right record without sharing extra private data.