Privacy Policy for wc3 Accounts
wc3 puts privacy choices beside your account flow, so you can see what data we collect, why we use it, and how to ask us about it before...
How Our Privacy Policy Works
Our Privacy Policy explains the personal data we collect when you create or manage a wc3 account, including contact details, sign-in records, device signals, wallet references, verification files, and support messages. We use that data to operate account access, keep wallet activity matched to the right profile, answer your requests, reduce fraud risk, and meet legal duties that apply in supported regions.
We do not sell your personal data. Limited data may be shared with service vendors who help with hosting, security checks, payment routing, or customer care, and they receive only what is needed for that task. JazzCash, Easypaisa, SadaPay and Raast references are handled as payment context, not public profile content.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Help Through wc3 Support
Privacy questions should reach people who can read account records without asking you to repeat private details in open chat. We keep contact paths clear inside wc3 so you can ask about stored data, request correction, or raise a concern about wallet references tied to your account.
Privacy inbox
Send privacy requests through the account contact form or the email shown in the footer. Include your wc3 account name and the request type, but avoid sending wallet PINs or full document images unless we ask.
Live chat handoff
If you start in chat, our team can move privacy matters to a safer channel. That keeps your personal data away from quick chat threads while still letting us link the request to your account.
Verification step
Before we change or release account data, we may ask for a narrow identity check. This protects your profile from someone else using your name, phone number, or wallet reference.
Privacy Signals We Maintain
We write this Privacy Policy from the same operational view used by our account, payments and security teams. The wording is meant to be practical: what is collected...
Clear data owner
The policy is written as wc3 speaking about our own account flow. We avoid vague outside wording so you know...
Wallet minimisation
For JazzCash, Easypaisa, SadaPay and Raast references, we aim to keep only the fields needed to match activity, resolve support...
Access controls
Customer care, finance and security staff receive role-based access. A support agent does not need the same record depth as...
Vendor limits
When we use vendors for hosting, fraud screening, analytics or message delivery, contract terms limit their handling of wc3 data...
Change record
When this Privacy Policy changes in a meaningful way, we update the page date and adjust the wording that explains...
Pakistan wording
We write for Pakistani English readers and refer to local wallet rails by name. That helps you connect the policy...
Consistency Across wc3 Legal Pages
Our Privacy Policy does not stand alone. It lines up with the account terms, cookie wording, support pages and wallet flow so the same data meaning is carried...
Visible Privacy Cues on wc3
The privacy-side layout is built so you do not have to search through long legal blocks for practical points. Short labels, contact cards and version cues help you...