Privacy Policy for your 400mb account
Live baccarat, Andar Bahar, crash rooms, slots and sportsbook markets create account records that deserve clear handling. This Privacy Policy explains what 400mb collects, why we need it...
How we handle your data
400mb treats privacy as part of the account flow, not as a hidden afterthought. We collect details needed to create your account, check access, process wallet activity, answer support requests and protect the lobby from misuse. That may include your name, phone, email, device signals, session logs, game records, payment references and messages you send us. We use these records where local
law permits, including supported regions in Pakistan. We keep data for the period needed for service, legal, security and dispute handling, then remove or anonymise it when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How this policy stays accurate
We keep this Privacy Policy connected to real 400mb account processes. When account forms, wallet checks, support scripts or security tools change, the policy is checked against those flows so the wording...
Named data categories
The policy describes account details, wallet references, device signals, game records and support messages separately. Clear categories help you see why each record exists and which privacy request fits your concern.
Local wallet context
JazzCash, Easypaisa, SadaPay and Raast references can appear in transaction records. We use them to match account activity, resolve disputes and confirm payment status without exposing extra wallet data.
Access checks
Login time, device type, browser signals and location hints help us detect unusual access. These records support account protection and are handled under privacy controls instead of public lobby content.
Support record handling
Messages sent to chat or email may be stored with your account case. We use them to answer privacy requests, track consent, correct mistakes and resolve account disputes.
Retention controls
Some records must stay for security, accounting or legal reasons. When those reasons expire, we aim to delete, anonymise or separate data from your account identity.
Policy checks
Before policy wording changes, we compare it with account forms, payment screens and support tools. That keeps the text grounded in the way 400mb actually handles data.
Aligned privacy pages across 400mb
Privacy wording should not clash from one legal page to another. We align this page with cookie use, account terms, promotional messaging and support language so you can...
Privacy page elements you can scan
This page is arranged so you can find the privacy point that matters before opening an account or changing account details. Each visible element explains a...
Plain collection summary
We state the main data categories near the start: account details, device signals, wallet references, game records and support messages. That lets you understand collection before reading deeper sections.
Local context chips
Short chips name Pakistan access and wallet references such as JazzCash, Easypaisa, SadaPay and Raast. They show where local privacy questions usually connect with account records.
Request routes
Support cards show which contact path fits data access, correction, deletion or security concerns. Clear routing reduces repeat messages and helps us verify your identity with care.
Retention wording
Retention language explains why some account records stay longer than others. Security, accounting, dispute handling and legal needs are separated so you can see the reason for storage.
Sharing explanation
Where service partners help with streaming, payment status or technical hosting, the policy explains the privacy purpose. We avoid selling personal data as part of 400mb account handling.
Choice markers
Privacy choices are shown around contact preferences, cookie settings and account requests. These markers help you decide what to change, what to ask for and which records may remain.