Terms of Use
Contract wording on the terms page follows the same structure as this privacy policy, so obligations and data promises sit side by side. Read one and you understand the other.
LEGAL REFERENCE
Privacy Policy for Your mle bet Account
Your personal data, login records and payment details sit behind one privacy policy at mle bet. Open an account and this page sets out what we collect, why...
What we collectWhy we hold itWho can see itYour request rightsPolicy updates
How This Policy Applies Where Local Law Permits
Our privacy policy is written for people who hold mle bet accounts from Pakistan, and it applies wherever local law permits those accounts. We keep one policy for the whole platform instead of separate documents per product, so the same rules cover your casino wallet, sportsbook balance and slot sessions. Where a region's rules ask for more than we describe here, those
local requirements come first. That is why some sections read differently depending on where you sign in, and why we date every update. Payment references such as JazzCash, Easypaisa, SadaPay and Raast appear throughout because those rails create account records we must hold and protect. Nothing on this page overrides a legal duty that applies to us in a supported region.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE WORK
What Keeps Our Privacy Policy Accountable
This privacy policy is drafted by the team that runs mle bet day to day, so every clause matches something we actually do with account data.
Plain-Language Drafting
We write in short sentences and skip legal padding, because a policy you cannot read is a policy you cannot rely on. Each paragraph answers one question about your account data.
Version History
Every change to this page is dated and older versions stay on file. If we widen what we collect, the new wording appears here before it takes effect on your account.
Named Data Controller
The company behind mle bet is named here, with the address policy notices should reach. You always know which legal entity holds your data and who to write to.
Retention Schedule
We list how long each record type is kept, from chat logs to wallet statements, and why that period is needed. Where local rules demand a longer hold, we say so.
Third-Party Register
Any outside service that touches your data, from payment processors to hosting, is listed with the reason we use it. We do not hand your details to advertisers.
Internal Audits
Our team checks the policy against real platform behaviour every quarter, comparing what we promise in writing with what our systems log. Gaps get fixed and the page changes.
POLICY CONSISTENCY
How Our Policy Pages Stay Consistent
Every policy page on mle bet uses the same definitions, so a phrase such as account data carries one meaning across this page, our terms of use and our cookie page.
Cookie Policy
Device identifiers, session cookies and preference storage are described on the cookie page using the same categories you see here, so nothing hides behind a different label, and each entry stays traceable.
Account Rules
Rules covering how you sign in, how we verify you and when an account is closed link back to the data clauses on this page, so the two documents stay consistent.
Payment Terms
Wallet wording for JazzCash, Easypaisa, SadaPay and Raast matches the data descriptions here, so a transaction record reads the same way on both pages and never changes meaning.
Security Practices
The safeguards described on this policy are repeated in the same order on the security page, from password handling to how we log sign-in attempts. Neither page contradicts the other.
Contact Page
Support routes listed there mirror the privacy contacts on this page, so a request about your data reaches the right desk instead of a general queue. Same address, same response windows.
Sportsbook Rules
Competition and settlement wording shares this page's definitions of account data, so a wager record and a wallet record are never described in conflicting ways. One vocabulary across the platform.
INSIDE THE PAGE
What You See on This Privacy Policy Page
The page you are reading is built for quick scanning: a short summary near the start, then the fuller clauses for anyone who wants them, with your data...
Summary Strip
A short band near the start lists the things most...
Data Categories Table
One table groups the record types we hold, from account...
Local Currency Labels
Amounts show in Rupees with the wallet rail named, so...
Region Wording
Where a clause only applies to some markets, we say...
Updated Stamp
A date sits under the page heading showing when the...
Contact Footer
The footer repeats the mailbox and chat routes for privacy...
Questions You Ask About Your Data
We hold what you hand us when you open an account, what your activity generates, and what payment rails return to us: name, contact details, wallet references, sign-in logs and session records.
No. We do not trade your data, and we do not pass it to advertisers. Sharing happens only with processors who help us run the platform, such as payment and identity partners.
Each transfer creates a wallet entry with the rail name, amount and reference number your provider returns. That record sits in your account history and our team checks it during a balance query.
Yes. Open your account settings to update contact details, or write to the privacy mailbox if a field is locked for verification. We confirm the change in writing once it is applied.
Retention depends on the record. Chat logs and sign-in data are held for shorter periods than wallet and verification records, which stay for as long as local rules in your region require.
Access is limited by role. Support agents see what they need to answer your query, while a smaller team handles wallet and verification checks. Every lookup is logged against the staff account.
Write from the email address on your account and ask for a copy of your records. We verify that the request comes from you, then send the file in a readable format.