Privacy Policy for your m16 account
m16 puts live casino, slots and sportsbook account data under one Privacy Policy, so you can see how sign-in, KYC, wallet and support records are handled before you...
How we handle your privacy rights
This Privacy Policy sets out how we collect, use, store and share data linked to your m16 account in supported regions of Pakistan where local law permits. We collect details you provide during account opening, sign-in security, KYC checks, wallet activity, game-session logs, device signals and messages you send to support. We use these records to run your account, verify withdrawals, protect
access, handle disputes, meet legal duties and improve policy clarity. We keep records only for the period needed for account service, security, tax, fraud prevention or lawful requests. You can ask us to access, correct or delete eligible data, and we will explain any lawful reason that limits a request.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact routes for privacy requests
Privacy requests need a clear path, so we keep them separate from general lobby chat. When you contact us, include your account ID, the request type and a reachable email or phone number. We may ask for extra verification before changing or releasing account data.
Account message
Send a privacy request from inside your m16 account when you can still sign in. This lets us match your message with your account record without asking for repeated identity details.
Email route
If account access is blocked, use the privacy email path shown on m16.im. Include the phone number linked to your account and avoid sending card images unless we ask.
Chat handoff
Live chat can pass a privacy case to the correct team, but it cannot release account data during a casual session. Verification comes first, then we answer through a safer channel.
How we keep the policy current
Our Privacy Policy is maintained by the team that runs account access, wallet checks and support handling. That matters because policy wording must match real data flows. When...
Operational ownership
The same teams that handle KYC, withdrawals and account recovery feed changes into the Privacy Policy, so the wording reflects...
Change log habit
When we alter privacy wording, we keep an internal change record with the clause, reason and date. This helps support...
Access controls
Only approved staff can reach sensitive account records, and access is tied to work duties. Privacy requests are routed through...
Vendor checks
Where service partners help with hosting, verification or payments, we assess the privacy need before sharing account data. We share...
Support training
Support agents are trained to separate privacy cases from normal account questions. They should verify you first, record the request...
Local wording
For Pakistan access, the policy names local rails and supported regions where relevant. We avoid vague wording when a JazzCash...
Aligned wording across policy pages
The Privacy Policy does not sit alone. It connects with account terms, cookie wording and support procedures, but it remains the main page for personal data handling. We...
Visible cues inside this policy
We design this Privacy Policy so you can scan the important privacy points before creating or using an account. The layout separates data categories, reasons for...
Data categories
The policy separates account details, identity checks, wallet records, session logs and support messages. This helps you see which data type is being discussed before reading the full clause.
Reason labels
Each privacy use is tied to a reason, such as account service, fraud checks, withdrawal verification or legal duty. We avoid open-ended wording where a narrower reason is available.
Sharing markers
When a partner may receive account data, the policy explains the service reason. Hosting, verification and payment processing are separated so you can understand the privacy role.
Retention cues
Retention wording explains why some records may remain after an account request, especially where security, tax or dispute records are required. Eligible data can still be requested.
Request path
The policy points you toward access, correction and deletion requests without hiding the verification step. We confirm identity first because privacy rights should not expose your account.
Region wording
Pakistan references are included where they affect account privacy, payment rails or supported regions. Access wording uses where local law permits rather than broad countrywide promises.