LEGAL REFERENCE

How Your Details Move Through mahadev app

Open an account and you hand us a short list of things: a mobile number, a payment handle, the handset you play on. This page spells out what...

Mobile number at sign-upPayment rails named, never resoldYour play history stays yoursDeletion requests get answered
Explore The Lobby Read FAQ
mahadev app How Your Details Move Through mahadev app

What We Collect and Why It Stays

An account needs a mobile number for sign-in codes, a name and date of birth for age and identity checks where local law permits, and a record of every transaction you push through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Device data — handset model, IP range, app build — tells us when a login does not look like yours. Play history exists

so you can trace your own session and so our team can settle a query without guesswork. Retention shifts with supported regions: transaction records stay while a payment dispute could still surface, then they are archived or wiped. You can correct your details whenever you like, ask for a copy of what we hold, or request erasure of anything we no longer

need for settlement or a legal obligation.

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

POLICY HELP DESK

Where to Take a Data Question

Nobody should have to hunt for a way to ask about their own data. Our desk reads every policy query that lands...

Live Chat Open live chat from the app footer and...
Policy Mailbox Send your request to our policy mailbox with...
In-App Help Hub Inside your account sits a short help hub...
WHY THIS POLICY

How We Keep the Wording Straight

Policy text drifts when nobody owns it. One writer keeps this page, a second reads it before anything goes live, and every change carries a date so you can see what moved...

Plain Language Write-Up

We turn legal phrasing into sentences you can act on. If a clause needs three readings before it makes sense, it gets another pass before it goes live.

Change Dates Kept

Every edit carries a date and a one-line reason at the foot of the page, so you can tell whether a rule that applied when you signed up has since moved.

Second-Pair Check

A second writer, separate from the author, checks each revision against the live product before publication, which catches rules we drafted ahead of the app.

Fields Kept Minimal

We add a field only when the product genuinely needs it. New collection routes go through the same write-up before they ever reach your sign-up screen.

Local Rail Wording

Cash-in and payout clauses name JazzCash, Easypaisa, SadaPay, NayaPay and Raast directly, so you can map a policy line onto a rail you actually use.

Someone Answerable

A named team owns policy queries and reports how many were closed each month. Questions that need a rules call are escalated rather than parked in a queue.

Where This Page Sits in the Set

This page runs alongside the other public documents on mahadev app, and you should be able to read any two of them without finding a contradiction. When an...

Account Terms
Sign-up, sign-in and closure rules live on the terms page. Anything about why we ask for a detail at onboarding points back here rather than repeating itself.
Cookie Page
Device identifiers and browser tags are listed on the cookie page. That page handles what sits on your handset; this one handles what reaches our servers.
Withdrawal Page
Payout timing, verification and the rails we use, including JazzCash, Easypaisa, SadaPay and Raast, sit beside the data we keep to run that check.
Offer Conditions
Each promotional run carries its own conditions. Where an offer needs account data, the wording here governs how long we retain it after the run closes.
Security Page
Password practice, device binding and session handling are set out on the security page. This page explains the logging that sits behind those protections.
Help Centre
Common how-do-I questions are answered in the help centre. If a question drifts into what we collect and why we keep it, it is rewritten here instead.
Contact Page
Phone, chat and email routes are listed on the contact page with hours. Policy questions sent through any of them reach the same desk and the same owner.
ON THE PAGE

The Blocks You See Here

A long policy reads better when you can jump around inside it. We keep the same page furniture on every clause, so you can reach the part about...

Jump Bar A short jump bar sits under the headline and links...
Version Date Row The current version date sits above the first clause, and...
Question Block Short answers to the questions our desk fields most, written...
Contact Chips Chat, email and in-app help chips sit at the foot...
Version Shelf Older versions of this policy are kept on a small...
Print View A single-column print view strips the furniture and runs the...

Questions About Your Data

A mobile number, your name and date of birth, the payment handle you use, a device fingerprint for each sign-in, and your play and transaction history. That is the working set.

Payment rails need a transaction reference to move money, and where local law permits a regulator may request a record. We do not sell account data to advertisers or brokers.

Ask through live chat, the policy mailbox or the in-app help hub. We verify the account, then send a file listing the fields we store and the dates attached to them.

Where local law permits, yes. Anything we no longer need for settlement, fraud checks or a legal duty comes out. A closed account keeps a skeleton record while a dispute could still surface.

Payouts move money out, so we match the name against the account holder and check the rail, whether that is JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Cash-ins need less.

Long enough to answer a dispute or satisfy a local requirement, which varies by supported region. After that window the record is archived, then wiped from the live systems your account touches.