Account terms
Our account terms explain how you open and manage access. This policy adds the data layer, including which identity, login and contact details we hold for that access.
LEGAL REFERENCE
Privacy Policy For Your Account
king 97 keeps privacy controls close to your account, so the data you share for login, identity checks, wallet activity and support is handled under one clear policy...
Pakistan account privacyLogin data careWallet record handlingSupport contact paths
How We Treat Your Data
This Privacy Policy explains how king 97 collects, stores, shares and protects data linked to your account in supported regions of Pakistan. We collect only what is needed to create access, confirm identity, process wallet records, detect account misuse, answer support messages and meet legal duties where local law permits. Payment references from JazzCash, Easypaisa, SadaPay and Raast may appear in account
records, but we do not ask you to send card secrets or wallet PINs to our agents. Some records are retained to answer disputes, confirm withdrawals, secure login sessions and keep a clear audit trail. When retention is no longer needed, we reduce or remove data in line with our internal controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY HELP
Contact Paths For Privacy Queries
If you want to ask about account data, correction, access logs or retention, contact us from the same account area you use for support. We may ask for matching details before discussing private records. That protects you from another person trying to obtain account data through chat, email or copied wallet receipts.
Team online
In-account chat
Use chat after logging in when your question involves wallet records, identity status or account activity. Our team can match the request to your session before discussing private details.
Email privacy desk
Send email when you need a written response about correction, access or deletion requests. Include your account name only, not wallet PINs, screenshots with secrets or third-party IDs.
Security escalation
If you think another person accessed your account data, contact us quickly. We can lock sensitive actions, check recent sessions and ask you to refresh login credentials.
CARE SIGNALS
Policy Checks Behind The Page
We write this policy from the operator side of king 97, not as a detached article. The wording reflects how our account, wallet and support systems work in...
Account access controls
Your private account area is protected by login checks and session controls. We use those controls to reduce unauthorised viewing...
Payment reference limits
JazzCash, Easypaisa, SadaPay and Raast entries are used as transaction references. We do not need your wallet PIN, full app...
Support handling
Our support team sees only the account data needed for the query. Sensitive cases are escalated so fewer agents handle...
Retention checks
We keep certain records for account security, dispute handling and legal duties. When those reasons end, our process is to...
Device session care
We track session data such as device type, login time and basic location signals. This helps us spot unusual access...
Policy change log
When privacy wording changes, we update the page date in our internal records and make the new wording visible here...
PAGE ALIGNMENT
Consistency Across Our Legal Pages
Your privacy rights should not change depending on which legal page you read first. We align this Privacy Policy with our cookie terms, account rules and promotion terms so the same data...
Cookie wording
The cookie page deals with browser storage and tracking choices. This policy connects those technical signals to wider account privacy, session security and fraud checks.
Promotion terms
Promotion terms may require account checks before rewards appear. This policy explains how related eligibility records are handled without exposing private wallet or identity data.
Wallet rules
Wallet rules explain funding and withdrawal steps. This policy explains the privacy treatment for transaction references, verification images and support messages about those records.
Security statements
Security statements describe controls around login and account access. This policy adds how session logs, device signals and escalation records are used to protect private data.
Regional wording
Where access depends on supported regions, we use the same local law phrasing across pages. This keeps privacy expectations clear before you open your account.
Contact routes
Support pages list contact channels for everyday account help. This policy narrows those routes for privacy requests, corrections, data access and account security concerns.
Privacy Layout You Can Read
We design the privacy page so you can scan what matters without digging through unrelated platform copy. The layout separates collection, use, sharing, storage and contact...
Plain collection labels
We label account data, wallet references, device signals and support messages separately. This makes it easier to see what is collected and why each category exists.
Clear use cases
Each privacy use case is tied to an account purpose, such as login, verification, withdrawal checks or support. We avoid mixing privacy wording with unrelated lobby copy.
Sharing boundaries
We explain when data may be shared with payment processors, fraud controls or legal responders. The wording keeps those boundaries tied to account and wallet activity.
Storage cues
Retention wording tells you why some records stay longer than others. Wallet references, identity checks and support transcripts can follow different storage periods.
Action prompts
Privacy actions are written around clear requests: access, correction, deletion or security help. You can contact us without sending secrets that support never needs.
Local context
Pakistan payment names appear only where they affect privacy records. JazzCash, Easypaisa, SadaPay and Raast references are treated as context for account handling.
Questions About Your Privacy
We collect account details needed for access, contact, identity checks, wallet activity and security controls. We also record session signals such as login time and device type to protect your account.
No. We may store payment references, receipt markers or transaction status linked to your account, but we do not ask for wallet PINs, app passwords or phone unlock codes.
Verification records help us confirm account ownership, answer disputes and reduce misuse. They are handled as private account records and retained only while there is a valid reason.
Yes. Contact us through in-account chat or email with the detail you want corrected. We may ask for matching proof before changing private account or identity records.
Only team roles handling your request can access relevant support messages. More sensitive privacy, identity or wallet cases may be escalated so access is kept narrower.
Cookies and similar tools help manage sessions, preferences and security checks. When those signals connect to your account, they are handled under this Privacy Policy as account-related data.
We place the current wording on this page and update our internal page date when changes are made. Read this page again before sharing new account or wallet details.