Terms page link
Our Terms explain account use, while this Privacy Policy explains the data behind that use, including registration details, login records and support messages.
LEGAL REFERENCE
How a37 handles your data
a37 keeps your account, payment and lobby privacy rules in one clear place before you open your account. This Privacy Policy explains how we collect, use, share and...
Pakistan privacy wordingAccount data usePayment record contextSupport contact paths
Our Pakistan privacy position
This Privacy Policy applies when you use a37.today, create an account, contact our team, complete verification, move through the casino lobby, open sportsbook areas or use supported Pakistani payment rails where local law permits. We collect only the data needed to run your account, process checks, answer your requests, protect access and keep accurate transaction records. That can include your name, contact
details, device signals, login history, payment references, verification files and support messages. We use this data to operate a37, manage security, meet record duties and respond to privacy requests. We do not sell your personal data. When service partners help us with hosting, payment routing, fraud checks or customer support tools, they receive only the data needed for that task.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How we keep policy wording checked
We write this policy from our operating records, not from generic templates. The wording is checked against how a37 handles account creation, wallet references, verification files, support conversations...
Operational source
Our policy wording follows the actual account flow: registration fields, login checks, wallet references, verification screens and support forms used...
Local payment mapping
JazzCash, Easypaisa, SadaPay and Raast records are described as payment references, not open wallet access. We record what is needed...
Access control
Internal access is limited by role, so support staff see only the data needed to answer your request or investigate...
Security logs
We keep login times, device signals and risk markers to spot unusual account behaviour and help protect your profile from...
Correction handling
If your contact details or profile record is wrong, we can update it after ownership checks, while keeping required transaction...
Retention control
We keep records only for account operation, legal record duties, dispute handling and security needs, then remove or anonymise data...
LEGAL MATCH
Aligned across our legal pages
Our privacy wording fits alongside the rest of the a37 legal area. Each page has a separate purpose, but the data handling position stays consistent so you can understand what happens before...
Cookie wording
Cookie wording covers browser storage and site measurement. This policy connects that activity to your wider privacy rights and account data choices.
Payment records
Payment pages may describe JazzCash, Easypaisa, SadaPay and Raast steps. This policy explains the personal data and references held during those flows.
Verification steps
Where identity checks are required, this page explains why documents or profile details may be collected, stored and protected during account checks.
Support records
Help pages explain how to contact us. This policy explains how those messages, attachments and contact details are handled after you send them.
Security alerts
Security wording on account pages may warn about login changes. This policy explains the logs and device signals used to investigate those alerts.
Regional access
Where local law permits access in supported regions, this policy explains how location signals may be used for compliance and account protection.
PAGE MARKERS
What you see on this policy page
This page is laid out so privacy details are easy to scan without losing legal meaning. We separate account data, wallet references, support routes, security logs and your...
Plain headings
Each heading names the privacy task it covers, such as...
Local labels
Pakistan payment names appear only where they help explain data...
Short badges
The badges near the hero summarise the policy areas covered...
Contact cards
Support cards show which route fits each privacy request, helping...
Consistent language
We use the same privacy terms across account, wallet and...
Request focus
FAQ answers are written around practical privacy actions, including access...
Questions about this Privacy Policy
We collect account details, contact data, login records, device signals, payment references, verification files and support messages needed to run your account and protect access.
We use payment references from JazzCash, Easypaisa, SadaPay and Raast to reconcile transactions, answer account queries, detect unusual activity and maintain required financial records.
We share limited data with service partners that help with hosting, payment routing, verification, fraud checks, analytics or support tools, and only for the task assigned.
Yes. Contact our privacy team with your account details and request. We will verify ownership before providing records or correcting profile data linked to your account.
We keep records for account operation, transaction reconciliation, support history, security checks and legal record duties. When no longer needed, data is deleted or anonymised.
We use access controls, security logging, role-based permissions and monitoring of unusual activity. Sensitive requests require ownership checks before records are changed or shared.