LEGAL REFERENCE

How We Handle Your Personal Data

This Privacy Policy explains how 999gj collects, uses, stores and shares personal data when you open or use an account from Pakistan, where local law permits. We keep...

Pakistan accountsClear data useSecure account accessSupport requests
Explore The Lobby Read FAQ
999gj How We Handle Your Personal Data

Your Data And Our Legal Duties

We collect details you provide when creating an account, such as your name, contact details, date of birth and chosen account credentials. We also create records from account activity, device signals, IP address, session times, verification steps, payment references and support conversations. We use this material to open and maintain your account, confirm access, process requests, detect misuse, resolve disputes, meet applicable

legal duties and improve security. Where a payment route is available in your supported region, records may include JazzCash, Easypaisa, SadaPay, NayaPay or Raast references, but we do not need to store your full wallet password or secret PIN. We retain data only for as long as needed for these purposes, legal requirements or a properly documented dispute. Access may be restricted

where local law does not permit service. You can ask about your data, request correction or raise a concern through our support channels.

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

PRIVACY CONTACTS

Where To Send A Data Request

Our support routes are designed to keep privacy questions separate from ordinary account assistance. When you contact us, please use the email...

Account message Send a privacy question from your signed-in account...
Privacy email Use the privacy contact listed on our contact...
Security concern Tell support promptly if you suspect unauthorised access...
DATA PRACTICES

Controls That Shape This Policy

This policy reflects the practical controls used around account access and payment records. We separate authentication details from ordinary support content, limit staff access according to work needs and use event records...

Access records

We record sign-in time, device context and security events so that unusual access can be checked. These records support account protection and are not treated as a public profile.

Identity checks

When a request affects personal data or account control, we may compare supplied details with existing records. The aim is to protect your account while collecting only what the check requires.

Wallet references

JazzCash, Easypaisa, SadaPay, NayaPay and Raast references may appear in transaction records. We use those references to trace a request and do not ask for your private wallet PIN.

Limited access

Account data is made available internally according to operational need. Support, security and payment teams receive the details needed for their task rather than unrestricted access.

Retention checks

We assess whether records remain needed for service, security, dispute handling or legal duties. When a retention reason ends, data may be removed, anonymised or securely restricted.

Policy changes

If our data practices change materially, we update this page and identify the effective date. Continued account use after a lawful update means the revised terms apply where permitted.

How This Page Differs From Related Terms

Privacy Policy answers questions about personal data rather than setting out every account rule. Other legal pages may explain account conditions, transaction handling, promotions or access restrictions, while...

Data purpose
This page explains why we collect personal data and how each category supports account access, security, payment tracing, support handling or legal compliance.
Account terms
Account conditions concern how an account may be opened, used, paused or closed. They do not replace the privacy explanations given here.
Transaction records
Payment records can help us trace JazzCash, Easypaisa, SadaPay, NayaPay or Raast requests. This page explains the related data handling, not a wallet provider’s own rules.
Support content
Messages sent to support may be retained to resolve a request, identify repeated security events and maintain a reliable account history.
Third parties
Service providers may process limited data for hosting, security, verification or payment coordination. We expect appropriate safeguards and restrict their use to assigned work.
Your choices
You may ask for access, correction or clarification about personal data. Some requests can be limited where retention or legal duties require continued handling.
Regional access
Account access depends on supported regions and local law. A request about availability does not change how we protect personal data under this policy.
PAGE HIGHLIGHTS

Privacy Details At A Glance

The layout of this page brings the main privacy points into view before the longer legal wording. Each highlight points to a distinct part of your data relationship...

Collection map See the main categories we may receive, including contact details...
Use reasons Each collection purpose connects to account access, identity confirmation, request...
Sharing boundaries We describe when limited data may reach hosting, security, verification...
Retention view Records remain only while they support a stated service, security...
Request route The support section shows how to ask about your records...
Update signal Material changes to this policy are reflected on this page...

Common Questions About This Policy

We may collect your contact and account details, identity-check material, device and IP signals, sign-in events, transaction references and messages you send to support. The exact data depends on how you use your account.

Identity details help us create the correct account, protect account control, respond to data requests, investigate unusual activity and meet duties that apply in supported regions. We aim to request only relevant details.

We do not need your JazzCash, Easypaisa, SadaPay, NayaPay or Raast secret PIN for ordinary account support. We may retain transaction references and status details needed to trace a request.

Yes. Send an access request through the privacy contact or signed-in account route where available. We may verify your identity first, then explain the records we can provide and any lawful restriction.

Contact support with the incorrect field and the accurate replacement. We may request account verification before making a change, especially where the update could affect access, security checks or transaction history.

Limited data may be shared with providers supporting hosting, security, verification, payment coordination or legal requests. We restrict the purpose and expect suitable safeguards, while retaining responsibility for our own handling.

We update this page when our privacy practices change materially and show the applicable date. Please check the page periodically if you keep an account or submit ongoing support requests.