Reference

Open tclottery legal terms for India

We keep this page focused on account terms, data use, access rules and contact paths for India.

India accessLocal lawAccount termsData use
tclottery Open tclottery legal terms for India
CONTACT PATHS

Switch to our legal contacts

If you need a legal answer, use the same account area you use for service messages.

Account message Send a written query from your account so we can link it to the…
Legal mail Use the email path for corrections, access requests or policy questions that need attachments…
Form request If you want a change to stored details, submit the form with the exact…
DATA AND RECORDS

Browse data use and retention

We handle this policy area with a narrow scope: only the data needed for account access, transaction checks, support handling and legal duties stays in active use.

Account records

We keep account details, transaction references and support records only for operating the service, handling disputes and meeting legal duties. We do not use them for unrelated work, and we limit access to staff who need the record.

Cookie controls

Cookies remember session state, language choice and whether you have already seen a notice. They help the page load with the same settings next time, and you can clear them in your browser if you want a fresh session.

Login checks

We protect login access with password checks, device checks and step-up verification when a change looks unusual. If you request a reset or a profile edit, we compare the request against the account record before we apply it.

Retention window

We retain records only as long as needed for support handling, dispute work, fraud checks and any legal duty that applies to the account. When a retention period ends, we remove or anonymise the data where the law allows.

Change requests

You can ask for correction, access or deletion of stored details through the account contact path or the legal mail route. Give the exact field, the reason and any proof we need so we can verify the request quickly.

Local access

Access and eligibility depend on local law and on where the service is available. If a rule in your area limits use, that rule applies for your account, and we will not extend access beyond what the law permits.

Open common legal questions here

These questions cover the parts people usually check before opening an account: access, record-keeping, cookies, correction requests and the contact path for legal concerns. We keep the answers direct so you can compare them with the page terms and decide what applies to you. If a rule changes, the page changes with it, and the version on screen is the one you should use for your account.

Access depends on local law and on whether the service is available where you are. If your region is restricted, we do not open or continue access there, and the local rule applies to your account.

We keep login history, account edits, payment references, support messages and consent choices for dispute handling, fraud checks and legal duties. We do not keep them longer than needed for those reasons and the retention rule that applies.

Send the exact field, the correct value and a short reason through the account contact path or the legal mail route. We check the request against the record we hold and apply the change where local law allows.

Cookies remember session state, language choice and whether you have already seen a notice. They help the page load in the same format next time, and you can clear them in your browser if you want to reset the session.

Use the account message path for everyday questions, and use the legal mail or form request when you need a written record, a policy correction or a request tied to your stored data.

When we change a term, we update the page and keep the date visible so you can compare the new text with the earlier version. If you keep using the account, the updated text applies to you.

Yes. You can ask for the categories we store, why each category is used and how long each one is kept. We respond through the same contact path once we verify the request.