Reference

Open your account with clear privacy terms

When you open an 8mm account, we explain how your profile details, device signals, game activity and UPI, Paytm or PhonePe records are handled.

Account dataCookie choicesUPI recordsPrivacy requests
8mm Open your account with clear privacy terms
CONTACT ROUTES

Check privacy contact paths

Privacy questions should reach the team that can trace your account securely. Before we discuss account data, we may ask for identity checks so we do not share details with the wrong…

Account privacy mailbox Email us from the address linked to your account and mention whether you want access, correction or deletion help. We use the mail trail to verify ownership before sharing account-related data.
In-account help desk After sign-in, open the help area and choose the privacy topic. This route lets us match your request with your profile, device record and recent account activity without extra back-and-forth.
Payment record queries For UPI, Paytm, PhonePe or Google Pay privacy queries, share only the transaction reference and date. Do not send full bank details, card images or unrelated personal documents.
POLICY CARE

Browse our data care practices

Our privacy work focuses on account access, wallet records, game activity and support history.

Data we collect

We collect details you provide, such as name, email, phone and account settings, plus technical records like device type, IP address, browser data and sign-in timestamps used for security checks.

Cookie handling

Cookies help keep you signed in, remember language choices and measure page performance. Some cookies are needed for account safety, while optional analytics can be managed through your browser settings.

Wallet privacy

UPI, Paytm, PhonePe and Google Pay references are used to match account payments, detect mismatches and resolve support cases. We store transaction references, not unnecessary banking material.

Account security

We use verification steps, session checks and access logs to reduce unauthorised account use. If we notice unusual sign-in behaviour, we may ask for extra checks before discussing personal data.

Retention approach

Some records must stay for payment reconciliation, fraud prevention, dispute handling or legal duties. When those reasons no longer apply, we remove personal identifiers or delete the record where possible.

Change requests

If your name, phone, email or payment reference is wrong, contact us with the correct detail and proof of account ownership. We assess each correction request before updating stored records.

Discover answers on privacy rights

These answers explain how privacy requests work on your account. They cover data access, correction, cookies, payment references, retention and contact steps. For any request involving account data, we first confirm that the request comes from you or from someone lawfully allowed to act for you.

We collect data needed to create and operate your account, including contact details, login records, device signals, payment references, game activity and support messages. We avoid asking for documents unless verification or law requires them.

Payment references help us match deposits or withdrawals to your account, handle failed transfers and respond to wallet queries. We use the reference, date and amount context rather than storing unnecessary banking material.

Yes, you can request a copy of eligible personal data linked to your account. We will verify your identity first, then provide data that can be shared under applicable law and security rules.

Contact us through the account help area or linked email and state what is wrong. We may ask for proof of account ownership before correcting your name, phone, email or payment reference.

We keep records while your account is active and for periods needed for security, payment checks, disputes or legal duties. When retention is no longer required, we delete or anonymise eligible records.

Cookies support sign-in, account safety, language choices and page measurement. Essential cookies are needed for core account functions, while optional analytics can usually be controlled through your browser privacy settings.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests are handled under applicable rules, and some records may be retained when law requires it.