Account terms
Our account terms explain your access duties, while this Privacy Policy explains the data behind those duties. Together they show why verification, login security and record keeping may be required.
LEGAL REFERENCE
How We Handle Your Data
g900 collects only the account, device and payment data needed to run your access where local law permits. Read how our Privacy Policy covers Pakistan records before you...
Pakistan account dataJazzCash recordsEasypaisa checksSadaPay and Raast
Privacy Terms For Pakistan Accounts
This Privacy Policy explains how we collect, use, store and protect data connected with your g900 account in supported regions of Pakistan. We may process your name, contact details, login records, device signals, payment references and support messages so your account can open securely, transactions can be checked, and privacy requests can be answered. JazzCash, Easypaisa, SadaPay and Raast references are used
as context for verifying account activity, not for unrelated profiling. We keep access to personal data limited to trained teams, security tools and service partners that help us operate the account flow. Where local law permits, we may keep records for fraud checks, dispute handling and legal duties, then remove or anonymise them when no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep This Policy Current
We write this Privacy Policy from how g900 actually handles account records, not from a template alone. When account flows, verification steps, support tools or payment checks change, we update the policy...
Local account checks
Our policy describes Pakistan account verification in plain terms, including identity checks, login protection and payment reference matching. This helps you understand why data is requested before access is granted.
Payment data separation
Wallet references for JazzCash, Easypaisa, SadaPay and Raast are kept apart from game activity data where practical. This reduces needless sharing inside our systems and keeps purpose clear.
Access control
Only trained staff and approved service tools may access personal data. Permissions are linked to job need, and sensitive account actions leave records that our security team can inspect.
Device security signals
We use device and session signals to protect account access, detect unusual logins and reduce fraud. The policy explains this use without turning those signals into unrelated advertising profiles.
Retention checks
Records are held for account operation, dispute handling, fraud prevention and legal duties. When those reasons expire, we remove, mask or aggregate data so it no longer identifies you.
Plain language updates
When the Privacy Policy changes, we aim to explain the change in clear Pakistani English. You should be able to see what changed without reading legal wording twice.
PAGE CONSISTENCY
Matching Privacy Across Legal Pages
Your privacy rights should not change from one g900 legal page to another. This section explains how the Privacy Policy aligns with our account terms, cookie wording, transaction records and support handling...
Cookie wording
Cookie wording covers browser storage and session tools. The Privacy Policy connects those tools to account security, preference handling and analytics that help us keep the site stable.
Transaction records
Transaction terms explain processing steps, while this policy explains how payment references are stored. We keep the purpose narrow, especially for JazzCash, Easypaisa, SadaPay and Raast checks.
Support records
Support pages explain how to reach us, and this policy explains how messages are handled. We may keep chat or email records to resolve account disputes and privacy requests.
Security wording
Security language on related pages describes account protection. This policy adds how device data, login time, IP records and risk flags may be used for that protection.
Promo notices
Promo notices may mention account eligibility, while this policy explains related data use. We avoid using sensitive payment details for unrelated targeting or unnecessary profiling.
Change records
When legal pages change, we keep wording aligned so privacy terms remain clear. The date on the page helps you see which version applies to your account.
VISIBLE CONTROLS
Policy Layout You Can Read Quickly
We structure the Privacy Policy so you can find the parts that matter without searching through dense legal text. The page separates collection, use, storage, sharing, retention and...
Clear section labels
Each policy area uses direct labels so you can move...
Local context chips
Pakistan payment names appear only where they explain data handling...
Request prompts
Contact prompts appear near rights wording, so you can ask...
Version date
A visible date helps you know when the Privacy Policy...
Short explanations
We use compact paragraphs for collection, sharing and retention so...
Rights wording
Rights sections explain how you can ask about personal data...
Privacy Policy Questions From You
We collect account details, contact data, login records, device signals, payment references and support messages. We use them to run access, verify activity, secure your account and answer privacy requests.
We keep payment references to match transactions, handle disputes and detect misuse. Wallet or rail details are treated as account records, not as material for unrelated profiling.
Yes. Contact our privacy inbox or secure chat and provide the account identifier we request. We verify ownership first, then explain the data we can provide under applicable rules.
Retention depends on the record type and the reason it was collected. Security, transaction and dispute records may stay longer than profile edits, then become masked or removed.
We share data only with service partners needed for hosting, security, verification, payments or support. Each partner must use the data for the agreed purpose and protect it.
Open a privacy request through chat or email and tell us which field looks wrong. We may ask for proof before changing details tied to verification or transactions.