Reference

Privacy Policy for India Accounts

Our Privacy Policy explains what data we collect when you open an account, use the wallet, contact support, or set cookie choices on dhankeshri.

Account dataCookie choicesUPI recordsSupport requests
dhankeshri Privacy Policy for India Accounts
CONTACT ROUTES

Three Contact Paths for Privacy Requests

You can reach us about this Privacy Policy through the same account channels you use for service queries, but privacy requests are handled as a separate…

Privacy email Send a privacy request to our email team with your registered contact detail and…
Live chat handoff Start with chat if you are already signed in and need the privacy team…
Account form Use the account form when you want to update contact details, correct spelling, or…
CARE CONTROLS

Six Controls Behind Your Data

Privacy depends on everyday account checks, not only legal wording. We limit access to account records, keep wallet references tied to verification steps, and separate support messages from public lobby activity.

Account verification

Before we share account data or make a correction, we may confirm your registered mobile, email, recent login details, or wallet reference. This reduces the chance of another person changing your records.

Payment record matching

UPI, Paytm and PhonePe references are used to match deposits or withdrawals with your wallet. We do not need your banking password, and you should never send it to support.

Cookie settings

Cookies help keep your session active, remember basic preferences, and flag unusual access patterns. You can clear cookies in your browser, though some account and security checks may need them again.

Access control

Account, wallet and support records are available only to staff or service partners who need them for a defined task. Internal access is limited, logged where practical, and checked against work purpose.

Retention checks

We keep records for account service, dispute handling, tax, security and legal needs. When retention is no longer required, we aim to delete the data or remove details that identify you.

Correction requests

If your name, email, mobile number or payment reference is wrong, ask us to check it. We may need proof before changing stored data, especially where wallet history is involved.

Privacy Questions Before You Join

These answers explain common privacy points before you open an account or send us a request. They focus on what we collect, why we need it, how payment data is handled, and how you can contact us. If your question involves local law, the outcome may depend on where you live and the records linked to your account.

It covers account details, contact data, login records, cookie data, wallet activity, support messages and payment references. It also covers documents or screenshots you choose to send when we need to verify a request.

We use payment references to match wallet transactions with your account, check failed or delayed entries, and answer payment queries. We do not ask for UPI PINs, banking passwords or private app access.

Yes, you can ask us to share the account data we hold where the law allows. We may verify your identity first, then provide a practical response based on the records available.

Contact us through email, chat handoff or the account form and state what needs correction. We may ask for proof, especially for mobile numbers, email addresses, name spelling or payment references.

Cookies store session details, remember settings and help us detect unusual account access. You can clear them through your browser, but signing in again may recreate cookies needed for account security.

Support messages are handled by team members or service partners who need them to answer your case. We restrict access by work purpose and avoid sharing more account data than the request needs.

Retention depends on account service, dispute needs, tax records, security checks and legal duties. When data is no longer needed, we aim to delete it or remove details that identify you.