LEGAL REFERENCE

How 3pati Handles Your Data

Your 3pati account relies on clear data handling: we collect what helps us open, secure, and maintain your access where local law permits. This Privacy Policy explains the...

Account dataCookie choicesPakistan payment contextSupport records
3pati How 3pati Handles Your Data

Our Privacy Position In Pakistan

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

PRIVACY HELP

Contact Routes For Privacy Requests

If you want to ask about your data, correction options, account access records, or how a payment reference is stored, contact us through the same channels used for account help. Give us the email or phone tied to your account so we can confirm the request before discussing private data.

Team online

Account support

Send your privacy request from the email linked to your 3pati account. We use that match to confirm you are asking about your own profile before sharing any account data.

Live chat handoff

Chat can collect your privacy question and route it to the right team. For safety, chat staff may ask you to continue through email before discussing stored records.

Payment reference checks

For JazzCash, Easypaisa, SadaPay or Raast queries, include only the transaction reference and account phone. Do not send wallet PINs, screenshots with hidden codes, or card secrets.

DATA CARE

How We Keep Policy Work Accountable

We write this Privacy Policy from our own operating flow, not as a generic legal page. The wording is tied to account opening, login safety, support handling, game session records, and Pakistani...

Purpose mapping

Each data category in this policy is tied to a real account purpose, such as login checks, payment matching, support follow-up, fraud controls, or legal record keeping in supported regions.

Limited sharing

We share data with service partners only when needed for verification, payment processing, security checks, hosting, analytics, or support handling. Partners receive the minimum fields needed for that role.

Access controls

Internal access is restricted by work role. Support staff see what they need to answer your request, while payment and security records are handled by smaller authorised teams.

Policy checks

When we adjust account flows, cookie tools, support forms, or payment matching steps, we check whether this policy still describes the data path accurately and clearly.

Retention logic

We keep account and transaction records only for operational, dispute, security, and legal needs. When records no longer serve those purposes, we delete or anonymise them.

Clear requests

You can ask about access, correction, deletion, or consent choices. We may need to verify your identity before acting, especially where payment or security records are involved.

POLICY ALIGNMENT

Consistency Across Privacy Pages

Our Privacy Policy sits beside related account terms and cookie wording, so your data rights are not split across unrelated pages. This section explains how we keep privacy language aligned wherever 3pati...

01

Account terms link

Our account terms explain service access, while this policy explains the personal data behind that access. We keep both pages aligned when verification or security steps change.

02

Cookie wording

Cookie text covers browser storage, session tools, and measurement tags. This policy connects those tools to privacy purposes, such as login continuity, fraud signals, and preference handling.

03

Payment records

Payment pages may describe JazzCash, Easypaisa, SadaPay and Raast flows. This policy explains how matching references, account names, timestamps, and support messages are handled.

04

Support transcripts

Support pages describe contact routes, while this policy covers how we store messages, attachments, agent replies, and identity checks needed to answer your privacy request.

05

Security wording

Security statements explain account protection steps. This policy adds the privacy side, including device signals, login history, and how access to sensitive records is controlled.

06

Regional wording

Where access is limited to supported regions, our privacy text follows the same regional approach. We avoid promising availability where local law does not permit service access.

07

Change tracking

If we update related legal pages, we check this policy for matching language. The aim is simple: you should not see conflicting privacy wording across 3pati.

Visible Privacy Layout Cues

This page is built so you can scan the main privacy points before opening an account or contacting us. The layout separates data categories, support paths...

Short badges

The badges under the page headline show the main privacy themes at a glance: account data, cookie choices, Pakistan payment context, and support records tied to your profile.

Plain section names

Each section title uses direct wording so you can move from collection to support, accountability, alignment, and questions without hunting through dense legal blocks.

Local context chips

The legal notice includes JazzCash, Easypaisa, SadaPay and Raast chips because payment references are a common privacy concern for Pakistani account holders.

Request paths

The support cards show where privacy requests start and what details are safe to share, reducing the chance that you send wallet secrets or unrelated documents.

Policy depth

The trust section breaks down sharing, access control, retention, and request handling so the page does more than state broad promises about privacy.

Question format

The FAQ uses direct questions we expect from you, including cookies, payment records, deletion requests, and account verification, with answers focused on privacy choices.

Questions About Your Privacy

We may collect your name, contact details, login history, device signals, account activity, payment references, and support messages. The exact fields depend on how you access 3pati and which services you use.

Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account, answer transaction queries, and maintain records for disputes, security checks, and legal duties in supported regions.

No. We do not sell your personal data. We may share limited fields with service partners for hosting, verification, payment processing, analytics, security monitoring, or support tasks needed to run your account.

We keep records for as long as needed for account operation, security, payment matching, dispute handling, and legal duties. After those needs end, we delete, anonymise, or restrict records where possible.

Yes. Contact support from the email or phone linked to your 3pati account and tell us what needs correction. We may verify your identity before changing sensitive account or payment records.

Cookies and similar tools help maintain sessions, remember preferences, measure page performance, and detect suspicious access. You can adjust browser settings, though some account features may not work smoothly without essential cookies.

Send your request through account support and include the email or phone tied to your profile. For your safety, avoid sending wallet PINs, passwords, or screenshots showing hidden security codes.