Reference

master 4d slot Privacy Policy

DANA, QRIS and your account login each create clear data points, so our Privacy Policy explains what we collect, why we use it and how you can ask…

Account clarityWallet contextMobile access
master 4d slot master 4d slot Privacy Policy
HELP WITH PRIVACY

Three ways to ask about your data

A direct question should not require you to search through payment screens. Our support route helps you ask about the Privacy Policy, check which account detail needs correction and understand a wallet-status record linked to DANA or QRIS. Use the same account details you normally use for login so we can distinguish your request from an unrelated message. If you are in Yogyakarta or elsewhere in Indonesia, the support path remains available through the site wherever local law permits.

Team online

Account help

Use the account support path when you need to confirm the phone number, login record or verification detail connected with your Privacy Policy request. We may ask for account identifiers, but never ask for your wallet password or full payment credential.

Wallet records

Choose the payment-status route when your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account reference. Share the receipt or reference shown to you so we can locate the relevant record without requesting unnecessary wallet access.

Correction request

Ask support to correct an inaccurate contact or account detail through the site help path. We review the request against your account step and may verify ownership before changing records, helping prevent another person from altering your Privacy Policy data.

DATA CARE DETAILS

Six controls behind our Privacy Policy

The Privacy Policy is supported by practical controls rather than broad promises. We separate account details from wallet credentials, use session signals to spot unusual device activity and limit internal access to…

Account collection

We collect the contact and verification details needed to create and protect your account. A clear phone verification step helps us confirm access before you reach account features, while optional details are not treated as necessary login data.

Device signals

A mobile browser or desktop session may share operating system, browser type, approximate session timing and security events. We use these signals to recognise unusual login behaviour, not to read private content stored on your device.

Wallet separation

For DANA, OVO, GoPay and QRIS, we record payment references and status needed to match a transaction. Bank transfer and virtual account checks follow the same principle: status data supports reconciliation without collecting your wallet password.

Cookie choices

Cookies and similar storage can retain sign-in continuity, security preferences and basic page settings. If you clear them, you may need to verify your account again or repeat a preference before continuing on mobile.

Retention checks

We review account, device and payment records against their operational purpose. Records may remain when needed for reconciliation, a support question, a dispute or a legal duty, then are removed or de-identified when that purpose ends.

Your request

Contact us through the site support path to ask what we hold, correct an error or request removal where local law permits. Include your account contact and the subject of the request; we verify ownership before disclosure or changes.

Privacy Policy answers for your account

These Privacy Policy answers focus on the searches Indonesian customers make before opening an account. They explain the practical link between login, mobile device signals, local wallet references and requests sent to support. Read them with the full policy, and contact us through the account help path if your situation needs a record-specific response. Access and any request outcome depends on local law.

It covers account creation, phone verification, login activity, device signals, cookies, support messages and payment references. It explains how we use those details for access, security, reconciliation and service, plus how you can ask for access or correction where local law permits.

No. We use the transaction status and reference needed to connect DANA or QRIS activity with your account. We do not need your wallet password. Bank transfer and virtual account checks use the same limited approach for payment matching.

Your browser type, operating system, session timing and security events can help us identify unusual sign-ins and keep account access working on mobile. The Privacy Policy treats these as security and service signals, not as permission to read private files or messages.

Use the site support path and state which account detail is inaccurate, such as a contact number or verification record. We may confirm account ownership before making a change. This protects your account while giving you a clear route to request correction.

We retain records for the period needed for account service, payment reconciliation, support, disputes or legal duties. When a purpose ends, we remove or de-identify the relevant record where possible. The exact outcome depends on the record and local legal requirements.

You can send a deletion request through account support where local law permits. We first verify ownership, identify the requested records and explain if some details must remain for reconciliation, a dispute or a legal duty before any available removal is completed.

Send it through the support path on our site using the account contact linked to your login. Describe whether your question concerns device data, cookies, DANA, OVO, GoPay, QRIS or account access so we can direct it to the right record.