LEGAL REFERENCE

How our Privacy Policy works

0 ad keeps your account data, payment records and lobby activity under one clear Privacy Policy for Pakistan. Before you open an account, this page explains what we...

Account data useCookie choicesPakistan supportPayment record care
Explore Lobby Read FAQ
0 ad How our Privacy Policy works

How we handle Pakistan account data

Our Privacy Policy explains how 0 ad handles the details you give us when you create an account, verify access, contact support or use payment rails in supported regions where local law permits. We collect only the data needed to run your account, protect access, process records and answer your requests. Payment references from JazzCash, Easypaisa, SadaPay and Raast are used to

match transactions with your account and resolve disputes. We also use device, cookie and session data to keep sign-in secure, remember privacy choices and identify unusual activity. We do not sell your personal data. When service partners help with hosting, payments or security checks, we limit access to the task they perform and expect secure handling of your records.

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

HELP CHANNELS

Reach us about privacy

Privacy questions should not feel hidden behind account menus. We keep clear contact paths for access requests, correction requests, cookie questions and payment-record checks. When you write to us, include the account detail needed to identify you, but never send passwords or full security codes.

Team online

Privacy inbox

Email our privacy contact when you want to ask what account data we hold, correct a record or raise a concern about how your details were handled by 0 ad.

Live help handoff

If you start in chat, our team can route a privacy request to the right inbox and tell you which account details are safe to share for identity checks.

Payment record query

For JazzCash, Easypaisa, SadaPay or Raast concerns, send the transaction reference and account email so we can trace the privacy impact without asking for sensitive codes.

POLICY CHECKS

How we keep the policy accurate

We write this Privacy Policy from our own account, support and payment flows, not from copied legal wording. Each section is checked against how 0 ad actually handles...

Account flow mapping

We map privacy wording to the actual account steps you see, including sign-in, verification prompts, profile edits and support requests...

Cookie checks

Our cookie wording is checked against the tags used for session security, preference memory and basic site measurement, with separate...

Payment trace controls

We describe payment record handling around references, timestamps and account matching, because JazzCash, Easypaisa, SadaPay and Raast queries need careful...

Security wording

Our policy explains why device signals, login history and verification results may be processed, with the aim of protecting your...

Support training

Support agents are told which privacy details they can request, which details they must never ask for and when a...

Change tracking

When we change privacy wording, we keep internal records of what changed and why, so questions about older account handling...

Policy wording across our legal pages

Your privacy rights should read the same wherever you enter our legal pages. We align this policy with our cookie wording, account terms and support scripts so there...

Cookie wording
Cookie text is kept aligned with this Privacy Policy, so session cookies, preference settings and measurement tools are described in the same way across our legal pages.
Account terms
Where account terms mention verification, we keep the privacy explanation consistent, including why identity checks may be needed and how related records are connected to your account.
Security pages
Security wording uses the same privacy position on device signals, login alerts and suspicious activity checks, so you can see why these records are processed.
Payment records
Payment wording matches this policy by separating transaction references from sensitive banking details, with special care for JazzCash, Easypaisa, SadaPay and Raast support cases.
Support scripts
Our support replies follow the same privacy language used here, including safe identity checks, response handling and what we will not ask you to send.
Regional access
Where access depends on supported regions and local law, the same wording is used across legal pages so your privacy expectations stay clear.
Policy updates
When privacy wording changes, linked legal pages are checked too, so old phrasing does not create a different promise about your account data.
VISIBLE CONTROLS

What you see on this page

This Privacy Policy is arranged so you can scan the parts that affect your account before you join. We separate data types, reasons for use, cookie choices, sharing...

Plain summary The opening section gives you the short version of our...
Data categories We group account, payment, device, cookie and support-ticket records separately...
Choice areas Cookie and contact preferences are described in their own areas...
Sharing limits Where partners help with hosting, security or payments, the policy...
Request path Privacy requests are placed close to contact details, making it...
Update marker The policy carries update wording so you can tell when...

Privacy questions before you join

We collect the details needed to create and protect your account, such as contact details, login records, verification results, device signals and support history. Payment references are added only when needed for account matching.

These rails create transaction references that may need to be matched with your 0 ad account. We use those records for payment tracing, dispute handling and support checks, not for selling your personal data.

Cookies help keep your session active, remember privacy choices and support basic site measurement. If cookie settings are offered on your device, your choices are stored so we can apply them on later visits.

Yes. Contact our privacy inbox with the account email or phone linked to your profile. We may need a safe identity check before sharing records, correcting details or handling a deletion request.

We share data only when a partner needs it for hosting, security, payment tracing or support delivery. Access is limited to the task involved, and sensitive codes or passwords should never be sent.

We update the policy text when account, cookie, security or payment-record handling changes. The page carries update wording, and material changes may also be flagged through account or support channels.