Reference

Legal Terms for India

Our legal pages explain how account use, data handling, cookies and record retention work at 365bet.

Local lawData useCookiesRecord keeping

When Access Depends on Local Law

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

These terms set the legal position for your account in India. Some actions depend on local law, the verification result on file, and the payment path tied to the account. Where local law permits access, we may ask for identity proof, device confirmation or wallet checks

1
before we accept a change. We keep records for fraud detection, dispute handling, audit trails and the legal duties that apply to us. Cookies help us remember login state, language and form entries, so you do not need to repeat the same steps each time you
2
return. If you use UPI, Paytm, PhonePe or Google Pay, the record we keep is limited to what we need for reconciliation, support and any later audit. Nothing here changes the rule that local law controls access in your state, and any request we receive is
3
handled against that rule first.

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

REQUEST CHANNELS

Where to Send Legal Requests

For legal requests, write from the email on the account and say exactly what you want changed.

Email us Use this for record corrections, access questions and account closure requests. Send the account email, a short reason and any document that supports the change so we can log it cleanly and keep the paper trail tidy.

In-account message This route keeps the conversation tied to the same profile, which helps when we need to compare your request with the account record, payment trail or recent login activity before we answer.

Support form The form is useful when you want a tracked reply without sending a long email. Add the subject, account email and the exact field or record you want us to look at.

DATA KEEPING

How We Handle Records Safely

We keep policy handling narrow and practical. Cookies store session state, language and page flow; they do not change your legal rights.

Data handling

We collect only the account, device and transaction records needed to run access checks, settle disputes and meet legal duties. Anything outside that purpose stays out of the file, and we do not broaden use without a reason tied to the account.

Cookies

Cookies help the site remember login state, language choice and form entries. They also support session checks, so you can move through the account area without repeating the same steps or losing a field you already filled in.

Account security

Use a strong password and keep your email access current. We may ask for a fresh verification step before changes to payment records, contact details or access settings go through, especially when the request comes from a new device.

Retention

Records stay only for the period needed for the account, the transaction and the legal reason tied to them. After that, we archive or remove them under our retention rules, using the shortest practical period that fits the purpose.

Correction requests

If you need a correction, send the exact field, the corrected value and any proof that supports it. We compare the request with the stored record before we update anything, so the change matches the account trail.

Contact and change requests

For deletion, access or complaint handling, use the support form or message route from your account. We will reply with the status, any missing item and the next step, so you know what the file needs.

Questions About Legal Access

These answers cover the parts of the legal page that matter before you open an account or send a request. If your situation depends on local law, the rule in your region decides the path we can take. We keep the language plain so you can see what we collect, how long we keep it and where to send a change request without digging through extra pages.

Yes. Access depends on local law and is available only where local law permits. If a rule blocks a feature in your state, we do not open that path for your account, even if the rest of the profile remains active.

We keep the minimum account, device and payment records needed for verification, fraud checks, dispute handling and statutory duties. Those records are used only for those purposes, and we avoid collecting anything that is not tied to the account flow.

Cookies help us keep you signed in, remember language and keep forms from clearing while you move between pages. They also help us spot unusual behaviour that may need a check, which protects the account from unauthorised access.

Send the request from your account email, name the field to change and attach any proof that supports it. We compare the request with our records and reply through the same channel after the change is checked.

Retention depends on the record type and the legal reason for keeping it. We hold account and transaction files only as long as needed for the purpose, then archive or remove them under our retention rules and audit needs.

Use email, the in-account message or the form in the support area. Choose one route and include your account email, so we can trace the request and answer with the right context without delay.

Yes. If local law changes, we adjust access and account handling to match the current rule. Where a feature is no longer permitted, we stop that path for the affected region and update the account terms we apply.

Legal Terms for India

Where to Send Legal Requests

How We Handle Records Safely

Data handling

Cookies

Account security

Retention

Correction requests

Contact and change requests

Questions About Legal Access

01 Does access depend on local law?

02 What records do you keep for an account?

03 Why do you use cookies?

04 How can I ask for a correction?

05 How long do you keep records?

06 Who can I contact about a legal request?

07 Can my access change if the law changes?

Related Pages