Reference

Your privacy with cricketbetting in India

cricketbetting keeps your account, wallet and lobby privacy choices in one readable policy, so you know what data we collect before you open an account.

India privacy scopeUPI data contextPaytm privacy contextPhonePe privacy context
cricketbetting Your privacy with cricketbetting in India
CONTACT ROUTES

Three privacy contact paths

Privacy requests need a clear route, especially when they involve account access, wallet records or device sessions.

Email privacy desk Send a privacy email when you want to ask for access, correction, deletion or…
In-account chat Use chat after login for quicker checks linked to cookies, device sessions or recent…
Security escalation Contact us promptly if you notice a login you do not recognise, a changed…
DATA PRACTICES

Six privacy controls we operate

Our privacy work covers the full account path, from the first form you submit to the records created by gameplay and wallet movement.

Account data purpose

We collect details such as your name, contact data and login records to create and maintain your account.

Cookie choices

Cookies help remember sessions, detect unusual access and measure page performance.

Wallet record care

UPI, Paytm, PhonePe and Google Pay references may be stored with transaction timing, status and verification results.

Game session privacy

If you open Teen Patti, Turbo Blackjack, Crash Game or Fishing War, session records may show game name, time, stake…

Access protection

We use login monitoring, password checks and limited internal permissions to reduce account misuse.

Retention review

Data is kept only for account operation, security, dispute handling or legal needs.

Privacy questions before you join

Before you open an account, you should understand how your personal data moves through the site. These answers explain what we collect, how wallet and cookie records are used, what rights you can request, and how we handle changes to this Privacy Policy. If your request involves access to real account records, we will ask for enough verification to protect your data.

We collect the details you provide, such as contact data, login credentials and account preferences. We may also collect device signals, IP address, cookie data and wallet references needed for access, security and account operation.

Wallet records can include transaction reference, timing, status and verification result. We use them to match deposits or withdrawals to your account, answer disputes, detect unusual activity and meet legal duties where they apply.

Yes, you can contact us and ask for a copy of data linked to your account. We may verify your identity first, then provide the data that can be shared under applicable law and security rules.

You can ask us to correct account data if it is outdated or inaccurate. Some changes may need verification, especially when they affect login access, payment records, withdrawal checks or contact details used for security.

Cookies support login sessions, device recognition, security checks and page performance. You can manage cookies in your browser, but turning off essential cookies may affect account access, wallet actions or privacy request verification.

Retention depends on the record type and the reason for keeping it. Account, wallet, security and dispute records may be kept while needed for service, legal, tax, audit or safety purposes, then deleted or restricted.

We may update this page when our data practices, support routes or legal duties change. The current version on this page applies to your account, and major privacy changes may be flagged within account messages.