Terms alignment
The Terms page explains account use, while this policy explains the data behind account access. Both pages use the same identity and verification language for consistency.
LEGAL REFERENCE
Your Privacy At w678
w678 keeps your account data, device checks and Pakistan payment records inside one clear privacy framework, so you know what we collect before you open an account. This...
Account data explainedPakistan payment contextSecurity checks includedYour privacy choices
How Our Privacy Policy Works
This Privacy Policy applies when you use w678, contact our team, open an account, complete identity checks, or make payment requests where local law permits. We collect data that lets us run your account, verify access, process requests, protect against misuse, and answer your privacy questions. That may include your name, mobile number, login records, device details, approximate location signals, KYC files,
support messages, and transaction references linked to Pakistan payment rails. We do not sell your personal data. When sharing is needed, we limit it to service providers that help with hosting, security, verification, payment handling, analytics, or legal requests that apply to us.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep Policy Accurate
Our privacy wording is maintained by the teams that handle account access, verification, support and payment operations. We update it when data flows change, when a new service provider is added, or...
Operational checks
We compare the policy against live account screens, KYC prompts and support forms, so the wording reflects data you actually provide rather than a generic legal template.
Change records
Material policy edits are dated internally before publication. That helps our support team answer what changed, why it changed, and which account areas were affected.
Limited collection
We aim to collect only the data needed for account access, identity checks, security monitoring, payments, support replies, and legal handling where those duties apply.
Payment tagging
JazzCash, Easypaisa, SadaPay and Raast references are tagged for reconciliation and fraud checks, not for public display. Sensitive payment context stays inside restricted tools.
Access control
Staff access to personal data is role based. Support can view what is needed for a case, while deeper verification files require additional permission and audit logging.
Plain wording
We write this policy in clear Pakistani English so you can see what happens to your data before opening an account or sending documents for verification.
PAGE ALIGNMENT
Aligned Across Legal Pages
This page connects with our other legal pages without repeating every clause. The Privacy Policy explains personal data handling, while related pages explain service rules, cookies, promotions, and account terms. We keep...
Cookie alignment
Cookie wording points back here when a tracker or device identifier may become personal data. This keeps browser settings and account privacy in one connected flow.
KYC alignment
Verification wording matches the document prompts you see during account checks. We explain why identity files are requested, who can view them, and how long we retain them.
Payment alignment
Payment rules describe transaction steps; this policy describes the personal data attached to those steps, including mobile wallet references, bank routing context, and reconciliation records.
Support alignment
Support pages explain how to contact us. This policy explains what support messages may contain, how we store case records, and why we may verify you first.
Security alignment
Security wording is matched with our account protection steps, including login checks, device signals, fraud monitoring, restricted staff access, and records of sensitive account actions.
Change alignment
When another legal page changes a data flow, we check this policy too. That keeps privacy wording in step with real account and support processes.
VISIBLE MARKERS
Privacy Page Layout Markers
We structure this page so you can scan privacy duties before you join. The visible markers separate collection, use, sharing, retention, security and contact rights, rather than hiding...
Last updated area
A visible update area shows when privacy wording was last...
Data category blocks
The policy separates account details, device logs, payment references, KYC...
Purpose labels
Each collection point is tied to a purpose such as...
Sharing markers
Where service providers may process data for us, the policy...
Retention signals
Retention wording explains why some records are kept after account...
Choice prompts
The contact section explains how to ask for access, correction...
Privacy Questions Before You Join
We collect account details, mobile number, login activity, device signals, payment references, support messages, and KYC files when required. The exact data depends on which account steps you complete.
Identity documents help us confirm account ownership, handle withdrawals, reduce fraud, and meet legal requests where they apply. Access to these files is restricted to trained staff and verification tools.
We share only what is needed with payment processors, reconciliation partners, security tools, or legal channels that apply to us. JazzCash, Easypaisa, SadaPay and Raast references are handled as restricted records.
Yes. Contact us from your registered account channel and explain what needs correction. We may ask for proof before changing details that affect identity, payments, withdrawals, or account access.
Retention depends on the record type. Some support messages are kept briefly, while KYC, payment and security logs may be retained longer for dispute handling, fraud checks, or legal duties.
We use restricted staff access, session checks, audit logs, encryption practices, and monitoring for unusual account activity. No online system is risk free, so keep your password and mobile access private.