Reference

bookmakers legal terms for your account

Open your account and you can read the legal terms alongside the India-facing wallet flow, including UPI, Paytm and PhonePe where local law permits.

IndiaUPIPaytmPhonePeGoogle Pay

explore the lobby Read FAQ

How these terms apply in India

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

These terms apply to your account, your use of the site, and any request tied to payments or records. Access depends on local law and is available only where local law permits. If your location, state rule, or a court order limits use, that limit controls

1
even when the page is reachable. We may ask for identity checks, payment verification, or a written confirmation before we process a correction, withdrawal record, or dispute. UPI, Paytm, PhonePe and Google Pay are shown here as India context chips, not as a promise of access
2
everywhere. We keep transaction logs, login history, and support threads for the period needed to run the account, settle queries, and meet legal or tax duties. If a term conflicts with local law, the law applies first and the affected part is read in that way.

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

CONTACT ROUTES

Contact paths for legal matters

If you need a copy of the terms that apply to your account, or you want a correction, deletion request, or data question, use the contact route listed here.

Email Send written requests here when you need access to stored data, a correction, or a legal query. Include your account detail and the exact change you want so we can match the record and reply with the right form.

Secure message Use the in-account message box for requests that need a secure trail, such as a copy of stored details or a dispute about a record. The thread stays linked to your account and to the request date.

Postal notice For formal notices, send a signed letter to the address we provide in your account area. This path is useful when a request needs a physical record, a dated signature, or a file copy for later checking.

DATA AND ACCESS

How we keep records and access

This policy area is handled through a small set of controls: data minimisation, session cookies, account lock steps, retention windows, and account-matched request channels.

Data handling

We store the details needed to run your account, confirm access, process records, and answer disputes. Collection stays limited to what the terms call for, and we avoid using it for unrelated purposes.

Cookies

Cookies keep sessions active, remember language choices, and help us spot repeated login errors or unusual traffic. Essential cookies support account functions; others are used only within the limits stated in the terms.

Account security

Keep your login details private and tell us quickly if a device, password, or contact detail changes. We may pause access until a verification step is complete when a sign-in looks unusual.

Retention

We retain account and transaction records only as long as needed for administration, legal duties, audit checks, or dispute handling. After that, we delete or anonymise the data in line with policy.

Change requests

If your stored name, contact detail, or record is wrong, send a correction request with the exact field and the requested edit. We will update it where the law and the audit trail allow.

Contact trail

Use the same channel that is linked to your account when you ask for access, correction, or deletion. That helps us confirm the request quickly and keep a clean record of what changed.

Common questions about legal terms

These questions cover access, data use, cookies, corrections, and record retention. If your request depends on local law, we handle it only where the law permits. Use the contact route that matches your account so we can confirm the request and reply with the next step. We keep the language plain so you can see what we store, why we store it, and how you can ask for a change without hunting through long clauses.

It sets the terms for account use, data handling, cookies, access checks, record retention, and the paths you can use to contact us. Where local law says otherwise, we follow the law first.

Access depends on local law and is available only where local law permits. If a state rule or another limit applies to your location, that limit controls how the account can be used.

We keep the details needed to run the account, verify access, process records, support disputes, and meet legal duties. We do not collect extra data for reasons outside those stated in the terms.

Cookies keep the session active, remember language and login state, and help us spot errors or unusual use. Essential cookies support core account functions, while optional ones are used only within the policy limits.

Send the exact correction from a channel linked to your account, and include both the current detail and the replacement detail. We update the record when the law and the audit trail allow.

Use the contact route shown here and say whether you need access, correction, deletion, or a copy of stored data. We may need to verify the request before we act on it.

We keep records only for the periods needed for account administration, disputes, security checks, and legal or tax duties. After that, we remove or anonymise them under the policy and local law.

bookmakers legal terms for your account

Contact paths for legal matters

How we keep records and access

Data handling

Cookies

Account security

Retention

Change requests

Contact trail

Common questions about legal terms

01 What does this page cover?

02 Can I access the service from India?

03 What data do you keep about me?

04 How do cookies affect my session?

05 How do I ask for a correction?

06 Who can I contact about a legal matter?

07 How long do you keep records?

Related Pages