Reference

Open baji365 with clear privacy terms

This Privacy Policy explains how baji365 handles your account details, device signals, wallet records and support messages while you use the lobby.

Account dataCookie choicesUPI recordsSupport requests
baji365 Open baji365 with clear privacy terms
CONTACT PATHS

Check privacy support channels

Privacy questions should reach the right team, not a general inbox with no context. Use the account help area, email channel or live chat and include the mobile number or email linked to your account. We may ask for a short verification step before discussing records, because privacy support must confirm that the request comes from you.

Team online

Account help desk

Open the help area after login and choose the privacy topic. This path links your request to your account record, so our team can check cookies, wallet references or profile data without asking you to repeat details.

Email privacy request

Send a clear request from the email address on your account. Include what you want checked, changed or removed, and avoid sending card images or unrelated documents unless our privacy team asks for them.

Live chat verification

Use chat when you need quick direction on where a privacy request should go. The agent can explain the next step, but account-level data changes may still require email confirmation for your protection.

DATA CARE

Browse our privacy handling practices

Your Privacy Policy should be clear enough to act on. We explain what we collect, why we collect it, how long we keep it and who can access it inside our operation.

Account data

We use your profile details to create and maintain your account, confirm access, send account messages and connect wallet activity to the correct person. We do not ask for extra identity data unless a check needs it.

Cookie choices

Cookies help keep you logged in, remember language and device settings, and measure whether pages load correctly. You can manage browser cookies, though some account functions may not work properly if essential cookies are blocked.

Wallet records

UPI, Paytm, PhonePe and Google Pay references are stored so we can match deposits, verify withdrawals and trace payment queries. We keep transaction records separate from game preference data wherever the system allows.

Security checks

Login attempts, device changes and unusual wallet activity may be checked to protect your account. If something looks inconsistent, we may pause a request while we confirm that the activity came from you.

Retention periods

We keep account and transaction records only for business, security and legal needs. When data is no longer required, we delete it, anonymise it or keep it in restricted archives with limited internal access.

Change requests

You can ask us to correct profile details, check stored data or remove records where the law allows. Some wallet and security records may need to stay for audit, dispute or legal reasons.

See common Privacy Policy questions

These answers explain how the Privacy Policy works in everyday account use. They focus on data rights, account access, cookies, wallet records and contact routes. If your question involves your own account, contact us from the registered email or logged-in help area so we can verify the request.

We collect account details, contact data, login records, device signals, cookie choices, support messages and wallet references. We use these records to operate your account, protect access, process payment checks and answer privacy requests.

Payment references help us match deposits, verify withdrawals and investigate wallet queries. They also help prevent account misuse. We keep these records for operational and legal reasons, then restrict, delete or anonymise them when no longer needed.

Yes. Contact us from your registered email or logged-in help area and state what needs correction. We may verify your identity before making changes, especially where the change affects wallet access or withdrawal checks.

You can request deletion where the law allows. Some records may need to remain for payment disputes, account security, fraud checks or legal duties. We will explain what can be removed and what must stay.

Cookies remember your session, language choices and basic device settings. You can control cookies in your browser, but blocking essential cookies may stop login, wallet pages or account tools from working as intended.

Only teams that need the message to handle your request can access it. Privacy, wallet and account security teams may see different parts of a case, depending on what you asked us to check.

Yes. Access and eligibility depend on local law and are available where local law permits. If a location check is required, we use it to decide whether account access can continue under applicable rules.