Reference

Legal terms for India access

This page sets out the legal side of wildpunt for India: how access works, what we collect, how long we keep records, and where to send change requests.

India accessLocal lawData useAccount records

Explore the lobby Read FAQ

Jurisdiction and policy scope

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

Our legal position follows the place from which you access the site. Where local law permits access, you can use the account flow under the current terms; where it does not, the affected feature remains closed. We may ask for identity, payment, or device checks before

1
approving changes, closing an account, or releasing funds linked to that account. We keep records needed for fraud control, dispute handling, tax duties, and audit trails, then remove or archive them under the retention rule that applies. Browsing data, cookies, and login logs may be stored
2
to secure sessions and remember your settings. If you want a copy, correction, or deletion request, send it from the email tied to your account so we can verify the request cleanly.

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

REQUEST PATHS

How to send legal requests

For legal requests, the fastest path is the contact form inside your account. You can also write from your registered email if you want a dated record of the request.

In-account form Use the form in your account for corrections, closures, or access requests. It gives us the exact account context, stamps the request, and sends it to the team that handles legal matters for India.

Registered email If you prefer email, write from the address linked to your account and state the request in plain words. That helps us verify identity, locate the correct records, and reply through the same channel.

Escalation thread For a follow-up on a pending matter, reply to the same thread instead of opening a new one. Keeping one chain helps us trace the history, avoid duplicate checks, and process the request in order.

DATA HANDLING

How we handle records and access

We keep legal records tied to the account you open, not to casual browsing. Cookies and session logs help us secure logins, spot repeated errors, and keep your preferences in place.

Data handling

We collect only the details needed to run the account, verify requests, and meet legal duties. That can include name fields, contact details, device logs, and transaction references linked to your profile.

Cookies and logs

Cookies help us remember login state and language settings, while logs record access events, error events, and security checks. Those records support dispute handling and help us spot unusual activity on the account.

Account security

Please keep your password private and use a device you control. If we see a risky login pattern, we may pause access until you confirm the account, because legal and security checks often move together.

Retention

We keep records only for as long as the law, tax rules, or dispute handling requires. After that period, the data is removed, anonymised, or archived under the rule that applies to that record type.

Change requests

You can ask for a correction, copy, or deletion request from the email linked to your account. Please describe the exact field or record, so we can verify it and apply the right retention rule.

Contact route

If the matter is urgent, use the account form first and then reply by email if we ask for proof. That keeps the request linked to one file and shortens the back-and-forth needed for checks.

Legal questions we hear most

These answers explain how our legal terms work in practice, from access rules to record handling. If your location, request, or payment trail needs a different rule, we follow the law that applies to your case and the account data we hold.

The law that applies is the one tied to your location and the service you use. If local law allows access, the account remains open under the current terms; if not, the affected feature stays unavailable.

Yes. We may ask for identity or payment proof when the request affects account changes, withdrawals, or a dispute. That check helps us make sure we act on the right account and follow the correct legal rule.

Cookies help us keep you signed in, remember settings, and protect the session from misuse. We also use logs to track errors and access events, which helps when we need to resolve a request tied to your account.

Yes. Send the request from the email linked to your account and say which records you want. We will verify the request, check what the law allows, and then share the data we are able to provide.

We keep records for the period needed for legal duties, tax checks, dispute handling, and account security. After that, the data is removed, anonymised, or archived according to the retention rule that applies to it.

If the local law does not allow access from your region, the affected part of the site stays closed. We do not ask you to bypass that block, and we apply the same rule to similar requests from that location.

Use the account form or write from your registered email, then state the exact field you want changed. Clear details help us verify the request, locate the record, and respond under the correct legal process.

Legal terms for India access

How to send legal requests

How we handle records and access

Data handling

Cookies and logs

Account security

Retention

Change requests

Contact route

Legal questions we hear most

01 Which law applies to my account?

02 Can you ask for identity proof?

03 How do you use cookies on this page?

04 Can I ask for a copy of my data?

05 How long do you keep records?

06 What if my region does not allow access?

07 How do I contact you about a correction?

Related Pages