Mahadev Book Privacy Policy – Your Data & Rights Explained

The Principles First

Responsible data practice on the mahadev book platform rests on four commitments: collect only what is needed — for operating your account, meeting legal obligations, preventing fraud and improving the service; use it only for stated purposes, with no silent repurposing; protect it seriously, with encryption, access controls and retention limits; and tell you the truth about all of it, in language a human can actually read.

What Is Collected — and Why Each Piece Exists

The information you provide: registration details — name, mobile number, date of birth — create your account and verify your identity and age. Identity documents — Aadhaar, PAN, passport or driving licence — are required by KYC and anti-money-laundering law; without them, full accounts cannot legally operate. Payment information processes deposits and withdrawals and confirms that payment methods belong to you. Your support communications are kept to resolve disputes and maintain service history.

The information your use generates: betting and gaming history operates your account, settles markets, calculates loyalty benefits and enforces the responsible-gaming limits you set. Transaction records meet accounting and legal obligations. Device and technical data — device type, IP address, session logs — serve security, fraud detection and compatibility. Usage analytics, aggregated and anonymised where possible, improve the product.

The honest framing: a betting platform cannot operate without most of this data, and the measure of a platform is not whether it collects — it must — but whether it collects the minimum, states the purposes plainly and honours them.

How Your Data Is Used

Operating your account — registration, verification, wallet, bets and withdrawals. Legal compliance — KYC and AML obligations, tax and accounting requirements, responses to lawful authority. Fraud prevention — multi-account detection, payment screening, account-takeover prevention. Responsible gaming — enforcing your limits and detecting concerning patterns. Service improvement — analytics and feature development. And communications you consent to — service notices always, marketing only with your consent and always with an opt-out.

What responsible use never includes: selling your identity data to unrelated parties, or using verification documents for marketing. Ever.

Retention, Protection, Cookies and Your Rights

Retention follows need and law: account data for the life of the account plus a defined period, identity documents only as long as legal KYC obligations require, transaction records for mandated accounting periods, and marketing consent until you withdraw it. When data is no longer needed it is deleted or irreversibly anonymised — retention is a rule, not an accident.

Protection runs on encryption in transit and at rest, strict access controls — verification documents receive the tightest handling — continuous monitoring for anomalous activity, and documented breach-response procedures. Your side of the partnership matters equally: strong unique passwords, OTPs never shared, and logouts on shared devices are protections only you can provide.

Cookies are small files the site stores on your device: essential cookies carry login sessions and security tokens; functional cookies remember choices like odds format; analytics cookies gather anonymised usage statistics; marketing cookies, where used, require your consent and are manageable through cookie settings and your browser. Blocking essential cookies breaks the platform the way removing wiring breaks the lights — but the choice is documented and yours.

Depending on your jurisdiction's data-protection framework, you may hold rights of access, correction, deletion, portability, objection and complaint. Exercise them through the mahadev book support channel with account identification; requests are handled per the applicable law of your region. And betting is strictly 18+: age verification at onboarding, no marketing to minors, and immediate closure and data deletion where an underage user is identified.

The Journey of a Verification Document

Players submit identity documents with understandable hesitation, so the lifecycle deserves plain description. Your document enters the verification system through an encrypted upload, is stored with the strictest access tier the platform operates, and is used for exactly one comparison: the details against your registration. It becomes visible only to the compliance personnel whose function requires it, is excluded from marketing systems entirely, and is deleted or anonymised when the legal retention window closes.

The contrasts that worry players — data brokers, resale, aggregation — are the behaviours of illegitimate operators, and the privacy policy plus licensing posture of a platform is precisely where those behaviours are excluded in writing. The practical guidance: submit documents through the platform's verification flow only, never through chat or email channels, and treat any "agent" requesting documents by message as the fraud it is.

Cookie Management, Practically

Cookie settings are a real privacy control, and managing them takes two minutes. Essential cookies — sessions, security, preferences — stay enabled; blocking them breaks the platform the way removing wiring breaks lights. Analytics cookies can stay if you are comfortable with anonymised usage statistics improving the product, or go if you prefer minimal footprint — the choice is genuine. Marketing cookies are the advertising layer, and players who dislike targeted promotion should disable them and unsubscribe from marketing consent in the same sitting, since the two together close the loop.

The browser-level habit completes the control: periodic cookie clearing logs you out everywhere, which is a minor inconvenience that also ends every stale session on every site you visit. Once a month is a reasonable rhythm, performed with the same energy as any other digital hygiene.

Exercising Your Rights, Step by Step

Data rights are practical tools, and using them follows a fixed sequence. Identify yourself through the support channel with your account details — the same verification that protects your money protects your data. State the request plainly: access to the data held, correction of a specific inaccuracy, deletion where no legal retention applies, or withdrawal of marketing consent. Expect proportionate handling — access requests compile within the statutory window, corrections reflect quickly, and deletions respect the accounting and KYC retention periods the law imposes.

Two practical notes: corrections matter most at registration (a mismatched name costs far more in friction than the two minutes of fixing it early), and marketing withdrawal is immediate, applying to channels you no longer wish to receive. The rights are only as strong as their use — the mechanism exists, costs nothing, and responds.