Reference

Your legal terms, in plain English

On diamondexch, this page sets out how we handle access, data use and account requests for India.

India accessLocal lawData useAccount requests

Jurisdiction rules and local access

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

This notice explains the legal position that applies to diamondexch in India. Access is not universal; it depends on local law and is available only where local law permits. We may ask for identity checks before account changes, record corrections or withdrawal-linked verification, because those steps

1
help us keep a clear trail and answer disputes later. When a payment record appears in UPI, Paytm, PhonePe or Google Pay, we keep it with the account file only as long as we need it for reconciliation, dispute handling or a legal duty. If a
2
state, union territory or other local rule changes what can be accessed, we follow that rule before we allow further use.

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

REQUEST ROUTES

How to reach us on policy

If you need help with legal access, record changes or a privacy question, we keep three contact routes open.

Email request Send legal or data questions to our mailbox with your account name, mobile number and the exact change you want. That lets us match the right record and answer inside the correct legal frame.

In-app form Use the form linked from the account area when you need a correction, access copy or closure request. The form keeps the thread attached to the right record and reduces back-and-forth.

Written follow-up For matters that need extra proof, we may ask for a written follow-up with a clear reason and supporting details. That helps us verify the request before we change or remove anything.

DATA HANDLING

How we handle records securely

We handle policy requests as part of your account record, not as a general mailbox thread.

Data handling

We collect only the fields needed for account access, verification, transaction history and support replies. If a field is no longer needed, we remove it unless a legal duty requires us to keep it longer.

Cookies

Cookies help the site remember sign-in state, language choice and consent settings. If you clear them, some pages may ask you to verify again, because the browser can no longer link the session to your record.

Account security

We use login checks, device checks and session timeouts to reduce unauthorised access. If you suspect a change you did not ask for, contact us quickly so we can lock the record and check the trail.

Retention

Retention periods depend on the request type, the payment trail and any legal duty to keep audit records. When the hold period ends, the file is removed or archived under our internal retention rules.

Change requests

To ask for a correction, update or deletion, send the exact field, the corrected value and a short reason. We may ask for proof before we alter the record, especially where the request affects access.

Contact route

For legal questions, use the same support path each time so the thread stays linked to your account. That makes it easier to trace earlier replies, verify identity and resolve the request without confusion.

Common legal questions for your account

These questions cover access, record use and the way we handle requests tied to India. If your situation is different because of local law, we follow the rule that applies to your location and account record. For anything that depends on proof or verification, send the request from the contact path listed here so we can answer it against the correct file.

Yes. Access depends on local law and is available only where local law permits. If your state or territory has different rules, we follow those rules before we let you proceed or change an existing record.

We keep the fields needed for identity checks, account control, payment records and dispute handling. If a field is no longer needed, we remove it unless a legal duty or audit hold requires retention.

Send the exact field, the corrected value and a short reason. We may ask for proof before we update the record, especially when the change affects access, payment trails or security checks.

Cookies help us remember sign-in state, language choice and consent settings. If you clear them, some pages may ask you to verify again, because we cannot link the same device automatically.

Retention depends on the request, the account history and any legal duty to keep records. We hold what we need for audits, dispute handling and safety checks, then remove or archive the file when the hold ends.

Use the contact route on this page, and send the request from the registered mobile if the matter affects an account. That helps us match the file and answer without mixing records.

Send a closure request through the support path, and we verify it against the account record first. Some records may still be kept for legal or audit reasons after closure, but active access stops where law permits.

Your legal terms, in plain English

How to reach us on policy

How we handle records securely

Data handling

Cookies

Account security

Retention

Change requests

Contact route

Common legal questions for your account

01 Does local law change my access?

02 What do you keep in my file?

03 How can I request a correction?

04 Do cookies affect my legal requests?

05 How long do you keep records?

06 Who should contact you about access?

07 What happens after account closure?

Related Pages