LEGAL REFERENCE

Privacy Policy For Your Account

n99 game links your account profile, lobby activity and JazzCash, Easypaisa, SadaPay or Raast records under one Privacy Policy, so you know what data we collect before you...

Pakistan account dataJazzCash contextEasypaisa contextSadaPay and Raast
n99 game Privacy Policy For Your Account

How We Handle Your Data

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

PRIVACY HELP

Contact Paths For Privacy Requests

If you want to ask about your data, correct account details or request access to records we hold, use the contact path...

Live chat Use chat when your privacy question is tied...
Email desk Send account data requests by email when you...
Account centre Inside your account centre, you can update contact...
ACCOUNT CARE

Policy Checks You Can See

We write this policy from the way n99 game actually handles account records, not from a generic legal template. Each privacy statement is tied to a live process: login security, game-session records...

Named payment rails

The policy names JazzCash, Easypaisa, SadaPay and Raast because those rails create practical records. We explain reference handling so you can match wallet activity with account history.

Session security

Login time, device type, IP signals and failed access attempts help us protect your account. We use these records to investigate unusual access without exposing full payment credentials.

Support files

When you contact us, we keep the message, reply path and any files you provide. This helps us answer follow-up privacy questions without asking you to repeat the same case.

Retention checks

We do not keep every record for the same period. Payment references, security logs and support files may follow different retention windows based on account safety and legal needs.

Limited sharing

We share data only with service providers needed for hosting, security, payment matching, analytics or customer support. Those partners receive the data required for their specific task.

Plain updates

When the Privacy Policy changes, we update the page date or policy text so you can see the new wording. Material changes may also appear inside account messages.

How This Policy Stays Aligned

Our Privacy Policy sits beside other legal pages, but it has a separate job. It explains personal data, while related pages describe account conduct, cookies or promotional conditions...

Account termsWhere account terms mention identity checks, this Privacy Policy explains the related data fields. That connection helps you understand why a document, phone number or payment reference may be requested.
Cookie pageCookie wording describes browser storage, while this policy explains how those signals connect with security, analytics and session continuity. The two pages should read together without conflicting meanings.
Promo rulesIf a promotion needs eligibility checks, this policy explains the data used for that decision. We avoid mixing offer language with data rights so privacy remains clear.
Payment recordsPayment help pages may describe transaction steps, while this policy explains what transaction data we keep. Reference numbers, status updates and timestamps are treated as privacy records.
Security wordingSecurity pages may describe account protection steps, and this policy explains the logs behind them. Device signals and access records are handled as personal data where they identify you.
Support scriptsSupport agents use wording that matches this policy when they ask for identity checks. That keeps privacy requests consistent across chat, email and account-centre conversations.
Regional accessWhere local law permits access, related pages use the same regional framing. This policy then explains how data is handled when your account is used from supported regions.
PAGE MARKERS

Visible Privacy Elements On This Page

This page is built so you can scan privacy details before sharing data with n99 game. The visible elements below point to the records we collect, the reasons...

Data categories We separate account details, device records, session activity and payment...
Purpose labels Each privacy purpose is written around a practical action, such...
Local rails JazzCash, Easypaisa, SadaPay and Raast appear as privacy context because...
Access wording The policy explains supported regions and local-law framing without adding...
Request routes Privacy contact paths are listed near the policy details so...
Change marker Policy changes are reflected in page wording or account messages...

Questions About Your Privacy

We collect account details, login records, device signals, session activity, support messages and payment references. The exact data depends on how you use your account and which privacy request you make.

No. We may store payment reference numbers, status updates, timestamps and masked wallet details for matching and support. We do not ask for or keep private wallet passwords.

Device and login data helps us spot unusual access, protect account sessions and answer security-related privacy questions. These records may include browser type, IP signals and failed login attempts.

Yes. You can request correction through support or update editable fields inside your account centre. We may confirm your identity before changing data tied to payments or account access.

Only teams and service providers that need the message to handle your request may access it. We keep support records so privacy follow-ups can be handled accurately.

Retention depends on the record type, legal needs and account safety. Payment references may be kept longer than simple support messages because they help resolve transaction and privacy queries.

We update the Privacy Policy text when our data practices change. If a change is material for your account, we may also place a message inside the account area.