LEGAL REFERENCE

How michezo bet Handles Your Account Data

Your account here comes with a data commitment we treat as part of the product itself. This page sets out what we collect when you register from Pakistan...

Account data onlyLocal wallet referencesAccess on requestCorrections honouredSupported regions only
michezo bet How michezo bet Handles Your Account Data

What We Collect And Why We Keep It

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

REACH THE DESK

Ways To Reach Our Data Desk

Data questions deserve a real person, so they route through the same desk that handles your account every day. Chat is staffed...

Live Chat Open chat from your account and an agent...
Email Desk Write to our privacy mailbox with your account...
In-App Form The contact form inside your account attaches your...
WHY YOU CAN RELY

Who Writes And Checks This Page

This page is drafted and kept current by the same team that runs accounts, payments and support, not by an outside writer. Every clause is checked against how our systems actually behave...

Written In-House

Our operations team drafts each clause, so the wording matches the screens you actually see when you open your account and move money around.

Checked Before Publishing

A compliance owner signs off every update, comparing the text against current wallet rules that apply in Pakistan and in supported regions.

Dated Versions Kept

We store older dated versions of this page so you can see what changed and when, without asking support to dig through previous copies.

Plain Language

We skip legal filler and write in clear English, so you can read a clause once and understand what it means for your own account.

Data Minimised

Forms ask only for what a payment or a verification actually needs, and unused fields are removed rather than left sitting in our systems.

Desk Hours Listed

Chat and email windows are published near this page, so you know exactly when a real person will read your data question and answer it.

How This Page Fits Our Other Documents

This page sits alongside our other documents instead of repeating them. Account rules live under terms of use, browser storage sits in the cookie notice, and wallet timings...

Terms Of UseAccount rules, age requirements and suspension grounds sit there. It sets the contract, while this page explains what happens to your personal data.
Cookie NoticeBrowser storage, analytics tags and consent choices are described there. This page covers the account data those tools feed into our systems.
Wallet ClausesJazzCash, Easypaisa, SadaPay, NayaPay and Raast timings, provider-set limits and refund paths live there rather than inside this page.
Account SecurityPassword rules, one-time codes and device checks are grouped there, keeping the steps you follow separate from the data clauses you read here.
Closure StepsHow to ask for account closure and what we remove afterwards is set out beside this page, matching the retention wording you read above.
Offer TermsAny running offer carries its own eligibility wording and expiry there. That page handles the campaign; this one handles the data it collects.
Complaints RouteIf an answer does not satisfy you, the complaints page lists escalation steps and response windows, kept in step with this policy.
HOW THIS PAGE READS

Visible Elements That Shape This Page

The layout here is deliberate. A short summary strip sits at the very start so you can skim before reading clause by clause, headed blocks carry anchor links...

Summary Strip The opening block lists the main points in plain lines...
Anchored Blocks Each heading links straight to its clause, which means you...
Wallet Context Local names such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast...
Plain Headings Titles describe what sits inside each block rather than using...
Visible Contact Block Chat, email and the in-app form are repeated near the...
Version Marker A short line near the start shows which revision you...

Questions About Your Data Answered

Your name, contact number, region and the wallet references tied to JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Device details are logged only to keep your login safe and spot unusual access.

Only with payment providers and verification partners that a transaction requires, and only the fields they need. We do not sell personal data and we do not pass it to unrelated advertisers.

Verification files are archived once checks close, while wallet references stay for the period financial rules require. Contact preferences are deleted far sooner, since nothing obliges us to hold them.

Yes. Message the desk through chat or the in-app form and we gather everything sitting against your account, then send a readable summary to your registered email inside the stated window.

We delete anything we are not required to retain and send written confirmation once that finishes. A small set of transaction references stays on file because financial rules oblige us to keep them.

Change your contact preference inside account settings and campaign messages stop. Service notices about logins, withdrawals and policy changes keep arriving, because your account genuinely needs them.