LEGAL REFERENCE

Your Privacy Policy Explained Clearly

This Privacy Policy explains how d99999 collects, uses, stores and protects details connected with your account in Pakistan. We keep the wording practical, so you can understand what...

Clear data purposesAccount securityPakistan context
d99999 Your Privacy Policy Explained Clearly

How We Handle Your Account Data

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

PRIVACY CONTACTS

Where To Send Privacy Questions

Privacy requests should reach the same support channels used for account assistance, but marking the subject clearly helps us route your message. We may ask for account details or an identity check before discussing personal records. That step protects your account and prevents disclosure to an unauthorised person.

Team online

Privacy message

Send a request through the account support channel and write “Privacy” in the subject. Include the email or mobile number linked to d99999 so we can locate the correct record.

Account assistance

If your request concerns access, correction or deletion, explain the result you need. Our support team may ask follow-up questions before making a change to account-linked data.

Transaction query

For a JazzCash, Easypaisa, SadaPay or Raast record, include the reference number and date. Never send a password, one-time code or complete card credential in a message.

DATA PRACTICES

Privacy Controls Built Into Operations

Our policy reflects the way account and transaction records are handled in daily operations. We separate access credentials from ordinary support conversation, restrict internal access by work need and use checks when...

Purpose-based use

We use account details for defined needs such as access, support, security checks, transaction reconciliation and legal compliance. We do not treat every collected detail as available for every business purpose.

Login protection

Account credentials are handled with security controls designed to reduce unauthorised access. We may record device or session signals when they help identify suspicious sign-ins or protect an active account.

Payment matching

When a supported Pakistani payment is used, a reference and status may be matched to your account. We use that record to confirm movement without requesting your private wallet password or one-time code.

Support records

Messages sent to support may be retained to resolve the matter, identify repeated account issues and demonstrate how a request was handled. Access is limited to staff who need the record for that work.

Retention checks

We assess whether records are still needed for service operation, legal duties, disputes or security. When a record no longer has a valid purpose, it may be securely removed or de-identified.

Regional access

Account access and data handling can depend on your location and local rules. We apply supported-region checks and use the wording “where local law permits” when access is conditional.

What This Policy Covers Differently

Privacy wording can appear beside account, transaction and security materials, yet each document has a separate purpose. This page focuses on personal data and the choices connected with...

Personal data
This policy explains collection, use, sharing, storage and access relating to details that can identify or be linked with you through a d99999 account.
Account access
Account terms may explain how an account is opened, maintained or restricted. This page instead explains which related records may be created while those steps take place.
Transaction records
A transaction may create references, timestamps and status details. The privacy rules here describe how those records are used for matching, security, support and lawful retention.
Security events
Security procedures can require device, session or contact checks. Those signals are addressed here only as personal data used to protect access and investigate unusual activity.
Third parties
Payment and technical partners may process limited details for a defined task. We expect those parties to receive only the data needed for their assigned service.
Your requests
You may ask about access, correction or deletion where applicable. We may verify identity first and may retain some records when law or a valid dispute requires it.
Policy changes
If this policy changes, the updated page may show a new effective date or revised wording. Continued account use after a lawful update is handled under the published version.

Privacy Details At A Glance

The layout of this page is designed to help you find a privacy answer without searching through unrelated account material. Each panel points to a distinct...

Collection

See the account, contact, device and transaction details that may reach d99999 when you create an account, use a feature, contact support or arrange a supported transaction.

Purpose

Find the reasons behind each data activity, including access management, security, support handling, transaction matching, service operation and duties imposed by applicable law.

Sharing

Understand when limited details may move to technical, identity, payment or legal partners, and why those recipients need the data for a defined operational task.

Storage

Read how retention depends on service needs, security work, disputes and legal obligations. Records may be removed, restricted or de-identified when a valid purpose ends.

Your choices

Learn how to request access, correction or deletion where applicable. We may need to confirm account ownership before responding or changing a personal record.

Regional wording

Pakistan-focused language explains supported access and local context while recognising that availability and data duties can differ according to your location and applicable law.

Common Questions About Your Data

Depending on how you use the account, we may handle your name, contact details, birth date, login data, device signals, support messages and transaction references linked with JazzCash, Easypaisa, SadaPay or Raast.

References help us match a payment status to the correct account, investigate an error, answer a support request, detect unusual activity and meet lawful record duties. They do not include your private wallet password or one-time code.

Limited details may be shared with technical, identity, payment or legal partners when a defined task requires it. We expect each recipient to handle the data for that task and apply suitable safeguards.

Yes, you can contact support with an access request. We may ask for reasonable proof that you control the account, then explain what can be supplied and any lawful reason a record must be withheld.

You may request correction when an account detail is inaccurate or incomplete. Some changes require an ownership check, supporting material or a separate account process before the record can be amended.

Retention depends on the reason for holding a record, including service operation, security, disputes and legal duties. When no valid purpose remains, the record may be removed, restricted or de-identified.

The policy is written for d99999 account activity in Pakistan and supported regions. Access and handling may vary with your location, and account availability remains subject to local law.