Reference

Your Data Choices At 2bhk

Lightning Roulette, Tiger Fury, UPI and Paytm sit behind account journeys where privacy choices must be easy to understand, so this policy explains what 2bhk collects and why.

Account data clarityUPI record handlingCookie choicesIndia law context
2bhk Your Data Choices At 2bhk
CONTACT ROUTES

Privacy Help Without Guesswork

Privacy requests should reach the team with enough account context to identify your profile without asking you to repeat sensitive details.

Email privacy requests Send privacy requests from the email linked to your account, state the change you…
Account chat trail Use signed-in chat for cookie questions, payment reference checks or a quick data correction.
Verification documents If we need documents for a privacy request, upload only what the support screen…
POLICY CONTROLS

Clear Rules For Account Data

Our Privacy Policy is written around the data journeys we handle every day: account creation, login security, cookie choices, game-session logs, wallet activity and support messages.

Account details

We collect account details such as name, contact data, login identifiers and verification status so your profile can be opened, secured and recovered. We do not ask for more than the workflow needs, and these fields support payout name checks.

Cookie choices

Cookies help keep your session active, remember device preferences and measure page performance. You can change browser settings, though some account security checks and wallet screens may work less smoothly after blocking them. You can revisit choices after clearing browser data.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored with timestamps, amounts and status messages. We use them to match deposits, investigate failed transfers and support withdrawal checks. Full wallet credentials are not requested through policy requests.

Security checks

Device signals, IP data and login events help us spot unusual account access. When a risk flag appears, we may pause actions until you complete a verification step. This keeps the data change from reaching the wrong person.

Retention windows

Retention periods depend on the record type. Support chats may be shorter than payment and KYC records, while dispute, tax or legal files can stay until the reason ends. The policy separates these categories so requests get clear answers.

Change requests

You can ask us to correct, export or delete eligible data. We verify the request first, then explain what we changed or why a legal reason requires retention. If only part qualifies, we say so.

Your Data Questions Answered

This section answers the privacy questions we hear most during account setup, payment checks and support conversations. It does not replace the full policy text, but it helps you understand what data is collected, where it goes and how to contact us. If your request depends on local law, we will explain the applicable step before making changes. Keep your account email active so we can verify replies and avoid sending sensitive data to the wrong inbox.

We collect the details you submit, login identifiers, device data, cookie records and verification status. We also keep game-session and wallet references so we can secure the account, match transactions, handle support requests and avoid repeated screenshots.

Yes, limited data may go to UPI, Paytm, PhonePe, Google Pay or payment service partners when needed to process, reconcile or investigate a transaction. They receive only the details needed for that task, such as references and status codes.

Yes. Send the corrected detail through the email linked to your account or signed-in chat. We verify the request, update eligible records and tell you if any legal, payment or security record must remain unchanged.

We keep data according to its purpose. Session cookies may expire quickly, support messages have service timelines, and payment or verification records may stay longer where law, disputes, tax checks or security checks require it.

Cookies keep you signed in, remember preference choices and help us understand page errors. You can manage them in your browser, but some account, security, lobby and wallet functions may require cookies to work.

You can request deletion of eligible data at any time. We first confirm your identity, close open support or payment issues, then remove or anonymise records that no longer need retention and reply with the result.

Access and eligibility depend on local law and are available where local law permits. If a location rule affects your account, we may adjust access while keeping required privacy, security and transaction records.