Reference

Privacy Policy for your 3fun account

Roulette, Number Blast, Crash X and UPI wallet checks create account data, and this Privacy Policy explains how we collect, use, store and share that data when you…

UPI data contextPaytm privacy pathPhonePe record careCookie choices
3fun Privacy Policy for your 3fun account
PRIVACY CONTACT

Three ways to ask about privacy

Privacy questions should reach the right team without making you repeat account details in open chat.

Email privacy desk Send privacy requests from the email linked to your account. Include your 3fun ID, the change you want and any UPI, Paytm or PhonePe reference only if it helps us locate the record.
Account chat handoff Start in account chat when you are logged in, then ask for privacy help. The chat team can pass your case to the data team without asking you to post full payment details.
Security review path Use the security route if you think someone accessed your account or changed personal data. We check recent logins, device signals and wallet activity before we explain what happened and what can change.
DATA HANDLING

Six controls behind our data handling

This Privacy Policy is backed by practical controls, not vague promises. We separate payment references from general support messages, reduce access to account records, and log changes made by internal teams.

Data we collect

We collect account identifiers, contact details, login records, device signals, cookie choices and payment references tied to UPI, Paytm, PhonePe or Google Pay. Game activity such as Roulette or Bingo is used for account records and disputes.

Why data is used

Your data helps us keep the account working, match payments, confirm withdrawals, prevent misuse, answer support requests and meet legal duties. We do not use payment handles for unrelated messages or sell account profiles.

Cookie choices

Cookies keep you logged in, remember basic preferences and help us detect risky access patterns. You can adjust browser settings, though some account checks may not work correctly if essential cookies are blocked.

Account security

We use login checks, device records and internal access controls to reduce unauthorised use of account data. If a privacy request involves security, we may verify identity before sharing or changing records.

Retention period

We keep records for as long as needed for account operation, payment matching, dispute handling, fraud checks and legal duties. When those reasons no longer apply, data is deleted, anonymised or reduced.

Request handling

You can ask for access, correction or removal through the privacy contact paths. We review the request, verify authority, check legal duties and reply with the action taken or the reason we cannot act.

Privacy questions before you open account

These answers explain common Privacy Policy points before you share data with us. They focus on account records, cookies, payment references, access rights and contact routes. If your question involves a specific transaction or login, include only the minimum details needed to identify it. Eligibility and access still depend on local law and are available where local law permits.

It covers account identifiers, contact details, login records, device signals, cookie choices, payment references and activity linked to your account. It also covers privacy requests you send to support or the data team.

We use payment references to match transfers to your account, confirm withdrawal requests, check disputes and meet legal duties. We ask for only the details needed to locate the relevant record.

Cookies help keep sessions active, remember preferences and support security checks. You can manage them in your browser, but blocking essential cookies may affect login, account verification or payment matching.

Yes. Send a request through the privacy contact paths and tell us what you want changed or removed. We verify the request, check legal duties, then reply with the outcome.

Access is limited to teams that need data for account support, payments, security, compliance with law or technical maintenance. Internal access is logged where needed and full payment details are not used in open chat.

We keep records while they are needed for account operation, payment matching, dispute checks, security reviews and legal duties. After that, we delete, anonymise or reduce the data where we can.

Some access, eligibility and data duties can depend on local law. Where local law permits access, this Privacy Policy explains the account data we handle and how you can contact us.