Reference

Privacy Policy for your b38m account

Speed Baccarat, Rooster Rumble, Football Strike, Crash X, Bingo and Fishing War create account activity, wallet records and device signals; this Privacy Policy explains how we handle that…

India privacy termsUPI data contextCookie choicesAccount security

Browse lobby Read FAQ

What this policy covers in India

b38m Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy sets out how we collect, use, store and share personal data when you create an account, enter the lobby, use support, or make wallet transactions. We process details such as your name, mobile number, email address, device data, login history, game activity and

1
payment references from UPI, Paytm, PhonePe or Google Pay. Where we mention access, account eligibility or service availability, it depends on local law and is available where local law permits. We may ask for identity checks before withdrawals, data changes or account recovery, because privacy requests
2
must be tied to the correct account. We also explain cookie use, retention periods and contact paths so you can act on your rights without guessing which team handles your request.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

PRIVACY CONTACTS

Reach us about privacy requests

Privacy questions need a clear route, not a long chase through the lobby. Use the contact path that matches your request, and we will ask for account checks before changing, sharing or…

Email privacy desk Write to our privacy mailbox from the email on your account. Include your account ID, the request type and any payment reference, but do not send full card or bank images unless we ask.

Live chat handoff If you start in chat, our team can pass your privacy request to the account team after basic checks. We keep the thread linked to your account so you do not repeat the same facts.

Wallet data queries For UPI, Paytm, PhonePe or Google Pay records, share the transaction ID and date range. We use that to match wallet entries before answering correction, access or deletion requests.

ACCOUNT CONTROLS

Your data controls inside b38m

Your privacy controls work across account setup, login checks, cookies, wallet activity and support history.

Data we collect

For account setup, we collect contact details, login credentials, device signals and account preferences. During play, we record game sessions, balance movements and support contact so the account history remains traceable.

Cookie choices

Cookies help us keep you signed in, protect sessions and remember display settings. You can clear cookies in your browser, but some account checks may repeat when the device looks new.

Security checks

We watch for unusual login patterns, repeated failed passwords and mismatched device signals. These checks help protect your account record before we allow withdrawals, data changes or recovery steps.

Retention periods

Account, wallet and support records are kept only as long as needed for service, dispute handling, security checks and legal duties. When storage is no longer needed, we delete or anonymise the data.

Payment privacy

UPI, Paytm, PhonePe and Google Pay references are used to match deposits, withdrawals and refund checks. We store only what we need to confirm the transaction and protect the account.

Change requests

You can ask us to correct account details, update contact data or explain stored records. We may request proof of control over the account before making any privacy-related change.

Privacy answers before you join

These answers focus only on how the Privacy Policy works for your account, wallet records, cookies and contact requests. They do not replace legal advice, and they do not change any local rule that applies to you. If a question affects account access or eligibility, availability depends on local law and applies only where local law permits.

We collect data needed to create and protect your account, such as name, mobile number, email, login history, device signals, game activity and wallet references. We do not ask for more than needed for the account purpose.

Payment references help us match deposits, withdrawals, refunds and support requests to the correct account. We use transaction IDs, time stamps and status data for wallet checks, dispute handling and security monitoring.

Yes. Send a request from your registered email or through verified support. We may ask for account checks first, then share the relevant record in a practical format where local law allows.

Contact support with the exact field that needs correction, such as mobile number or email. For sensitive changes, we verify account control before updating the record so your privacy is not put at risk.

Yes. Cookies are used for login sessions, security checks, language settings and device recognition. If you clear them, you may need to sign in again or complete extra checks on that device.

We share data only when needed for payment processing, account security, support handling, legal duties or service providers who help run the account system. We do not sell your personal data.

You can ask us to delete data linked to your account. Some records may be kept for security, dispute, wallet or legal reasons, and we will explain what can be removed or anonymised.

Privacy Policy for your b38m account

Reach us about privacy requests

Your data controls inside b38m

Data we collect

Cookie choices

Security checks

Retention periods

Payment privacy

Change requests

Privacy answers before you join

01 What personal data does b38m collect?

02 How are UPI, Paytm and PhonePe records used?

03 Can I ask for my account data?

04 How do I correct wrong account details?

05 Does the policy cover cookies?

06 When can my data be shared?

07 Can I request deletion of my data?

Related Pages