Reference

Open spin2x Legal Terms for India

This page sets out how we handle account use, data, and policy requests on spin2x.

India accountsLocal lawCookiesData use
spin2x Open spin2x Legal Terms for India
REQUEST CHANNELS

Browse Contact Paths for Requests

When you need help with this page, start from the contact paths inside your account.

Email the team Send a message from your registered email and mention the account name, the request type, and any date range. We use that match to find the right records before we reply.
Use in-app chat If you are logged in, open chat and ask for a data copy, correction, or access check. We will ask for matching details before any change leaves the queue.
Postal request For formal requests on paper, use the postal address listed in your account area. Mark the envelope for legal handling so it reaches the right team without delay.
RECORD CARE

Explore How We Handle Your Records

We handle this policy area with the same checks we use for account access: the request must come from a matched channel, and the result is logged for future reference.

Data use

We use account details, device signals, and session logs to run the page, check access, and settle disputes. That use stays limited to the purpose that created the record, not a wider profile.

Cookie settings

Cookies remember sign-in state, language choice, and consent selections. You can clear browser storage at any time, though some server-side records remain if we still need them for law or account handling.

Login safety

Keep your password private and use only the channels listed in your account area. We never need your full password over chat or email, and any change request goes through a matching check.

Record retention

Some records stay after closure for the period required by law, tax, dispute handling, or fraud checks. After that period ends, we remove or anonymise the parts that no longer need to stay in readable form.

Change requests

If you spot an error in your name, contact detail, or linked wallet record, send a correction request from the registered account. We verify the match first, then update what the record allows.

Contact trail

Each legal request gets a traceable ticket so you can ask for a status update later. If more proof is needed, we will say exactly what to send and which channel to use.

Open Questions on This Policy

These are the questions we get most often about access, data, and request handling. The same rule applies across them all: we verify the account first, we act only within the record kept for that account, and we follow local law where it applies. If your region is not eligible, we will say so in the reply tied to your request.

We keep the details needed to match your account, confirm access, run support checks, and keep legally required records. That usually includes contact details, device logs, and payment traces linked to the action you asked us to process.

Yes. Send the request from the registered account or the email linked to it, and we will confirm the match before sending any copy we are allowed to share. Some records may stay private where law requires.

Yes. Tell us which field is wrong, attach the right value, and use the channel tied to the account. We verify the request first, then update the record if the change is allowed by law and system rules.

We compare the request against the contact details, login history, or other account markers already on file. If the match is weak, we may ask for a second step before we act on the request.

We keep records only as long as needed for law, accounting, dispute handling, or fraud checks. After that period ends, we remove or anonymise the parts that no longer need to stay in readable form.

Access depends on local law and is available where local law permits. If the rule does not allow use from your location, we will not continue the account action and will point you to the next step in the reply.