Reference

Open your d400 privacy choices

d400 keeps your account data, UPI, Paytm and PhonePe wallet records, device signals and cookie choices explained in one Privacy Policy, so you can see what we collect…

Account data controlsCookie choice detailsUPI and wallet recordsPrivacy request paths
d400 Open your d400 privacy choices
CONTACT ROUTES

Check your privacy contact paths

Privacy requests work better when you contact us from the same account email or mobile number used on d400.asia. Tell us what you need changed, copied, restricted or deleted, and include any wallet reference only when it helps us locate the record. We may ask for account checks before acting, so your data is not handed to the wrong person.

Team online

Privacy email

Write to [email protected] for copy, correction, deletion or cookie-related requests. Use your account email, keep the message specific, and avoid sending full bank or UPI PIN details.

Account help inbox

Open the help inbox after login when your request relates to wallet records, device access or identity checks. We can match the request to your account without asking for extra screenshots.

Security contact

Use the security contact path if you think your login, mobile number or wallet reference was used without permission. We review access logs and may pause account changes while checks run.

DATA CARE

Browse our privacy handling checks

Our privacy work is tied to the account flow you use each time you log in, verify a wallet action or change device.

Data collected

We collect account name, contact details, login records, wallet references, device data and support messages when they are needed for access, security, transaction tracing or a privacy request you send.

Cookie controls

Cookies help keep you signed in, remember language choices and read basic site health signals. You can manage browser cookies, though some account checks may need cookies to work correctly.

Account security

Login alerts, device checks and session records help us detect unusual access. If a privacy request could affect account safety, we confirm identity before copying, changing or deleting records.

Retention checks

Wallet, identity and dispute records may be kept while legal, tax, audit or security reasons apply. After that, we delete, shorten or separate records from your account where possible.

Shared processors

We may use payment, hosting, analytics, fraud-control and support service providers. They receive only the data needed for their task and must protect it under written privacy and security terms.

Change requests

You can ask us to correct contact details, update consent choices, provide a data copy or delete records where law allows. We explain any refusal in plain language.

Discover answers on privacy rights

These answers focus only on how the Privacy Policy works on d400.asia. They explain what data we collect, why payment references appear, how cookies are used and how you can contact us about your rights. If a request involves account safety or wallet history, we may need identity checks before we make any change.

We collect account contact details, login records, device signals, wallet references, cookie choices and messages you send to support. Each record is tied to account access, security, transaction tracing or privacy request handling.

Those names help describe wallet records connected to your account. We may store transaction references, timing, status and support messages, but we do not ask you to share UPI PINs or full banking secrets.

Email [email protected] or use the logged-in help inbox. Send the request from your account contact details, state that you want a data copy, and complete any identity check we require.

Yes, you can ask us to correct contact details or account records that are inaccurate. Some wallet, security or identity records may need verification before we change them, especially after a transaction query.

We keep records while they are needed for account access, legal duties, tax checks, disputes, security and request handling. When those reasons end, we delete, shorten or separate records where practical.

Cookies can remember login sessions, language choices and basic site health signals. You can control cookies in your browser, but disabling some cookies may affect account access or security checks.

Only teams that need to handle the request, such as privacy, security, support or wallet operations, can access relevant records. We record handling steps so changes can be traced internally.