Reference

Privacy Policy for your account

We keep this privacy policy focused on the records tied to your account, device, and payment trail, so you know what we handle from the start.

Account dataCookie usePayment recordsIndia access

Browse games Read FAQ

How this policy works in India

mainbazar Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This policy applies to account records created on mainbazar from India, and from any other place where local law permits access. If local law needs a different treatment for a particular record, we follow that rule to the extent the law applies. We collect what is

1
needed to create your account, confirm your sign-in, handle UPI, Paytm and PhonePe transaction references, answer service messages, and keep the system working. We may also store browser, device, and session details so we can spot duplicate logins, stop misuse, and correct errors. We do not
2
ask for extra records unless a legal duty, a support case, or your own request makes them necessary. Where a payment flow needs a retry or a reversal check, the record stays in the same file as the transaction so we can trace it without asking
3
you to resend the full history.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

HELP ROUTES

Contact paths for privacy requests

If you want a copy of your stored records, a correction, or a check on how we handled a consent choice, use the account help form or the contact route shown in…

Registered address reply Reply from the email address linked to your account when you want a copy, correction, or deletion check. That lets us match the request to the right record without asking for a long back-and-forth.

Account help form Use the form inside your account if you want a privacy request logged in writing. Tell us which record needs attention, and add the date or screen reference if you have it.

Live chat When chat is open, you can raise a privacy question and ask for the right contact route. We may still move the request to a written channel if it needs verification.

DATA CARE

How we handle data day to day

We handle account data in layers: what you enter, what our systems log, and what our payment records show. Cookies keep sessions steady, while login checks protect the account from misuse.

Account records

We store the profile, contact fields, login timestamps, and other records needed to run your account and answer your requests. Each file is tied to the same account history so we can act on corrections without confusion.

Cookie records

Cookies help us keep your session active, remember basic preferences, and reduce repeat checks while you move through the site. They also help us spot unusual activity that may need a closer look.

Login checks

If a sign-in looks unusual, we may ask for a quick check before access continues. That step protects your account record, your messages, and any pending service action from misuse.

Payment trails

UPI, Paytm, PhonePe, and Google Pay records are used only for reconciliation, support, and legal duties. We keep transaction references and status fields, not the extra details we do not need.

Retention

We keep records only for the period needed for service, support, accounting, dispute handling, or a legal requirement. After that period, we remove or de-identify them where our systems allow it.

Change requests

To request a copy, correction, or deletion, contact us from the address linked to your account. We may ask a short set of checks before we act so the right file is changed.

Privacy questions you may ask

These answers cover how we collect, store, use, and correct records tied to your account. If local law gives you a stronger right, we follow that rule to the extent it applies. For anything not covered here, send a message from the address on your account so we can match it to the same file and reply with the right next step. If you need a fast change, include the account name and the last action you remember.

We keep the details you enter for the profile, sign-in, and support flow, plus device and session logs that help us secure the account. If you use a payment rail, we also keep the transaction reference and status.

Cookies help us remember your session, language choice, and basic security checks. They also make it easier to spot repeated sign-ins from the same device and keep the page working without constant reloading.

We only share records with service partners that help us run support, payments, fraud checks, or legal duties, and only to the extent needed. We do not hand out your records for unrelated use.

We keep it for the time needed for the account, support, accounting, dispute handling, or a legal duty. Once that purpose ends, we remove or de-identify the record where our systems and the law allow.

Yes. Send the request from the address linked to your account and tell us which record needs attention. We may ask for a short verification step before we release a copy or make a change.

If your contact details change, send the update through the account channel so we can confirm the old and new details. That helps us keep receipts, alerts, and privacy replies tied to the same file.

It applies where local law permits access, and we may adapt parts of it to meet local legal needs. If a region has a different rule, we follow that rule to the extent it applies.

Privacy Policy for your account

Contact paths for privacy requests

How we handle data day to day

Account records

Cookie records

Login checks

Payment trails

Retention

Change requests

Privacy questions you may ask

01 What records do you collect when I open an account?

02 Why do you use cookies on the site?

03 Do you share my records with others?

04 How long do you keep my data?

05 Can I ask for a correction or a copy?

06 What if I change my phone or email?

07 Does this policy apply outside India?

Related Pages