Reference

ds160 Privacy Policy for India Account Use

ds160 keeps your privacy terms in one place so you can see what we collect, why we collect it, and how you can ask us to change it.

Data useCookie settingsAccount rightsVerified requests
ds160 ds160 Privacy Policy for India Account Use
REACH US

Ways to reach our privacy team

If you want to ask about this policy, ask for a copy of your stored data, or request a correction where law allows, reach us through the channel linked to your account.

Email us Send the request from the email linked to your account and mention the data you want checked. We use that trail for access, correction, and deletion requests after identity checks.
In-app chat Use chat for a quick policy question about cookies, account data, or a notice on your screen. We may still ask for a small identity check before discussing anything private.
Write to us If you prefer a written request, send your details and the change you want. We keep the record tied to your account and reply through the same verified path.
CARE CONTROLS

How we keep privacy in check

We collect only what is needed to run your account, show the page correctly, secure access, and answer support requests.

Data use

We use account and device data to deliver the service, check requests, and reduce abuse. We do not keep extra fields just because they are available; each record has a purpose and a retention step.

Cookies

Cookies help us remember language, session state, and consent choices. They also help us see whether a page loads as expected, so we can fix broken flows without asking you to repeat every step.

Account security

We use sign-in checks, device checks, and alerting for unusual access attempts. If something looks off, we may pause the session until you confirm that the account belongs to you.

Retention

We keep records only for the time needed for the stated purpose, tax duties, dispute handling, or audit checks where law asks for it. After that, we remove, archive, or mask them.

Verified requests

You, or a person legally allowed to act for you, can ask for access, correction, or deletion. We may need matching account details before we respond, so the right record is used.

Update path

When we change this policy, we replace the page text and keep the latest date with it. If a change affects your account records, we use the contact path on file to tell you.

Questions people ask about privacy

These answers cover the main things you may want to check: what we collect, how long we keep it, how you can ask for a change, and when local law shapes the result. If your request depends on an account record, we use the same verified path you already used so the reply is matched to you and not to someone else.

Mostly the details needed to run your account, secure access, and answer your messages: contact details, device data, IP address, cookies, and the records created when you use the site or contact support.

Cookies remember session state, language choices, and consent settings, and they help us spot load errors or suspicious access patterns. They do not replace the account checks tied to your profile.

Yes, you can ask for a copy of the data linked to your account where local law permits. We will first confirm your identity, then send the record through the verified contact path.

Yes. If a detail is wrong or outdated, send the correction request through your account-linked channel and add any proof that helps us match the right record quickly.

We keep records only for the time needed for the stated purpose, legal duties, dispute handling, or audit checks. After that, we delete, archive, or mask them according to our retention rules.

You can contact us from the email or chat connected to your account, and a legally authorised person can also write in. We may ask for identity checks before sharing anything private.

We replace the page text here, keep the latest version available, and use the contact route on file if a change affects your stored record or request handling.