Reference

d55 legal terms for India accounts

Before you open your account, this page sets out how we handle access, records and jurisdiction for India accounts.

India lawAccess rulesRecord keepingAccount checks

Jurisdiction rules and account duties

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

These terms apply to your d55 account, the wallet trail attached to it and the records we keep for legal handling. Where local law permits access, you can use the site from India; where a rule blocks a feature, we leave it unavailable until the rule

1
changes. If your payment route uses UPI, Paytm, PhonePe or Google Pay, we may ask for a matching name, bank reference or device check before we accept a deposit or release a withdrawal. When local law, a court order or a regulator asks for a different
2
practice, that requirement takes priority over our usual process. If we update these terms, we place the new version here and use your registered contact detail when the change affects your account or stored records. Please read this page before you submit documents or move money,
3
because it explains what we can accept, what we must decline and how long we keep the trail for audit or dispute work.

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

REQUEST CHANNELS

Where to send legal requests

If a clause needs plain reading, if you want a correction, or if you need a record checked, use the paths below.

Email a request Send your request from the registered email address and add the account name, phone number and the point you want changed. We use those details to match the request to your record before acting.

Use live chat Use chat if you need a quick read on a clause, a wallet record or a document step. We may move you to email when the request needs verification or an attached file.

Raise a formal case If your concern touches access, retention or a transaction trail, ask for a formal legal case. We log the request, keep the thread on your account and reply through the contact detail you have registered.

RECORD SAFETY

How we handle your records

This page explains how we handle records, cookies, security checks and retention for your account. We verify identity before we change legal settings, correct stored details or release copies of records.

Records we keep

We keep the account name, contact details, device signals and payment references needed to operate the legal side of your account. We do not keep more than we need for handling, dispute checks and tax or audit duties.

Cookie use

Cookies help us keep you signed in, remember form entries and recognise a device that has already passed a check. If you clear them, we may ask you to verify again on the next session.

Account security

We use sign-in checks, session timeouts and change confirmation when a request touches your profile, wallet route or stored documents. If something looks unfamiliar, lock the account by reaching us from the registered contact detail.

Retention window

We retain records for as long as the law, a dispute or a tax obligation requires. After that period, we delete or archive what no longer needs active storage, using the minimum set that still meets the rule.

Change requests

If you want a correction, export or deletion where the law allows it, send the request from your registered email and include enough detail for identity matching. We act only after we confirm the account belongs to you.

Local-law access

Access and eligibility depend on local law, and we adjust the process when that law changes. If a request cannot be completed in your region, we will say so and keep the blocked step out of the flow.

Common legal questions for your account

These answers cover access, records, corrections and contact paths for your account. If you need a record-specific reply, use the contact route in the support section and send the registered email or number so we can match the request to the right file. We keep replies direct so you can see what we can change and what must stay as it is. Where local law changes, the process changes with it.

Where local law permits, you can open and use the account path from India. If a rule blocks access in your region, that part stays unavailable until the legal position changes.

We keep the account name, contact detail, device signals and transaction references needed for legal handling, dispute checks and payment verification. We do not keep unrelated data just because it was sent once.

Yes. Send the request from your registered email or phone and tell us what should change. We verify identity first, then update the record where the law and the account status allow it.

Cookies help us keep your session live and remember the checks you already passed. They do not replace identity checks, and clearing them may mean you need to confirm the account again.

If local law changes, we change the access path and any related legal process to match it. We do not keep a step in place once it is no longer allowed.

Use the support path with your registered name, email and the record detail you want checked. We log the case, keep the reply on your file and answer through the same contact route.

d55 legal terms for India accounts

Where to send legal requests

How we handle your records

Records we keep

Cookie use

Account security

Retention window

Change requests

Local-law access

Common legal questions for your account

01 Who can use the account path from India?

02 What records do you keep about my account?

03 Can I ask for a correction to my details?

04 How do cookies affect my legal settings?

05 What happens if local law changes?

06 How do I contact you about a record dispute?

Related Pages