Reference

Legal terms at a glance

This page sets out how legal terms work on betloto: account use, privacy, cookies, record keeping and contact routes.

TermsPrivacyCookiesRecords

How these terms apply in India

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

These terms apply to India-facing accounts and sit beside our privacy notice and cookie settings. If a clause needs a different treatment under local law, the local rule takes priority in the place where service is permitted. We may ask for identity checks before sensitive changes,

1
including name edits, account closure, access requests or withdrawal-related verification. Records linked to UPI, Paytm, PhonePe and Google Pay can be kept for audit, dispute handling and tax or compliance duties, then removed when the retention period ends. We also log browser, device and session data
2
needed to run the account and reduce unauthorised access. Any request that changes account status should come from the registered contact, and we may hold the change until the request matches our records. If you send a question about a transaction, include date, amount and the
3
last four digits of the payment reference so we can find it faster.

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

REQUEST ROUTES

Where legal requests reach us

For legal requests, use the registered email, the in-account form or the help channel tied to your wallet.

Email request Write from the email linked to your account, mention the page or rule you are asking about, and include any supporting record. We use that thread to verify the request and keep a dated reply for your file.

In-account form Use the contact form inside your account when you need a correction, a copy of records or a closure request. It helps us match the message to your profile before we make any change.

Wallet thread If the request concerns a deposit, withdrawal or transfer record, open the wallet thread so our team can see the linked transaction and respond with the next step without asking you to repeat details.

DATA HANDLING

How records and cookies stay handled

We keep your account file limited to what we need for sign-in, payments, support and legal duties. Cookies store language, session and device settings, while security checks help spot strange access.

Data use

We link your profile, device and transaction history so we can run the account, settle disputes and answer legal requests. The file stays limited to what is needed for those purposes, not for unrelated use.

Cookies

Cookies keep your session alive, remember language choice and reduce repeat logins. If you clear them, some saved settings disappear, but the legal text and contact routes remain available through the site.

Security

Sign-in checks, one-time codes and device alerts help us spot account changes we did not expect. If you notice something strange, tell us at once so we can freeze access and check the log trail.

Retention

We store records only for the period needed for account admin, dispute handling and any legal duty that applies. When that period ends, the relevant data is removed or anonymised under our internal process.

Changes

To change name, phone number or other sensitive fields, write from your registered contact and include proof where requested. We update only after verification, so the record stays tied to the right account.

Contact path

For access, correction or deletion requests, use the same support route listed on this page. We reply with the steps we need and keep a copy of the exchange so your request has a clear trail.

Common questions about legal terms

The questions below cover access, record requests, cookies, corrections and retention. If your situation is not covered here, send a message through the registered contact path so we can match the request to your account and reply in writing. Where local law changes the answer, the local rule applies only in places where service is permitted, and we will tell you what that means for your file.

If a clause conflicts with local law, the local rule applies in the place where service is permitted. We then follow the closest lawful process for your account and explain any limit that remains.

Yes. Send the request from your registered contact and tell us which records you want. We may ask for identity checks first, then we will share the file in the format we can support.

Cookies keep sign-in state, language choice and page settings in place while you move through the site. If you clear them, the stored settings reset, but you can set them again on the next visit.

Send the correction from the account contact we already have on file and include proof if we ask for it. We update only after verification so the record stays linked to the right person.

Retention depends on the record type and the reason for keeping it. We hold the file for account admin, dispute handling and legal duty, then remove or anonymise it once that purpose ends.

The request should come from the registered contact linked to the account. If that is not possible, tell us why and we will explain what proof we need before we move ahead.

Yes. Access depends on local law and is available where local law permits. If your region is not eligible, we will say so plainly and point you to the lawful position for that location.

Legal terms at a glance

Where legal requests reach us

How records and cookies stay handled

Data use

Cookies

Security

Retention

Changes

Contact path

Common questions about legal terms

01 Which rule applies if local law differs?

02 Can I ask for a copy of my records?

03 How do cookies affect my session?

04 What if my details need correction?

05 How long do you keep records?

06 Who should send a legal request?

07 Can access be limited in some places?

Related Pages