LEGAL REFERENCE

Your data rules at 77 slots

77 slots explains how we collect, use, store and protect your account data when you open an account, enter the lobby, verify access, or request a payout where...

Pakistan privacy scopeAccount data usePayment record careRequest channels
Explore the Lobby Read FAQ
77 slots Your data rules at 77 slots

How this policy applies in Pakistan

This Privacy Policy applies to 77 slots activity on 77slots.win for Pakistan supported regions where local law permits. We collect only the data needed to create and secure your account, run identity and access checks, process privacy requests, record payment events, and keep account history accurate. When you use JazzCash, Easypaisa, SadaPay or Raast, we store transaction references and verification status, not

unnecessary wallet secrets. We may share limited records with service providers who help with hosting, fraud checks, support tooling, analytics, and payment routing. We keep privacy handling tied to account safety, payout checks, dispute handling, and legal record duties, then remove or limit data when it is no longer needed.

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

CONTACT ROUTES

Privacy requests and response paths

Need something changed or explained? Send us the privacy request that fits your account. We will ask for enough detail to confirm...

Email privacy desk Use email when your privacy request needs documents...
Live chat handoff Open chat for quick privacy checks such as...
Account request form Use the in-account form for access, correction, or...
DATA CHECKS

Checks behind this privacy wording

We write this policy from our own account flow, not from a template detached from 77 slots. Each point connects to a real step: login, verification, payment reference checks, support contact, device...

Access logs

We record login time, device signals, and session status to help spot account misuse. These records support privacy and security checks without exposing more personal detail than needed.

Payment references

JazzCash, Easypaisa, SadaPay and Raast activity is linked to transaction references, status messages, and account ownership checks. We use those records for support, reconciliation, and dispute handling.

Verification handling

When we need proof for account safety or payout checks, we store it in restricted areas. Access is limited to trained staff handling privacy, risk, and support duties.

Policy maintenance

We check this page when account tools, support routing, or payment flows change. The wording is updated so your privacy choices stay connected to the live service.

Regional wording

Because Pakistan access depends on supported regions and local rules, this policy uses careful wording. We avoid promises beyond what our account process and service providers can support.

Support records

Your support messages may be kept with timestamps, agent actions, and resolution status. That helps us answer follow-up privacy requests without rebuilding the same case again.

Aligned privacy pages across our site

Our Privacy Policy sits beside other legal pages, but it has its own job. It explains data handling only. We keep language consistent across connected pages so your...

Account terms
Our account terms explain how you use 77 slots. This policy explains what data sits behind that use, including login records, verification status, and support messages.
Cookie page
The cookie page covers browser tags and device storage. This policy explains how those signals may connect with account security, preferences, analytics, and session management.
Bonus rules
Promo rules may mention eligibility checks. This policy explains the data side of those checks, including account status, location signals, and record accuracy where local law permits.
Payment help
Payment help explains transaction steps. This policy explains privacy handling around those steps, including wallet references, status logs, reconciliation checks, and support follow-up records.
Security page
Security wording focuses on keeping access safe. This policy adds how we collect and retain device signals, login alerts, password reset events, and contact history.
Complaint route
If you raise a complaint, we may need chat, email, payment, and account records. This policy explains how those records are gathered and handled.
Account closure
When you close your account, some records may still be kept for legal, payment, or dispute duties. This policy explains why retention may continue.
PAGE SIGNALS

Privacy page signals you can see

We built this privacy page to be easy to check before you join and easy to revisit later. The visible layout separates collection, use, sharing, storage, rights, and...

Clear section labels Each heading names the privacy subject before the paragraph begins...
Local context chips We show Pakistan payment rails as context chips because they...
Plain request language Rights requests are described in direct account terms: access, correction...
Retention cues Retention points explain why certain records stay after account changes...
Safety markers Security markers show where device, login, and verification records fit...
Contact placement Privacy contact routes appear before the long policy details end...

Privacy questions before you join

We collect account details, contact data, login records, device signals, and verification status. We use them to run your account, protect access, process requests, and keep records accurate.

No. We do not ask for wallet passwords or private codes. We keep transaction references, status messages, and account matching records needed for payment support and reconciliation.

Yes. Send a privacy request through email or the in-account form. We may verify ownership first, then provide the account data we can lawfully share with you.

Retention depends on the record type. Some chat or login records may be short term, while payment, dispute, security, or legal records may need longer controlled storage.

Only staff or service providers with a direct need should access it. We restrict privacy cases to support, risk, payment, or technical teams handling the request.

This page is written for Pakistan supported regions where local law permits. If access rules or service availability differ by location, privacy handling may also follow local requirements.