Reference

Open with clear legal terms

Account terms, privacy rights, cookie choices and India contact routes sit here in one place so you can check the rules before you open an account.

India legal accessPrivacy rightsCookie choicesAccount security

Explore lobby Read FAQ

Explore India access rules

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

This legal page explains how ultrabet applies account terms, privacy duties, cookie consent and dispute handling for India. We ask you to give accurate account details, keep your sign-in credentials private, and use only payment names that match your account record. Access may vary by state

1
or union territory, and eligibility depends on local law and is available where local law permits. UPI, Paytm and PhonePe records may be used to confirm transaction ownership, resolve wallet questions and support legal requests. We may pause account activity while identity, location, fraud-risk or document
2
checks are being assessed. If any term changes, we place the current wording on this page and apply it from the date shown in your account area or policy banner.

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

CONTACT ROUTES

Check legal contact routes

Legal questions need a clear path, not a generic inbox. Use the contact route that matches your request so we can verify your account, read the relevant record and reply with the…

Account terms help Write to support with your registered email, account ID and the clause you want to discuss. We check the current terms, your account record and any policy banner shown before giving a written reply.

Privacy request desk For access, correction or deletion requests, send the same name used on your account and a contact number. We verify ownership first, then explain what data can be changed, retained or removed under law.

Payment record query If a UPI, Paytm or PhonePe record is part of a legal question, share the transaction reference only through support. We compare it with wallet logs and never ask for your PIN or full banking password.

DATA CONTROLS

Browse privacy and security controls

Our legal process covers what we collect, why we keep it and how you can ask for changes.

Data we collect

We collect account details, login events, device data, cookie choices, wallet references and support messages. These records help us run identity checks, protect accounts, answer legal requests and confirm transaction ownership.

Cookie choices

Cookies help keep sessions active, remember consent choices and detect unusual access patterns. You can adjust browser settings, though some account security checks may need essential cookies to keep your session valid.

Account security

We use password protection, session checks and device review when account activity looks unusual. If you report access you did not authorise, we may pause sensitive actions while we confirm ownership.

Record retention

Some records are kept while your account is active, while transaction and dispute records may stay longer where law requires. When retention is no longer needed, we delete or anonymise the record.

Correction requests

If your name, phone number or email is wrong, contact support from the registered channel. We may request proof before changing details because payment records and legal notices depend on accurate identity data.

Dispute handling

For a legal dispute, share dates, account ID, transaction references and any support ticket number. We review wallet logs, consent records and account actions before sending a written response through the verified channel.

Discover answers on legal rights

These answers explain the legal controls you can use when you hold an account with us. They cover eligibility, privacy rights, cookie choices, account access, payment records and dispute contact steps for India. If your question involves local law, we will apply the rule that access depends on local law and is available where local law permits.

You may open an account only where local law permits access and where you can provide accurate personal details. We may verify identity, location and payment ownership before allowing full account use.

Send a request from your registered email with your account ID and the data range you want. We verify ownership before sharing records, because account data may include wallet references and support history.

Yes, you can request correction of details such as name, email or phone number. We may ask for proof where the change affects identity checks, payment matching or legal communication records.

We keep payment references to confirm transaction ownership, investigate wallet disputes and meet legal record duties. We do not need your PIN, full banking password or private app credentials for these checks.

Cookies support login sessions, consent records and security checks. You can manage them in your browser, but essential cookies may still be needed for account access and fraud-risk checks.

Contact support with your account ID, dates, device details and any ticket number. We may pause sensitive actions, verify ownership and check login records before replying through your verified contact route.

Use the legal contact route in support and include the clause, date, account ID and related transaction references. We review the account record and respond in writing after identity verification.

Open with clear legal terms

Check legal contact routes

Browse privacy and security controls

Data we collect

Cookie choices

Account security

Record retention

Correction requests

Dispute handling

Discover answers on legal rights

01 Who can open an account under these terms?

02 How do I ask for my account data?

03 Can I correct personal details on my account?

04 Why are UPI, Paytm or PhonePe records kept?

05 How are cookies handled under this policy?

06 What happens during an account access dispute?

07 How do I raise a legal complaint?

Related Pages