Reference

Your bank99 Privacy Policy In One Place

Your bank99 Privacy Policy explains what we collect when you create an account, sign in, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesAccess rights
bank99 Your bank99 Privacy Policy In One Place
HELP WITH REQUESTS

Get Policy Help Near Your Account

A privacy question should not slow down your account access. Our support route is connected to the account area, so you can identify the phone number, wallet reference or device involved without sending unnecessary details in a public message. Use the contact path shown after sign-in for questions about a data request, cookie choice, payment reference or correction. If access is unavailable, use the support route displayed on the bank99 page and include only the details needed to locate your account.

Team online

Data request

Ask us to explain the account details, phone verification record, device signal or payment reference connected with your bank99 account. We may ask you to confirm account ownership before discussing personal data, so a request cannot be redirected to the wrong person.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the transaction date and visible status rather than a full wallet password. We use the available reference to check the record while limiting the personal details shared in support.

Access assistance

If your login or phone verification blocks a policy request, tell us which device path you used and where the step stopped. We can direct you to the account contact route without asking for your password or requesting unnecessary copies of identity documents.

DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by separating account operation from optional preferences.

Account records

We use the details you provide during account opening, including your contact information and phone verification result, to create access…

Device activity

Login time, browser or device signals and session events can help us detect unusual access and restore the correct account…

Cookie choices

Cookies can remember a sign-in state, language preference or page setting, while necessary cookies support core account access.

Payment references

We may retain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference to match a deposit or status…

Retention periods

We keep records for as long as needed for the purpose described in the Privacy Policy, account protection, dispute handling…

Changes and contact

You can ask for a correction, access request or explanation through the account contact path.

Privacy Policy Answers For bank99

These Privacy Policy answers cover the questions most often raised before account opening or after a wallet status check. Each answer stays focused on the data connected with your bank99 account, device and payment path. If your situation involves access or eligibility, it depends on local law, and the account contact route remains the right place for a case-specific request.

The bank99 Privacy Policy covers account details, phone verification, device and session signals, cookie choices, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain, and how you can request access or correction.

Yes. The Privacy Policy explains how we use a DANA or QRIS reference to match a payment status with your account. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We ask for a visible reference, not your wallet password.

We collect limited device and login signals to protect your account, recognise an unusual sign-in and understand where an account step stopped. A mobile path may produce different technical events from desktop access. These records support account security and are handled under the Privacy Policy.

Use the account contact path shown on bank99 after sign-in and state that you want a personal data request under the Privacy Policy. Include the account contact detail needed to locate you, but never send a password. We may verify ownership before releasing account-linked data.

Yes, you can request a correction through the support path connected with your account. Tell us which field is inaccurate and provide the replacement detail. We may confirm phone verification or account ownership first, then assess the request under the Privacy Policy and local requirements.

Retention depends on why a record exists. Account, payment-reference, security and support records may remain while needed for account operation, dispute handling, protection against misuse or legal duties. The Privacy Policy describes this approach, and you can ask support about a specific record.

Where local law permits, you can use the cookie control displayed on the site to change optional preferences. Necessary cookies may still support sign-in and account pages. Removing optional cookies can clear remembered settings, so your next mobile or desktop session may ask again.