Reference

dutampo Privacy Policy For Your Account

Our Privacy Policy explains how dutampo handles the details connected with your account, wallet status and device access.

Account recordsWallet referencesDevice signalsPolicy requests
dutampo dutampo Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Help Beside Your Account

A clear contact route matters when you want to ask about personal data rather than a wallet balance. Open the support path beside the cashier area and tell us the account step involved, such as phone verification, a DANA receipt or a QRIS status. We use the details you provide to locate the request and keep the reply focused on your Privacy Policy question. Access remains where local law permits.

Team online

Account data request

Ask us to identify the account records connected with your verified phone step. Include the account reference shown to you, but do not send a password or wallet PIN through support.

Wallet data check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the payment reference and date. We can check the stored status without asking for your private wallet credentials.

Policy contact route

Use the support link beside the cashier path for correction, access or deletion questions. We may request account verification before discussing personal data, helping keep another person from receiving your records.

HANDLING DETAILS

What We Do With Your Privacy Choices

Our handling process separates account access, payment references and support correspondence so each request has a clear purpose.

Account data

We may hold your phone number, verification result, sign-in events and account settings. These details help us recognise your account and investigate an access issue without exposing your login secret.

Payment references

A DANA, OVO, GoPay or QRIS action may leave a rail name, amount status, timestamp and reference. Bank transfer and virtual account records can be checked against the same account request.

Cookies and devices

Cookies and device signals can help keep a session open, remember a language choice or identify unusual sign-in activity. You can manage browser permissions, though some account steps may then need repeating.

Account security

Phone verification before account access helps connect a sign-in with the correct account. We do not ask you to disclose a password, wallet PIN or one-time security code in a support message.

Retention periods

We keep records for the period needed to provide account support, reconcile payment status, address disputes and meet applicable legal duties. When a record is no longer needed, our process allows removal or anonymisation.

Your requested changes

You can ask to access, correct or remove eligible personal data through the support path. We may confirm your identity first, then explain any record that must remain for security or legal reasons.

Privacy Policy Answers For dutampo

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. Each response points to a practical step, from checking a device record to requesting a correction through support. If eligibility or access is part of your question, it depends on local law and the region linked to your account.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention and requests to access, correct or remove eligible personal data.

Yes. The policy covers the DANA or QRIS reference, status, timestamp and related account request we receive. The wallet provider may apply separate privacy terms to its own processing.

Phone verification helps connect an account access attempt with the correct account and helps protect personal data. We may use the verification result when handling a support or account-change request.

You can use the support path beside the cashier area to request access to eligible records. We may ask for account verification before sharing data linked to your phone or payment references.

Send a correction request through support and identify the account field that needs changing. We check the request against your account before updating it or explaining why a record must remain unchanged.

Retention depends on the purpose of the record, including account support, payment reconciliation, disputes, security and legal duties. When the purpose ends, the record may be removed or anonymised.

You may request removal of eligible personal data through support. Some records can remain where needed for security, dispute handling or legal duties, and we will explain that outcome.