Reference

Open the defabet Privacy Policy

Live Blackjack, Lucky Lightning and UPI payments create account records, and this Privacy Policy explains how we collect, use, store and protect those records on defabet.

Account data useCookie choicesUPI privacy contextData request paths
defabet Open the defabet Privacy Policy
HELP CHANNELS

Check Privacy Help Before Account Use

Privacy questions should reach the team that can actually act on them. Use the email path for data access, correction or removal requests, and use live chat when you need help finding…

Privacy email Write to [email protected] from the email linked to your account. Include your account name, the request type and any payment reference only if it helps us find the record safely.
Live chat handoff Chat support can point you to the privacy team and confirm which details are needed. For data copies or removal requests, the final response will come through the dedicated email route.
Account verification Before we change contact data, release a data copy or close records where allowed, we check ownership through account signals. This protects your wallet history, login trail and support conversations.
DATA CARE

Browse How We Handle Your Data

Our privacy work is practical: collect only what is needed for account access, wallet operation, fraud checks, customer help and legal duties.

Account data

Your name, contact details, login records and account preferences help us maintain access and respond when you contact support. We use these records only for account operation, safety checks and service messages.

Payment records

UPI, Paytm, PhonePe and Google Pay entries may create transaction IDs, timestamps and status markers. We store those references to match wallet activity, answer disputes and meet applicable record duties.

Cookie controls

Cookies and similar tools help keep your session active, remember device choices and detect unusual access. You can adjust browser settings, though some account pages may need cookies to function.

Security checks

We monitor login patterns, device signals and failed access attempts to reduce account misuse. If a risk appears, we may pause sensitive changes until you confirm that the request is yours.

Retention periods

Some records are kept while your account is active and for a lawful period after closure. When retention is no longer needed, we delete, aggregate or anonymise data in line with our process.

Change requests

You can ask us to correct contact details, send a copy of account data or remove records where law allows. We reply with the outcome and any reason a record must stay.

Explore Privacy Questions Before You Join

These answers explain the privacy choices you have before and after account opening. They cover account data, payment references, cookies, access requests, correction requests and retention. If your question involves a specific transaction or login event, contact us from the email linked to your account so we can match your request safely.

We collect account contact details, login records, device signals and payment references needed to run your wallet and support your account. Extra checks may apply when local law or payment partners require verification.

Yes. The policy covers transaction references, timestamps, status markers and support records linked to UPI, Paytm, PhonePe and Google Pay. We do not ask for wallet passwords or your UPI PIN.

Cookies help maintain your session, remember device choices and detect unusual access patterns. You can adjust browser settings, but certain account pages may not work correctly if essential cookies are blocked.

Yes, you can email [email protected] from your account email and ask for a data copy. We will verify ownership first, then explain what can be shared and the expected response path.

Send the correction request from your linked email and state which detail needs changing. We may ask for account checks before updating contact data, payment labels or identity records where required.

You can request deletion where law allows. Some records, such as payment references, dispute history or security logs, may need to stay for a lawful retention period before removal or anonymisation.

Only the teams needed to process your request should access it, such as privacy, support or security staff. Internal access is controlled, and sensitive changes are checked before any action is taken.