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.
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...
This Privacy Policy applies when you interact with 3pati from supported regions in Pakistan, open an account, manage access, complete checks, contact our team, or use payment routes connected to your profile. We may process your name, contact details, device identifiers, login activity, transaction references, and messages sent to support. We use this data to protect account access, meet verification duties, detect
misuse, maintain service records, and respond to your requests. We do not sell your personal data. Where a payment provider or verification partner is involved, we share only the fields needed for that task. If local law changes, we may amend this page and keep the updated wording available here.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
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.
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.
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.
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.
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...
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.
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.
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.
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.
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.
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.
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...
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.
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.
Payment pages may describe JazzCash, Easypaisa, SadaPay and Raast flows. This policy explains how matching references, account names, timestamps, and support messages are handled.
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.
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.
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.
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.
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...
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.
Each section title uses direct wording so you can move from collection to support, accountability, alignment, and questions without hunting through dense legal blocks.
The legal notice includes JazzCash, Easypaisa, SadaPay and Raast chips because payment references are a common privacy concern for Pakistani account holders.
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.
The trust section breaks down sharing, access control, retention, and request handling so the page does more than state broad promises about privacy.
The FAQ uses direct questions we expect from you, including cookies, payment records, deletion requests, and account verification, with answers focused on privacy choices.