Account terms link
Account terms explain what you agree to when you use we33. This Privacy Policy adds how personal details from that account flow are collected, used, shared and retained.
LEGAL REFERENCE
Privacy Policy for your we33 account
we33 sets out how your account details, device signals and Pakistan payment records are handled when you open an account and use our lobby where local law permits...
Pakistan privacy scopeJazzCash contextEasypaisa recordsSadaPay checksRaast references
How we handle personal details
This Privacy Policy explains what we collect, why we collect it, and how long we keep it when you use we33 from supported regions. We may process your name, phone number, email address, account access logs, device identifiers, approximate location, payment reference codes and service messages. We use these details to create your account, protect access, reconcile JazzCash, Easypaisa, SadaPay and Raast
activity, answer support requests, detect misuse and meet lawful record duties. We do not sell your personal details. Some service partners help us with hosting, security checks, payment reconciliation and message delivery, and they receive only what is needed for that work. If law, court order or regulator request applies, we may disclose relevant records after checking the request.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How we keep this policy current
We keep the Privacy Policy tied to how we33 actually works, not to vague legal wording. When account access, wallet handling, device security or support routing changes, the...
Operator wording
The policy is written from our own account flow, including sign-in checks, payment references and support handling. That keeps the...
Pakistan context
We describe Pakistan access, supported regions and local payment references in plain English. This makes the policy easier to read...
Security alignment
Access logs, device markers and session records are treated as security data. We use them to detect unusual access, protect...
Retention checks
We keep records for service, legal and accounting needs, then reduce or remove data when it is no longer required...
Partner control
Hosting, security and payment service partners may process limited records for us. We choose the data fields needed for the...
Plain request path
Your access, correction or deletion request goes through support first, then privacy handling if deeper checks are needed. We explain...
PAGE ALIGNMENT
Consistency across our legal pages
Our legal pages are meant to work together. This Privacy Policy explains data handling, while account terms cover service use and cookie wording covers browser storage. If two pages touch the same...
Cookie wording link
Cookie wording covers browser storage, analytics signals and preference tools. This policy connects those signals to account security, session continuity and privacy choices available through support.
Payment references
Payment pages may show JazzCash, Easypaisa, SadaPay and Raast options. This policy explains the privacy side, including transaction references, reconciliation records and support checks.
Support records
Support terms may explain service contact. This policy explains what happens to chat logs, email messages, account checks and documents you provide during a privacy request.
Security notices
Security language explains how we protect access. This policy shows which personal details help that work, such as device signals, login times and account activity records.
Market wording
Where we mention Pakistan or supported regions, the privacy meaning is location context and service availability. It does not change your ability to ask about personal details.
Policy changes
When we update legal wording, the Privacy Policy date and page text should reflect the changed practice. You can ask support what changed if a section affects your account.
POLICY LAYOUT
Visible privacy page cues
This page is arranged so you can check the privacy points that matter before sharing details with we33. Headings separate collection, use, sharing, retention and request rights. Short...
Clear section labels
Each page block names the privacy action it covers, such...
Local context chips
Short chips mention JazzCash, Easypaisa, SadaPay and Raast only as...
Direct request wording
The page uses direct wording for access, correction and deletion...
Security markers
Security cues explain why device and login records exist. They...
Retention clarity
Retention text separates service records, payment references and legal records...
Change awareness
Policy change text points you back to this page when...
Privacy Policy questions answered
We collect details needed for your account, such as name, phone number, email, access logs, device signals, payment references and support messages. Extra checks may apply when security or legal duties require them.
We keep transaction references to match wallet activity with your we33 account, investigate support queries and meet record duties. We do not need your wallet password, PIN or unrelated wallet history.
Yes. Contact support with your account phone number and the records you want to access. We may verify your identity first, then share available records unless a legal restriction applies.
You can ask us to correct inaccurate account details through support. We may request proof when the change affects identity, payment reconciliation or account recovery, so the update protects your account.
We share limited data with partners that support hosting, security, payment reconciliation and support messaging. They receive only the fields needed for their task and must handle them under our instructions.
Retention depends on the record type and legal need. Support messages may be kept for service history, while payment references and account checks can remain longer for reconciliation and compliance duties.
We update this page when privacy handling changes in a meaningful way. If the change affects your account choices, we aim to make the wording clear and support can explain the affected section.