How we handle your data
Live Baccarat, Andar Bahar, slot rooms and sportsbook slips create account data that our Privacy Policy explains before you open an account. We set out what we collect...
Our privacy position for Pakistan
Our Privacy Policy describes how 1k game collects, uses, stores and shares data linked to your account where local law permits. We collect details you provide during account creation, contact with support, payment checks and activity inside the lobby. For Pakistani payment rails, we may process transaction references, account names, time stamps and verification results needed to match your JazzCash, Easypaisa, SadaPay,
NayaPay or Raast activity with your 1k game balance. We do not sell your personal data. We use your data to operate your account, protect access, answer privacy requests, meet legal duties and keep records for security checks. If access changes in supported regions, this policy remains the reference for how your stored data is handled.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy requests
You can contact us when you want to ask what data we hold, correct account details, or raise a privacy concern tied to payments, login activity or support chat. We ask for enough proof to match the request with your account, then route it to the team that handles account records and security checks.
Live chat request
Use chat after logging in if your privacy question relates to recent account activity, payment matching or device access. We may ask verification questions before discussing personal data.
Email privacy desk
Send privacy requests by email when you need a written response or want to attach identity proof. Include your account name, contact number and the data issue.
Payment query route
For JazzCash, Easypaisa, SadaPay, NayaPay or Raast records, share the transaction reference only through our support channel so we can match it securely.
How we keep policy text current
Our Privacy Policy is written around the account flow we operate: sign-in, lobby activity, payment matching, verification and support handling. We check wording when we adjust account security, add a contact route...
Account flow mapping
We map each privacy clause to a real account step, from login to withdrawal checks, so the policy reflects how your data moves inside 1k game.
Security wording
Security clauses cover password protection, device checks and suspicious access handling. We explain why these checks use data rather than leaving them hidden behind vague wording.
Payment record checks
We describe how transaction references from Pakistan rails are matched to your account, including names, timing and status results needed for balance accuracy.
Support access limits
Support staff only see account details needed for the request they are handling. Privacy questions are routed with extra care before personal data is discussed.
Change tracking
When our data handling changes, we update the policy text rather than relying on outdated account wording. Material changes are placed where you can notice them.
Regional wording
Pakistan references are written for supported regions and local law context. We avoid broad claims that would not match how access works for your account.
Consistency across related policy pages
The Privacy Policy connects with our other legal pages, but it has its own purpose. It explains personal data handling rather than account rules, reward terms or game...
| Terms page link | Our terms explain account rules, while this policy explains the data behind those rules, including verification, access checks and records needed for disputes. |
|---|---|
| Cookie notice match | Cookie wording covers browser storage and session signals. The Privacy Policy connects that data to login protection, analytics and account safety choices. |
| Payment page context | Payment pages describe rails you may use. This policy explains how related references, account names and status messages are processed for privacy purposes. |
| Support page link | Support pages show how to contact us. This policy explains what support can request, what it records and why identity checks may be needed. |
| Security page match | Security wording covers access protection. The Privacy Policy explains the personal data used in that protection, such as device signals and login timing. |
| Promo terms separation | Reward pages may mention eligibility records. This policy explains how eligibility data is stored without turning privacy wording into promotional copy. |
| Regional access wording | Where access is limited to supported regions, related pages use matching language so your privacy expectations remain consistent across the site. |
What the privacy page shows
This privacy page is arranged so you can scan the matters that affect your account before you join. The layout keeps collection, use, sharing, storage, contact...
Clear section labels
Each privacy area has a direct label, so you can move from collection to storage, sharing or contact rights without reading unrelated account material.
Plain account wording
We use account terms you see inside 1k game, such as login, balance, support chat and verification, instead of legal phrasing that hides meaning.
Local context chips
Short chips name Pakistan rails and regions where context matters, helping you spot how payment references connect with privacy handling on this page.
Request path markers
Contact markers show where to ask about access, correction or account data handling, reducing confusion when you need a privacy response.
Security callouts
Security callouts explain why login checks, device signals and transaction matching may involve personal data, keeping protective processing visible.
Update placement
When wording changes, we place the change near the relevant privacy area, so you can see what shifted without scanning the entire page.