Reference

duit123 Privacy Policy For Your Account

The duit123 Privacy Policy explains how we handle your account details, phone verification, device access and wallet records for DANA, OVO, GoPay and QRIS.

Account data clarityWallet record handlingCookie choicesContact for changes
duit123 duit123 Privacy Policy For Your Account
CONTACT WHEN NEEDED

Get Clear Answers About Your Privacy

A privacy request should not leave you guessing which account step to describe. We route questions through the contact path shown in your duit123 account area, where you can identify the relevant…

Account privacy request Ask for a copy, correction or clarification through the account contact path. Mention your registered phone number so we can match the request without asking for unrelated details.
Wallet record question For DANA, OVO, GoPay or QRIS records, include the transaction reference and date shown in your account. Never send a wallet PIN or full authentication code.
Device access concern If a mobile browser or desktop session looks unfamiliar, tell us the device path and account step affected. We can direct you through verification before discussing private account data.
HOW WE HANDLE DATA

Your Account Data Across Devices

Privacy controls work best when they follow the way you actually access your account. Our handling covers the account record, payment references, browser cookies, verification events and security checks connected with your…

Account details

We use your account details to create access, complete phone verification and respond to requests made through the account contact path. Keeping these details current helps us identify the right record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a requested cashier action. We do not need your wallet PIN to investigate a status.

Cookies and browser data

Cookies can retain session preferences and help the mobile lobby load the selected account state. Your browser settings can remove or block cookies, though some account steps may then need repeating.

Account security

Phone verification and session checks help us confirm that an account request comes from the correct account holder. We may ask for an additional check before changing private account details.

Retention period

We retain account and transaction records for as long as needed for the stated account purpose, security checks, dispute handling or legal duties. When no longer needed, records follow our deletion process.

Requests and corrections

You can ask us to correct account details, explain a data use or discuss removal through the contact path shown after login. We may verify your identity before making the requested change.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account actions that matter when you use a local wallet, change devices or ask us to update your record. Each response describes the practical route first, including the account contact path and the checks that protect your details.

It covers account details, phone verification, browser cookies, device sessions, payment references and contact requests connected with your duit123 account. It also explains retention, corrections and security checks.

Phone verification helps us connect an account request to the correct account holder. We may use it before discussing private details, changing account data or responding to an access concern.

Yes. The policy covers DANA, OVO, GoPay, QRIS, bank transfer and virtual account references used to match an account action. We do not ask for your wallet PIN.

Use the contact path shown in your account area and describe the record that needs correction. Include your registered phone number only when requested; we may verify identity before changing it.

Cookies can remember session settings and help a mobile browser return to the correct account state. You can manage them in browser settings, but blocking cookies may repeat verification steps.

We retain records for the account purpose, security checks, dispute handling or legal duties that apply. When a record is no longer needed, it follows our deletion process.

Yes. Contact us through the account route and name the device type, browser path and affected account step. We can begin a security check before sharing private session details.