LEGAL REFERENCE

How msp2 handles your data

msp2 keeps casino account data, live-table logs and Pakistan payment references in a clear privacy flow before you open your account. Read how we collect, protect and use...

Account dataCookie controlsPakistan paymentsAccess requests
Explore Lobby Read FAQ
msp2 How msp2 handles your data

Our privacy posture for Pakistan

This Privacy Policy explains how msp2 handles personal data connected to your account, identity checks, device sessions, wallet activity and support messages in supported regions of Pakistan. We collect only the data needed to run your account, secure access, process requests and meet legal or operational duties where local law permits. Payment references from JazzCash, Easypaisa, SadaPay and Raast are used to

match wallet actions with your account record; we do not ask you to share private wallet PINs with support. We may keep limited records for security checks, dispute handling, fraud prevention and tax or audit duties. When we use service providers for hosting, analytics, payment routing or customer care, we require them to handle your data under controlled access and purpose limits.

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

CONTACT ROUTES

Reach us about privacy requests

If you want to ask about your data, update account details or raise a privacy concern, contact us from the same email or phone linked to your msp2 account. That helps us verify you without exposing extra data.

Team online

Privacy email

Use our privacy email for access, correction or deletion requests. Include your account email, mobile number and a short reason so our privacy desk can locate the right record safely.

Live chat

Open chat from your account when the matter is urgent. Our agents can capture the request, confirm your identity steps and move sensitive privacy cases to the correct internal queue.

Security contact

Message security support if you notice an unknown login, changed phone number or wallet reference you do not recognise. We lock access while checks are completed and keep a case trail.

DATA CHECKS

How we keep the policy current

We treat this page as an operating document, not a static notice. Our privacy, product and support teams check it when account flows, cookies, security tools or Pakistan payment references change.

Operational checks

We compare the policy against active account screens, wallet forms and support scripts. If a data field is added or removed, the policy wording is checked before release.

Access mapping

Internal roles are mapped to the data they need. Support cannot see wallet PINs, and security staff receive only the records needed to investigate login or account protection issues.

Cookie register

We keep a register of cookies and similar tools used for login sessions, fraud signals, language settings and analytics. Changes are tracked so your control choices stay meaningful.

Vendor limits

Service providers that host, route payments or process support cases receive limited data for assigned tasks. Contracts require confidentiality, access control and deletion or return when work ends.

Regional wording

Pakistan-specific payment names, support hours and identity steps are checked against current operations. We avoid copying generic legal text that would not match your account journey.

Change trail

Policy edits are logged with the reason for the change. That trail helps us answer privacy questions and show why a section was added, changed or retired.

Aligned across our legal pages

Our Privacy Policy sits beside our cookie, account and transaction terms. Each page uses the same account definitions, but this page stays focused on personal data and how...

Account terms
Account terms explain eligibility, access rules and conduct. This Privacy Policy explains the data behind those steps, such as identity details, login records and contact preferences.
Cookie page
The cookie page lists browser tools and session signals. This policy explains why those signals exist, how long we may keep them and how they support account security.
Transaction terms
Transaction terms cover wallet movement and processing rules. This policy covers related personal data, including reference IDs, timestamps and payment names used to match account activity.
Security terms
Security terms describe login checks and account protection steps. This policy explains the data used for those checks, including device markers, IP patterns and verification outcomes.
Support terms
Support terms explain service channels and response handling. This policy explains how chat records, email threads and call details may be stored to resolve your request.
Promo terms
Promo terms set rules for offers shown inside your account. This policy explains how eligibility data, opt-in choices and message preferences are handled without exposing unrelated records.
Withdrawal checks
Withdrawal terms cover processing steps and verification. This policy explains why we may keep identity, wallet and risk-check records after a transaction has been completed.
PAGE SIGNALS

Visible cues inside this policy

We designed this Privacy Policy so you can scan the parts that matter before opening an account. The headings, badges and contact routes point to practical data questions...

Plain headings Section headings use everyday account language, such as data collection...
Local context Pakistan payment names appear only where they help explain data...
Request paths Contact routes are placed near the policy text so you...
Retention cues Where we mention storage, we explain why records may be...
Security cues The policy names the practical safeguards around account data, including...
Choice cues Where choices are available, the policy points to account settings...

Common privacy questions answered

We collect contact details, login credentials, device signals, identity-check data where needed and account activity records. This lets us create your account, protect access and meet operating duties.

No. We only use payment references needed to match account activity, such as wallet name, transaction reference and timing. Never share wallet PINs or one-time codes with support.

Cookies help keep you signed in, remember language choices, protect sessions and measure page performance. Some are needed for account security, while optional tools may be managed through controls.

Yes. Contact us from your linked email, phone or account chat and tell us what you need. We may verify your identity before sharing or changing any record.

We keep data for as long as needed for account service, security checks, disputes, legal duties and audit trails. When records are no longer required, we remove or anonymise them.

Access is limited by role. Support, payments, security and compliance staff see only the records needed for their task, and sensitive cases are handled through controlled queues.

We update the page date or policy text when material changes are made. For important privacy changes, we may also show an account notice or send a message.