How ptd3 protects your data
ptd3 keeps your account, device and transaction data in a privacy policy you can read before you open your account. We explain what we collect, why we need...
Our privacy policy position
Our privacy policy explains how ptd3 collects and uses data when you create an account, access the lobby, contact support or use Pakistani rails where local law permits. We collect only the data needed to run account access, protect sessions, process transactions and answer your requests. This can include your name, contact details, device signals, login records, transaction references and messages you
send us. JazzCash, Easypaisa, SadaPay and Raast references are handled as account records, not public content. We keep access limited to staff and service partners who need the data for security, payment processing, account checks, fraud prevention or customer care. We also describe how you can ask about correction, access or deletion where it applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy accurate
We do not treat privacy text as a static page. The policy is checked when account flows, transaction partners, device controls or support tooling changes. Each change is written for plain reading...
Service owner checks
Account, support and payments staff check the policy language against the data they actually handle. That keeps the page tied to real workflows instead of broad legal phrasing.
Change records
When a privacy process changes, we record what changed and why. That helps us answer your questions with context rather than relying on memory or old wording.
Plain English drafting
We write this page in clear Pakistani English, with short sections and direct examples. Legal meaning matters, but the policy should still make sense before you open an account.
Access control
Internal access to account and transaction data is limited by role. Support staff see what is needed for your request, while sensitive account checks stay restricted.
Partner purpose checks
Service partners are assessed by the purpose they serve, such as transaction routing, account security or customer care. We do not share data simply because it is convenient.
Retention review
We keep data for account operation, legal record needs and dispute handling, then reduce or remove it when it is no longer required for those purposes.
Where this page stays consistent
This privacy policy connects with other ptd3 legal pages without repeating them word for word. When those pages mention account checks, cookie settings, promotions or disputes, this page...
| Account terms | Where our terms describe account creation or closure, this policy explains the data used for those steps. The two pages should read together, without conflicting dates or purposes. |
|---|---|
| Cookie wording | Cookie settings may collect browser and device signals. This policy explains why those signals matter for session security, language preferences and fraud checks on ptd3. |
| Promotion records | When you check what is running this week, we may record eligibility checks and account actions. This policy explains how those records are linked to your profile. |
| Transaction references | Payment help pages may mention JazzCash, Easypaisa, SadaPay or Raast routing. This policy explains how transaction references are stored and used for account support. |
| Security alerts | Account security pages may describe login alerts or device checks. This policy states what data is processed when we investigate unusual access or reset contact details. |
| Support records | Help pages explain how to contact us. This policy explains how chat transcripts, email threads and identity prompts are kept for service quality and dispute handling. |
| Regional access | Where access is available in supported regions, this policy explains the data checks linked to location signals, account language and local transaction references. |
Privacy layout you can scan
We designed the privacy page so you can find the part that matters before sharing more details. The layout separates account data, transaction records, cookies, contact routes and...