Reference

pendanaan Privacy Policy, Clearly Explained

Our Privacy Policy explains what pendanaan collects when you open an account, sign in, use DANA or QRIS, and contact account support.

Account dataWallet recordsDevice signalsSupport requests
pendanaan pendanaan Privacy Policy, Clearly Explained
ACCOUNT HELP

Privacy Questions Near Your Account Path

A clear contact route matters when a Privacy Policy question relates to a phone check, wallet receipt or device sign-in. Start from account help and include the email or phone detail attached to your account, plus the relevant date and payment reference when your request concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a full wallet password or private access code.

Team online

Data access requests

Ask us which personal details are linked to your account and why they are used. Include your account contact detail so we can confirm the request before sharing any record.

Correction requests

If your phone number, verification detail or account contact is wrong, contact account help with the change requested. We may ask for an account step to confirm that you own the record.

Wallet record checks

For a DANA, OVO, GoPay or QRIS question, provide the payment reference and receipt time rather than your wallet password. We use that narrow detail to trace status safely.

SECURITY PRACTICE

What Our Privacy Process Covers

We keep the Privacy Policy practical by separating account access, wallet records, device signals and support correspondence.

Account collection

We collect the contact and verification details needed to create and protect your account. A phone check can connect your request to the correct record before we disclose or change anything.

Payment references

A wallet or bank transaction reference helps us match a receipt to an account action. We do not need your wallet password to investigate a DANA, QRIS or bank transfer status.

Device signals

Browser, device and connection signals can help us spot unusual sign-ins or repeated account attempts. These signals support access protection rather than replacing your phone verification step.

Cookie controls

Cookies can preserve your session and remember selected page settings. You can adjust cookie permissions in your browser, though refusing some cookies may interrupt sign-in or require another account check.

Retention choices

We retain account, payment and support records only while they serve an operational, security or legal purpose. When a record is no longer needed, our handling follows the applicable retention process.

Policy requests

To request access, correction or removal of eligible details, contact account help with your account contact and a focused description. We confirm ownership before changing or releasing personal data.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers focus on the questions you may have before opening a pendanaan account from Indonesia. They explain account data, payment references, cookies, device checks and request handling without asking you to reveal private access credentials. If your situation depends on a specific region or eligibility rule, access depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support correspondence. It also explains how we use, retain and protect those records when you access the service where local law permits.

No. For a DANA, OVO, GoPay or QRIS status question, we generally use a transaction reference, receipt time and account contact. Never send a wallet password or private access code in a support request.

Phone verification helps connect an account request to the correct person and reduces mistaken access to another account. We may use the verified contact when handling a Privacy Policy request, correction request or sign-in concern.

Where local law permits, you can ask for the personal details linked to your account and the purpose for using them. Contact account help with your account contact; we confirm ownership before responding.

Send account help the detail that needs correction and the replacement value you want recorded. We may request a phone verification or another account step before changing contact, verification or support records.

We keep records for as long as they support account operation, security checks, payment tracing or a legal need. After that purpose ends, handling follows the applicable retention process rather than indefinite storage.

Yes. Your mobile browser provides cookie controls in its privacy or site-settings path. Refusing some cookies can end a session or require another sign-in check, so account access may behave differently after the change.