LEGAL REFERENCE

Your a07 Privacy Policy

Clear data handling for your a07 account starts here, with plain detail on what we collect, why we use it, and how payment traces are protected. Read this...

Pakistan privacy contextAccount data explainedJazzCash and EasypaisaSadaPay and RaastContact paths included
Explore Lobby Read FAQ
a07 Your a07 Privacy Policy

How we handle your data

This Privacy Policy explains how a07 handles the personal data connected with your account where local law permits access to our services. We collect only the details needed to create your account, protect access, process wallet activity, respond to privacy requests, and meet record duties that may apply in supported regions. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay, and Raast are treated

as account security records, not public profile content. We do not sell your personal data. When service partners help with hosting, fraud checks, payment routing, or customer care, we limit their access to the task required and expect them to protect the data under written controls. You can contact us to ask for access, correction, deletion, or an explanation of how a

specific data item is used.

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

CONTACT ROUTES

Reach us about privacy

Privacy questions should reach the right team without you repeating your account details across several channels. We separate account support from privacy...

Privacy email Send privacy requests through our contact mailbox with...
Live chat handoff If you start in chat, our team can...
Payment trace query For JazzCash, Easypaisa, SadaPay, NayaPay, or Raast privacy...
POLICY CHECKS

How we keep this policy current

We treat this Privacy Policy as a live account document, not a static footer link. When our account flow, payment partners, security checks, or support routing changes, we...

Data map checks

We compare policy wording with the data fields used during account setup, login, payment tracing, and support contact. If a...

Access control

Internal access to privacy records is limited by role, with customer care, payment support, and security teams seeing only what...

Payment rail matching

We check JazzCash, Easypaisa, SadaPay, NayaPay, and Raast wording against the actual reference data our team receives. The policy avoids...

Security wording

Privacy text is aligned with password reset, session control, device checks, and fraud alerts. If a security process affects personal...

Change log discipline

Material edits are dated internally before publication, so we can trace why a privacy clause changed. This helps support answer...

Local language pass

We write in clear Pakistani English and avoid legal fog where a plain sentence works. Terms around account identity, phone...

Aligned wording across our legal pages

Your privacy rights should not change from one a07 page to another. We keep definitions, contact routes, payment references, account checks, and security wording aligned so this policy...

Account terms
Where account terms mention identity checks, this policy explains the related data use. That keeps account access wording and privacy duties connected without repeating every legal clause.
Cookie text
Cookie wording is matched with this policy so device data, session signals, and preference records are described the same way wherever you read about browser-based data use.
Security page
Security content explains protection steps, while this policy explains the personal data behind those steps. Together they show why login checks, device records, and alerts may be used.
Wallet records
Payment pages may show how a transfer is routed, but this policy states how related references are stored, checked, and limited to account and support purposes.
Promo terms
If a promotion needs account eligibility checks, this policy explains the data categories used for that decision. The same contact route applies if you ask about the record.
Support scripts
Support replies should match this policy when agents ask for verification. We keep scripts focused on required identifiers rather than collecting extra details during privacy conversations.
Regional wording
Access language across legal pages refers to supported regions and local law. This policy uses the same framing when describing why some account data may need extra checks.
PRIVACY LAYOUT

Privacy page elements at a glance

This page is built so you can scan privacy duties before reading every clause. The layout separates data categories, account controls, support contacts, regional wording, and update cues...

Plain headings Each heading points to a privacy decision, such as collection...
Short chips The chips near legal text call out Pakistan payment contexts...
Rights markers Where a clause affects access, correction, deletion, or explanation requests...
Storage cues Retention language is grouped near the data it covers, including...
Sharing labels When partners are mentioned, the page states the task they...
Update signal Policy changes are placed where you can spot them without...

Privacy Policy questions answered

We collect the details needed to create and protect your account, such as contact data, login signals, device markers, payment references, and support messages. We use them for account access and required checks.

Payment references help us match JazzCash, Easypaisa, SadaPay, NayaPay, or Raast activity to your account. We use them for tracing, support, fraud checks, and record duties, not public display.

Yes. Contact us with the field you believe is wrong and enough account detail to verify you. We may ask for extra proof before changing identity, phone, or payment-related records.

We may share limited data with partners that help with hosting, security checks, payment routing, analytics, or support. Their access should match the task, and they are not given open account control.

Retention depends on the record type and the reason it exists. Account, payment, security, and support records may be kept for different periods where local law permits or requires retention.

When we make a material privacy change, we update the policy text and keep internal change records. If the change affects your account choices, we aim to make the wording easy to notice.

Use the privacy contact route and include your account name, registered phone, and the action you want. Do not send wallet passwords or full card-style secrets in any privacy request.