Reference

Legal terms for durabet account access

Account terms, privacy choices, cookie settings and India access rules are set out here before you open your durabet account.

India access depends on local lawUPI context includedPrivacy and cookies coveredAccount terms in plain English

Explore the Lobby Read FAQ

India policy posture and payment context

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

These terms set the legal frame for your account, wallet records, identity checks, content use and service access. We write them for India in clear English, but access remains jurisdiction-dependent and is available where local law permits. When a wallet action uses UPI, Paytm, PhonePe or

1
Google Pay, the same account terms still govern the account record, payment reference, verification step and any later query. We may ask for documents when the law, a payment partner or account security process requires it. We keep legal records only for defined operational, regulatory and
2
dispute-handling reasons, then remove or anonymise them when retention is no longer required. If any clause changes, we present the updated wording through this page or account notices before it applies.

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

CONTACT ROUTES

Three routes for legal help

If a legal concern affects your account, start with the channel that matches the issue.

ACCOUNT CARE

Six ways we protect legal rights

Legal work is not only a page we publish. It affects how we collect account details, verify access, handle cookies, respond to rights requests and retain records.

Data collected

We collect account identifiers, contact details, device signals, payment references and verification records needed to run the account and meet legal duties. We avoid asking for extra files unless a specific check requires them.

Cookie choices

Cookies help us keep sessions active, remember language choice and detect risky access patterns. Where a cookie is not needed for core account safety, we explain its purpose before you continue using it.

Security checks

Login alerts, device matching and one-time verification codes are used to reduce unauthorised access. If we see a mismatch, we may pause sensitive actions until you confirm the account belongs to you.

Record retention

Wallet entries, support messages and verification logs are kept for set legal, tax, operational or dispute-handling periods. After that, we delete, anonymise or restrict the record depending on the duty that applies.

Change requests

You can ask us to correct contact details, update identity records or remove data that no longer needs to be kept. We may retain limited proof of the request for audit reasons.

Team access

Only trained staff can view legal or verification cases, and access is granted by role. Support can see case status, while sensitive documents are limited to teams handling compliance or legal review.

Your legal questions answered here

The questions below focus on account terms, privacy rights, cookie use, payment records and India access rules. They are written to help you decide what to do next before opening an account or contacting us. For a case involving your own record, send the account email or mobile number so we can verify you.

Your account is governed by our terms, privacy statement, cookie statement and any market-specific rules shown during account opening. Access depends on local law and is available where local law permits.

Availability may differ by state, location, device setting or legal requirement. If our checks show that access is not permitted for your location, we may restrict account opening or certain account actions.

We may collect your name, contact details, device data, location signals, payment references and verification files. The exact request depends on account activity, wallet action, security need or a lawful request.

Send a correction request through the privacy route with your registered email or mobile number and the detail that needs changing. We verify the account first, then update or explain any lawful reason for keeping the existing record.

Payment references are linked to your wallet record so we can trace a transaction, answer disputes and meet record-keeping duties. We do not ask for unrelated banking files when a reference number is enough.

Cookies can support session security, language choice, consent records and fraud checks. We describe their purpose so you understand which cookies are needed for account safety and which relate to preference handling.

Use the legal mailbox for formal correspondence, the privacy route for data rights and account support for terms or eligibility questions. Include dates and references so we can match your request correctly.

Legal terms for durabet account access

Three routes for legal help

Six ways we protect legal rights

Data collected

Cookie choices

Security checks

Record retention

Change requests

Team access

Your legal questions answered here

01 What legal terms apply when I open an account?

02 How does local law affect account access in India?

03 What personal details do we collect for legal checks?

04 How can I ask for a correction?

05 How are UPI, Paytm and PhonePe records handled?

06 Why do cookies appear on a legal page?

07 Who do I contact about a legal concern?

Related Pages