Reference

Privacy Policy for your baji888 account

Blackjack, Zeus vs Hades, Football Strike, Spribe Aviator, Bingo and Fishing War sit behind one account, and this Privacy Policy explains what data we collect before you open…

UPI data carePaytm privacy checksPhonePe wallet contextCookie choices
baji888 Privacy Policy for your baji888 account
CONTACT PATHS

Three paths for privacy requests

Privacy requests work faster when you contact us from the same account you are asking about. Use the in-account chat for login or cookie questions, email for formal access or deletion requests, and the wallet query path for UPI, Paytm, PhonePe or Google Pay records. We may ask for identity checks before changing data, because the Privacy Policy requires us to protect your account from unauthorised changes.

Team online

Account privacy inbox

Send access, correction or deletion requests from your registered email address. Include your account name, the data you want checked, and whether the request relates to login records, profile details or cookie settings.

Wallet data queries

For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction date and masked reference only. We check the payment record without asking for your full banking credentials.

Correction request

If your name, mobile number or email address is wrong, ask us to correct it through the account area. We may request proof before changing details tied to withdrawals or security checks.

ACCOUNT CONTROLS

Six controls behind your account data

Our privacy work is built into account creation, login checks, wallet records and cookie tools.

Data collection

We collect profile, contact, device, login, wallet and session data that relates to your account. The Privacy Policy explains why each group is used and how it supports verification, security and support work.

Cookie controls

Cookies help remember your session, language choice and basic site settings. You can adjust browser cookie settings, though blocking required cookies may affect login, wallet checks or account protection tools.

Account security

We use login records, device checks and verification steps to reduce unauthorised access. If a privacy request could expose account data, we confirm identity before sharing, correcting or deleting records.

Retention rules

We keep account and wallet records only for purposes stated in this Privacy Policy, including legal duties, dispute handling and security checks. When the purpose ends, we delete or anonymise data where practical.

Partner sharing

Payment processors, hosting partners and customer care tools may receive limited data needed for their role. We do not permit partners to use your personal data for unrelated purposes.

Change requests

You can ask us to access, correct or delete eligible data. We explain the outcome, any legal reason for keeping a record, and the next contact path if you disagree.

Privacy Policy questions before you join

These answers focus on the Privacy Policy for your baji888 account, including personal data, cookies, wallet references, access requests and local-law limits. They are written for India access and use the same plain approach we apply in account support. If your case involves a live wallet record or identity change, contact us from your registered account so we can verify the request safely.

It covers account profile details, contact data, login records, device signals, cookie data, wallet references and support messages. It also explains how we use those records for verification, security, payments and privacy requests.

We use payment references to match deposits, withdrawals and wallet queries to your account. We do not ask for full banking passwords, and privacy requests about payments should include only masked references.

Yes. Contact us from your registered account and state which detail needs correction. We may ask for proof before changing identity, mobile, email or wallet-linked data, because incorrect changes can affect account security.

You can request deletion of eligible data. Some records may need to be kept for legal duties, payment disputes, fraud checks or account security; we will explain any reason that applies to your request.

Cookies support login sessions, language settings, security checks and basic site measurement. You can change browser settings, but blocking required cookies may prevent the account area or wallet checks from working correctly.

Only team members who need the request for identity checks, support action or legal handling should access it. We limit internal access by role and keep a record of the response we provide.

Yes. Access and eligibility depend on local law and are available where local law permits. That legal position may affect what data we collect, how long we keep it and how requests are handled.