LEGAL REFERENCE

Privacy Policy for your six6 account

six6 puts your account data, verification records and local payment details under clear privacy rules before you open your account. This page explains what we collect, why we...

Account dataVerification recordsPakistan supportPayment privacy

Explore lobby Read FAQ

How our privacy stance works

Our Privacy Policy describes the data we collect when you create an account, verify access, contact support, use security tools or make payment requests where local law permits. We keep the data set practical: contact details, device signals, login records, payment references, identity checks and messages you send to us. We use these records to run your account, protect balances, handle disputes,

process withdrawals and meet legal duties that apply to our service. We do not sell your personal data. Access is limited to trained teams and service partners who need it for account, security, payment or support work.

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

CONTACT ROUTES

Ask us about your data

If you want to update, access or question your account data, contact us through the routes linked to your six6 profile. We...

POLICY CARE

How we keep the policy reliable

We write this Privacy Policy from the way six6 operates, not from a generic template. Product, payments, security and support teams check the wording when account flows change...

Local payment awareness

JazzCash, Easypaisa, SadaPay and Raast records can include references, timestamps and status labels. We use those details to match requests...

Security-led access

Staff access to personal data is role based and logged. We limit sensitive records to teams handling verification, fraud checks...

Clear retention reasons

We keep records only for account operation, legal duties, dispute handling and security checks. When a record is no longer...

Device signal use

Login device data helps us spot unusual access, protect sessions and confirm account changes. We use these signals for security...

Support transcript handling

Chat and email messages may be stored with your account so we can resolve follow-up questions. Sensitive documents are handled...

Policy change checks

When we adjust this page, we check that the change matches real account flows. Material changes may be shown through...

How related policy pages stay aligned

Your privacy rights connect with our terms, cookie controls, security rules and payment processing standards. We keep those pages aligned so one page does not promise something another...

Terms connection

Our terms explain account access, verification duties and service rules. This Privacy Policy explains the data used to support those duties, so both pages work together without mixing legal topics.

Cookie connection

Cookie settings cover browser storage and analytics signals. This page covers the wider personal data picture, including account records, payment references, support messages and security logs.

Security connection

Security rules describe how we protect access and balances. The privacy page explains which login data, device checks and account alerts may be used to keep those protections working.

Payment connection

Payment pages show available rails and processing steps. This policy explains how payment references, status records and withdrawal checks are handled behind those account actions.

Promotion connection

Promo pages may use account eligibility and activity records. This policy explains how those records are used, how messages may be sent and how you can ask about contact choices.

Support connection

Support pages explain how to reach us. This policy explains how your messages, attachments and account checks are stored, protected and linked to later service requests.

Regional connection

Access may depend on supported regions and where local law permits. This policy explains data handling for account activity tied to Pakistan language, payment and verification flows.

Visible elements on this privacy page

This page is arranged for quick reading without hiding key privacy points. Each block tells you what data is involved, why it matters and where to...

Plain section order

We start with the data we collect, then explain use, storage, sharing and contact paths. That order helps you scan the policy before moving into deeper legal wording.

Local context chips

Payment chips name JazzCash, Easypaisa, SadaPay and Raast because those records can appear in account privacy questions. The chips are context labels, not separate permissions.

Actionable contact cards

Support cards show where privacy questions should go and what details help us respond. We avoid asking for sensitive documents unless a request actually needs identity confirmation.

Account-first wording

The policy speaks to you as the account holder. We explain data handling around your profile, payments, messages and access logs instead of writing abstract legal copy.

Change awareness

Policy updates are written so you can see what changed in practical terms. If a change affects account data handling, we aim to make the wording clear on this page.

Request readiness

The layout prepares you to ask for access, correction or deletion where applicable. It also explains when we may need to keep records for security, disputes or legal duties.

Privacy Policy questions answered clearly

We collect account details such as contact data, login records, device signals and verification records. We also store support messages and payment references when they are needed to run your account.

Payment references help us match account activity with payment requests, handle delayed status updates and investigate disputes. We keep only the records needed for account operation, security checks and legal duties.

Yes, you can contact us through the privacy routes linked to your account. We may verify your identity first, then share the records we can provide under applicable rules.

Device and login data helps us protect your account, spot unusual access and manage session security. It can include device type, IP signals, timestamps and failed access attempts.

We may share necessary details with service partners that process account payments, verification or support tasks. They receive only what is needed for that purpose and must handle it securely.

Some profile fields can be updated inside your account. For locked details, verification records or payment-linked changes, contact support so we can confirm ownership and make the correction safely.