Reference

Legal terms for your account

This page sets out the legal terms that shape how you open an account, what we collect, and how we handle requests.

India lawUPIPaytmPhonePe
betscratch Legal terms for your account
REQUEST CHANNELS

Where to send legal requests

If you need a legal correction, a copy of the current terms, or a question about access, use the contact route that matches your account. Tell us what happened, the date, and the record you want us to check so we can route it fast. We may ask you to confirm your identity before we change anything, because legal requests can affect account history, payment records, and support logs.

Team online

Registered email

Send your request from the email tied to your account, and include the exact point you want us to address. That helps us verify the sender before we touch records or reply with a status.

Account form

Use the form in your account area if you want a written trail. Add your account name, the page you are asking about, and any deadline so we can route it to the right team.

Written notice

For formal notices, use the postal contact shown in the footer. Include your identity details, the legal issue, and the record reference so we can match the notice to the right file.

DATA AND ACCESS

How we keep records safe

We keep this policy area practical. Only the data needed to run an account, settle requests, and meet legal duties is retained, and we separate that from cookie data used for session…

Data use

We keep account data for identity checks, request handling, and legal duties tied to the account. If you ask for a change, we work from the exact record set linked to your registered details.

Cookies

Cookies help remember your session, language, and whether you already accepted the current legal page. You can clear them in your browser, but some pages may then ask you to repeat the same step.

Security checks

Before we change sensitive records, we may ask for a one-time code, login history, or matching account details. That extra step helps stop someone else from altering your file on a shared device.

Retention

We keep some records longer when law, tax checks, disputes, or fraud control require it. Once that purpose ends, we reduce the record set or remove it where our process allows.

Request changes

If a detail is wrong, tell us exactly which field needs correction and send supporting proof. Clear requests help us update the right record without affecting payment history or contract logs.

Contact trail

We log the time, channel, and outcome of each legal request so you can ask for a status update later. That trail also helps us track whether a reply was sent within our stated process.

Common questions on legal terms

These questions focus on your rights, access, and the records we keep. If your situation is tied to local law, the answer may vary by state or region, and we will point you to the right contact route. When you are unsure what applies, send the request from your registered account details so we can check the record without delay.

Yes. Ask from your registered email or in-account form, and we will confirm the categories of data tied to your account, subject to legal duties that may require us to keep some records longer.

Tell us the field, the correct value, and a matching proof document. We check the request against the account record before changing anything, so unrelated payment or contract history stays intact.

Local law comes first. If a rule in your state or region conflicts with this page, we follow the local rule and apply the version of the process that fits the legal requirement.

You can ask, and we will check whether any part of the record must stay for tax, dispute, fraud, or other legal duties. If removal is allowed, we process it through the right account channel.

Cookies remember session state, language, and page confirmations. If you clear them, you may need to confirm your details again, but that does not change the legal terms tied to your account.

Use the support path in your account area or the postal contact shown in the footer, and include your identity details plus the request reference so we can route it correctly.