Reference

bondan69 slot Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, verify your phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsMobile accessPolicy requests
bondan69 slot bondan69 slot Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Privacy and Access

A clear contact route helps you question a record, correct an account detail or ask why a wallet status appears in your account history. Use the support path available from your signed-in account and include the relevant date, payment rail and request type. We use those details to locate the right record without asking you to send a wallet password.

Team online

Account privacy request

Ask us to correct your phone number, contact detail or verification record through the account support path. We may ask for account checks before making a change.

Wallet record question

For DANA, OVO, GoPay or QRIS data, include the transaction reference and displayed status. We can then match the payment event without requesting your private wallet credentials.

Access concern

If a login or phone-verification event does not look familiar, report the date and device path through support. We review the account event and explain the next privacy step.

ACCOUNT SAFETY

Your Account Data From Login to Deletion

We keep this policy practical by connecting each data purpose with an account action you can recognise.

Data we receive

We may receive your phone number, login details, verification result, payment reference and support messages. Device and browser signals help us identify unusual sign-in activity around your account.

Cookie choices

Cookies and similar browser storage can remember a session, protect the sign-in path and measure page use. You can manage browser permissions, though some account functions may then need another login.

Account security

Phone verification is checked before account access, while sign-in events and device changes may be recorded for security review. Never send your wallet PIN or password in a support message.

Payment matching

For DANA, OVO, GoPay, QRIS and bank transfer, we retain references and status details needed to reconcile an account entry. We use the record for the transaction purpose rather than wallet credentials.

Retention approach

We retain account, security and transaction records only for the operational, dispute or legal period connected with their purpose. When that need ends, records are removed or handled in a restricted form.

Requesting changes

You can ask who handles a data record, request a correction or ask about removal through account support. Include your account contact and the record date so we can verify the request.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers focus on the account actions you are most likely to check before opening an account or contacting support. They cover phone verification, mobile browsing, wallet references, cookies, retention and requests for access or correction. If your situation is not listed, send the relevant account date and we will direct the question through the available privacy route.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and protect the account, send the verification step and check account ownership when you request a correction or report an unfamiliar login.

Yes. When you sign in from a phone or tablet browser, we may record browser type, device signals and security events so we can recognise unusual access and maintain the account session.

We store the payment reference, displayed amount, status and time needed to match the event with your account. We do not need your QRIS PIN, DANA password or wallet login.

Use the signed-in support route and name the field that needs correction, such as your phone number or contact detail. We may verify account ownership before changing the record.

Retention depends on the purpose of each record, including account security, payment matching, dispute handling and legal needs. When the purpose ends, we remove or restrict the record.

Yes. Send a privacy request through account support with your contact detail and the relevant date. We will check the request, explain the available record and apply local-law requirements.