Reference

Privacy Policy for your account data

madhurmatkano1 sets out how we collect, use, store and protect your account data when you open an account, enter the lobby, use UPI, Paytm or PhonePe, and contact…

Account dataUPI contextCookie choicesSupport requests
madhurmatkano1 Privacy Policy for your account data
CONTACT ROUTES

Three ways to raise privacy requests

If you want to access, correct or ask about your data, contact us through the same account details you use with the lobby.

Account privacy email Use the privacy email channel for requests about stored account data, correction of profile…
Live chat record check Open chat from your account when you need a faster privacy status check.
Payment reference help For UPI, Paytm or PhonePe privacy questions, share the transaction reference without sending full…
DATA HANDLING

Six privacy controls we apply

Your privacy settings sit alongside account security, cookie handling and wallet checks. We keep only the records needed for account operation, legal duties, dispute handling and safety checks.

Account data collection

We collect data you provide during account opening, login and profile updates, including contact details and verification records.

Cookie and device data

Cookies help us remember login sessions, detect suspicious access and understand page errors.

Game activity records

When you open Roulette, Holi Festival, Bingo or Fishing God, we keep activity records linked to your account for disputes…

Payment data care

UPI, Paytm, PhonePe and Google Pay references are stored with transaction status, time and account link.

Retention and deletion

Some records are kept for legal, tax, security or dispute timelines, even after you ask to close an account.

Correction requests

If your name, mobile number or payment reference is wrong, ask us to correct it through support.

Answers about your privacy rights

These answers explain how we handle common privacy requests on madhurmatkano1. They focus on account data, payment references, cookies, retention and contact routes. If your request involves access from a specific Indian state or region, we may need to check local law before changing access or records.

We collect details needed to create and protect your account, such as name, mobile number, login records, device signals, payment references and KYC records where required. We also keep support messages linked to your requests.

We use payment references to match deposits, process withdrawals, check disputes and maintain account records. We do not ask for PINs or full banking credentials, and those should never be shared in chat.

Yes. Send the correction request through your account email or chat, then complete any ownership check we ask for. Some edits may be limited when the record is tied to payments, KYC or legal duties.

We keep data for as long as needed for account operation, disputes, security checks, tax or legal duties. When a record is no longer needed, we remove it or reduce its link to your identity.

Cookies store session, preference and security signals. You can clear or block them in your browser, but login checks and account safety prompts may return because we still need to confirm authorised access.

Only team roles that need the request can view it, such as support, verification or security staff. We limit internal access and may mask sensitive payment or identity details when full visibility is not needed.

We share limited data with payment, verification, security, hosting or legal partners when required to run your account or meet duties. Each sharing step is tied to a specific purpose, not broad resale.