Reference

Privacy Policy for India accounts

Your account data, UPI, Paytm and PhonePe records, cookie choices and support messages are covered in this Privacy Policy before you join dq41.

UPI data contextPaytm record handlingPhonePe privacy checksCookie choices
dq41 Privacy Policy for India accounts
PRIVACY HELP

Privacy contact paths for your account

Your privacy request should reach a person who can act on account data, not a general inbox that loses context. Use the route that matches your situation: email for formal requests, chat for quick clarification, and a help ticket if access to your registered email has changed. We may ask for verification before sharing, correcting or deleting data so another person cannot take control of your privacy request.

Team online

Email privacy desk

Write to [email protected] from the email linked to your account. Include your account ID, the data request you want handled, and a contact number if you prefer a call-back.

Live chat request

Use in-account chat when you need a quick privacy clarification. Our agent can raise a privacy ticket, confirm your identity checks, and send the next steps to your registered email.

Account help ticket

If your email access has changed, open a help ticket after login. We ask security questions first, then route correction, export or deletion requests to the privacy team.

DATA HANDLING

Data controls across UPI and lobby

Each control below links a privacy promise to the way your account actually works. We separate identity details from wallet logs, limit access to staff who need a task record, and keep…

Account data mapping

We map the data you provide during account opening, login and KYC checks to clear purposes. That includes contact details, identity documents, device identifiers and security events needed to protect access.

UPI payment privacy

UPI, Paytm, PhonePe and Google Pay references are used to reconcile wallet entries, handle failed transfers and verify withdrawals. We keep only the payment details needed for account records and legal duties.

Cookie choices

Cookies help keep you signed in, remember language settings and detect unusual access attempts. Where a cookie is not essential, we explain its role and provide a practical way to change consent.

Access security

Login records, device signals and one-time verification steps help us detect account takeover attempts. Staff access to sensitive data is limited, logged and checked when a privacy request is processed.

Retention schedule

We keep account and transaction records only for as long as they are needed for service, dispute handling, fraud checks, tax or legal duties, then remove or anonymise them when allowed.

Correction requests

If your name, mobile number, email or payment reference needs correction, contact us through the privacy routes above. We verify ownership first, then update records or explain why a change cannot be made.

Privacy questions before you join

These answers cover the privacy points you may want settled before opening an account. They focus on what we collect, how payment records are used, when data is shared, and how you can reach us for correction, access or deletion requests. The same privacy process applies whether you use mobile data, home Wi-Fi or a shared device.

We collect the details needed to create and protect your account, such as name, mobile number, email, login records, KYC documents, wallet activity, device identifiers, game session records and support messages.

We share payment details only with processors, banks, verification partners or advisers who need them for a defined task, such as reconciling a transaction, checking a withdrawal or responding to a lawful request.

Cookies keep your session active, remember basic preferences and help detect unusual login patterns. Some cookies are essential for account access, while optional cookies can be managed through the choices shown on the site.

Yes, you can ask us to delete personal data through email, chat or a help ticket. Some records may be kept for a required period because of payment disputes, fraud checks or legal duties.

You can request correction of contact details, spelling errors or outdated payment references. We verify that the account is yours, apply the correction where allowed, or explain why the record must stay unchanged.

Retention depends on the type of record. Login logs may be shorter, while payment, withdrawal and identity records may stay longer for dispute handling, security checks, tax or legal requirements before removal.

Yes. Account access, eligibility and certain data rights depend on local law and are available where local law permits. If a privacy request is affected, we explain the reason in our reply.