Reference

Open the Legal Terms for India

91clube sets out clear access terms, data handling and request paths for India.

AccessDataCookiesSupport
91clube Open the Legal Terms for India
REQUEST PATHS

Explore Contact Paths for Legal Requests

If you need a legal correction, a data copy, or a question about how this page applies to your account, contact us through the routes below.

Email request Send the request from the email linked to your account and state whether you want access, correction, deletion or a status check. Include one clear subject line so we can route it without delay.
Account form Use the in-account form when you want the fastest matching against your record. Attach the date, the relevant UPI or Paytm reference if needed, and the exact change you want us to make.
Postal request If you prefer a written record, send a signed letter with your account name, current contact detail and the request type. We reply using the contact method you provide and keep the thread for audit.
DATA HANDLING

Switch Through Data, Cookies and Retention

We handle legal data with a narrow purpose: account access, security checks, request fulfilment and records required by law.

Data use

We collect only the details needed to open, secure and service your account, including login identifiers, device signals and request history. When a legal request arrives, we check the record before making any change.

Cookies

Session cookies help keep you signed in and let us detect repeated failed logins or unexpected device changes. You can clear them in your browser, but some legal pages may ask you to sign in again.

Security checks

For account safety, we may ask for a one-time confirmation, a matching email or a recent activity detail before we act on a sensitive request. That keeps changes tied to the right account.

Record retention

We keep legal and security logs only for the period needed to answer disputes, meet legal duties and prevent misuse. After that period, records are deleted or anonymised according to our internal retention rules.

Change requests

If your contact detail or account record is wrong, send the corrected value and the old value together. Clear pairings help us update the file without guessing, and they reduce back-and-forth.

Contact routes

Use the same email or in-account path for follow-up, so every reply stays attached to one thread. If a request needs extra proof, we will ask for it before making any change.

Open Common Questions on Legal Access

These questions cover access, data, corrections and how we handle request trails. If your concern is tied to a legal or privacy matter, start with the contact route that matches your account details. We will check the record, reply in the same thread where possible and tell you what we can change under local law. If a specific rule applies in your state, we follow that path first.

Yes. You can ask for the account data we hold, the request history linked to it and the security events we store for access checks. We will confirm what can be shared under local law before we send it.

Send the exact field that needs fixing, the current value and the corrected value. If you include the email on the account and any related reference, we can match the record faster and avoid extra follow-up.

You can ask, but we may need to keep some records for legal duties, dispute handling or security logs. If that happens, we will tell you what remains and why, then delete the parts we are allowed to remove.

No. Cookies help with sign-in, session checks and device recognition. They do not remove your right to ask for access, correction or deletion, and they do not replace the account records we keep for legal requests.

We match the request against the account email, the contact route used and any extra proof we ask for. If the details line up, we move ahead. If they do not, we request more context before making a change.

Phone contact may be used only as a first step if we direct you there, but written requests are easier to trace and verify. A saved thread gives you a clean record and helps us respond with fewer delays.

Use the support path that matches your account email and describe the issue in plain words. We will tell you whether it is a data request, a correction, an access question or something that needs another route.