Reference

Privacy Policy for India accounts

Our Privacy Policy gives you a clear account-data view before you open an account: sign-up details, device checks, cookies, game activity such as Roulette or Spribe Aviator, and…

Account data useCookie choicesUPI privacy contextIndia access terms
k094 Privacy Policy for India accounts
CONTACT ROUTES

Privacy help for your k094 account

Privacy requests should reach the team that can match your message with your account safely.

Email privacy desk Send privacy requests through the contact address shown inside your account area. Include your registered email, the request type and any UPI, Paytm or PhonePe reference only if it helps us locate the record.
Account chat route Use live chat when you need to ask how a privacy request will be handled. Our team can explain identity checks, expected response steps and what data should not be shared in chat.
Security report path If you think your account data, device login or payment reference has been exposed, contact us from the account area quickly. We can freeze changes while we verify access and check recent activity.
ACCOUNT CARE

How we protect Bingo account data

Our privacy work covers the full account path, from sign-up checks to cookies, wallet records, game logs and support messages.

Collection scope

We ask for account details, contact data, device signals and transaction references needed to operate your account. We avoid asking for unrelated documents unless a verification or security step requires them.

Cookie choices

Cookies help keep sessions active, remember preferences and detect risky logins. You can manage browser settings, though some account functions may not work if essential session cookies are blocked.

Account security

Login records, IP ranges and device changes help us detect access that does not match your normal pattern. When risk appears, we may require extra checks before data changes proceed.

Payment records

UPI, Paytm, PhonePe and Google Pay references are used to match wallet activity and handle account queries. We do not need your full banking password or payment app PIN.

Retention rules

Some records must be kept for dispute handling, security, audit or legal reasons. When those reasons end, we delete, anonymise or reduce stored data according to our internal retention schedule.

Change requests

You can ask us to correct account details, provide a copy of certain records or consider deletion. We first verify identity, then explain what can be changed and what must be retained.

Privacy questions for Indian account access

These questions focus only on how this Privacy Policy works for your account data, payment references, cookies and support requests. They also explain how we handle access requests, corrections and deletion where local law permits. If your question involves a specific UPI, Paytm, PhonePe or Google Pay record, contact us from the account area so we can verify ownership first.

We collect account details, contact data, device signals, login records, game activity and payment references needed to operate your account. We may also keep support messages connected with privacy, security or transaction queries.

Payment references help us match wallet activity with UPI, Paytm, PhonePe or Google Pay transactions. We use them for reconciliation, dispute handling, fraud checks and account support, not for selling your personal data.

Cookies keep your session active, remember account preferences and help detect risky login behaviour. You can adjust browser settings, but blocking essential cookies may affect sign-in, wallet checks or account security features.

Yes. Send a correction request from the account area or privacy contact path. We verify identity first, then update eligible details or explain why a record must stay unchanged for security or legal reasons.

You can ask us to delete eligible data. Some records may need to remain for transaction disputes, security checks, audit duties or legal requirements, and we will explain what can be removed.

Access is limited to trained team members or service partners who need the data for account operation, payment handling, security checks or support. Each access level is tied to a defined work need.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests are still handled through verification steps so your account records are not changed by anyone else.