Privacy Policy for your 2gis account
2gis connects your privacy choices with every account step, from opening the lobby to checking Pakistan payment records. Read this policy before you join, then open your account...
How our privacy policy works
This Privacy Policy explains how we handle personal data when you create a 2gis account, access casino or sportsbook areas where local law permits, use support, or connect a Pakistan payment rail. We collect only the data needed to run your account, verify access, manage security checks, process payment records, and answer privacy requests. Payment names such as JazzCash, Easypaisa, SadaPay and
Raast may appear in your account history so we can match your request with the correct transaction record. We do not sell your personal data. We may share limited records with payment processors, security vendors, or legal advisers when needed for account safety, dispute handling, fraud checks, or lawful requests in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy choices
If you want to ask about your data, start with the privacy contact path rather than a lobby message. That helps us identify whether you need access, correction, removal, or a copy of certain account records. We may ask for account proof before sharing any privacy details.
Privacy email
Ask about what data we hold, why a record exists, or how to correct account details. We route privacy messages separately from lobby chats so your request reaches the right team.
Live chat handoff
If you begin through chat, tell us the request is about privacy. Our team will move it away from general help and may ask you to confirm account ownership first.
Security checks
Before we release or change account data, we check identity signals such as your login email, recent payment rail, and device pattern. This protects your account from unwanted access.
How we keep this policy reliable
We write this policy from the account flow we operate, not from generic legal wording. Each section is tied to a real data point: joining, login, payment matching, support tickets, cookies, and...
Plain account language
We explain privacy steps in the same terms you see while using 2gis: account, login, payment record, support ticket, device signal, and cookie choice. This keeps the policy practical.
Local payment context
Pakistan payment rails can create reference numbers, wallet names, and status messages. Our policy tells you why those details may be kept with JazzCash, Easypaisa, SadaPay, or Raast records.
Limited sharing
We share account data only when a service is needed, such as payment processing, security screening, technical hosting, or legal handling. Each transfer is tied to a defined privacy purpose.
Access control
Internal access to privacy records is limited by role. Support can see request history, payment teams can check transaction status, and security staff can examine login risk where needed.
Retention checks
We keep records for account operation, payment disputes, fraud prevention, and legal duties. When a record is no longer needed, we reduce, archive, or remove it according to our controls.
Policy change log
When we adjust this policy, we refresh the date and explain material changes in clear wording. You can read the current version before deciding whether to keep using 2gis.
Privacy pages stay aligned
Your privacy rights should not change depending on which 2gis legal page you open. This page is written to align with our cookie, terms, and support wording, while...
| Account terms | Our terms describe account access and acceptable use. This Privacy Policy adds the data angle, including what we collect during join steps, login checks, and account protection processes. |
|---|---|
| Cookie page | Cookie wording covers browser storage and preference tools. Here we explain how cookie data connects with privacy choices, session safety, device recognition, and analytics that support account reliability. |
| Support page | Support content shows how to reach us. This policy adds how your ticket text, attachments, contact details, and identity checks may be used when the request involves personal data. |
| Payment records | Payment help may mention status checks. This policy explains the privacy side: wallet references, rail names, timestamps, and verification steps used to match JazzCash, Easypaisa, SadaPay, or Raast activity. |
| Security wording | Security sections discuss keeping accounts safe. This policy explains data signals behind that work, including device patterns, failed login attempts, location indicators, and fraud screening in supported regions. |
| Promo notices | If you receive account messages, this policy explains what contact data may be used and how you can ask us to adjust privacy preferences for non-essential messages. |
| Legal requests | Where a lawful request applies, we may need to preserve or disclose limited records. This policy explains the reason, scope, and checks used before any privacy-related action. |
What you see on this page
We built this page so you can move from broad privacy scope into practical choices without hunting through legal blocks. The layout separates account data, payment record context...