Reference

d365 Privacy Policy for India Accounts

d365 keeps your privacy policy easy to read: one page for account data, device signals, cookies and payment checks tied to your use.

India accountsCookie useData checksLocal law

Browse Lobby Read FAQ

What This Policy Covers in India

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

We collect the data needed to keep your account working, confirm requests and settle payment actions you start from India. That can include your name, contact details, device signals, login history, cookie data and the records tied to UPI, Paytm or PhonePe transactions. We use it

1
for account security, fraud checks, service messages, legal compliance and to respond when you ask for access, correction or deletion where local law allows. We may share limited data with payment partners, hosting vendors and verification partners who act for us under contract. We keep records
2
only for as long as needed for the account, dispute handling and tax or legal duties in the region tied to your profile. Where data has to stay longer, we keep the stored set as small as possible and separate active account data from archived records.
3
If access or eligibility is mentioned anywhere on this page, it depends on local law and is available where local law permits. That same rule applies to any request that reaches us from outside India.

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

CONTACT ROUTES

Contact Paths for Privacy Requests

If you want help with a privacy request, start from the contact path that matches your issue.

Email Send your request from the email tied to your account, name the change you want, and attach any proof we ask for. We use those details to match the request before we update records where local law allows.

Chat Use chat when you need a quick route to the privacy team. We can explain the next step, list the checks needed and move the request to the right queue without making you repeat details.

Phone If email is not easy, phone support can route your request. We still verify the account first, then explain what we can change, what we must keep and what the local rule allows.

HANDLING PRACTICE

How We Handle Account Data

We keep the policy practical: collect only what we need, separate payment logs from general browsing data, and limit staff access to the smallest set needed for the task.

Collection

We collect account, device and transaction data only for the services you use. We do not ask for extra details unless a check, payment action or legal duty needs them, and we keep each field tied to a clear purpose.

Cookies

Cookies and similar tools keep session state, remember language choices and help us spot unusual access. You can adjust browser settings, but some pages may not work the same once those tools are turned off.

Security

Access to privacy records is restricted to staff who need it for support, verification or legal handling. We use account checks before we disclose, change or delete records, and we log the request path for audit use.

Retention

We keep records for the account period and for any dispute, audit or tax duty that still applies after closure. After that, we remove or de-identify data when possible, subject to backup cycles and legal hold rules.

Access Requests

If you want a copy of your data, a correction or a deletion request, send it from your registered email and include enough detail for us to verify the account before we process anything.

Change Requests

When a change affects linked payment records or legal logs, we may keep a backup record of the old entry. That helps us show what changed, when it changed and why the record stayed.

Common Privacy Questions for d365

These are the privacy questions we hear most from India accounts. If a request needs identity checks, we ask for the minimum proof needed to protect the account. Where local law permits, you can ask for access, correction, deletion or a copy of the records linked to your account. If a request touches payment logs or legal retention duties, we explain the limit plainly before we act. That way you know what we can do and why.

We keep the details needed to run your account, process requests and secure access. That can include contact data, device signals, login history, cookie data and records tied to the payment path you chose.

Yes, where local law permits. Send the request from your registered email, let us know what you want copied, and we will verify the account before we share the records that apply.

Cookies help us keep your session active, remember language choices and detect unusual logins. You can change browser settings, but some parts of the page may not behave the same without them.

Only where it is needed to process a deposit, withdrawal or related check. We share the minimum set with the payment partner, and only under the contract and legal duties that apply.

Write from the email linked to your account, name the field you want corrected and add proof if we ask for it. After verification, we update the record or explain why we must keep it.

Use the contact path that matches your issue: email, chat or phone. We will route the request to the privacy team, confirm what we need and tell you the next step.

d365 Privacy Policy for India Accounts

Contact Paths for Privacy Requests

How We Handle Account Data

Collection

Cookies

Security

Retention

Access Requests

Change Requests

Common Privacy Questions for d365

01 What data do you keep from my account?

02 Can I ask for a copy of my data?

03 How do you use cookies?

04 Do you share data with payment partners?

05 How can I correct my details?

06 How do I contact you about privacy?

Related Pages