Reference

Privacy Policy for banker123 Accounts

Our Privacy Policy explains how we collect, use and protect the details you provide when opening a banker123 account or accessing the lobby.

Account dataWallet recordsCookie choicesContact requests
banker123 Privacy Policy for banker123 Accounts
HELP WITH REQUESTS

Get Clear Answers About Privacy

A privacy question should not interrupt your account path. We keep a direct route for requests about stored details, cookie choices, account access or a payment record linked to your profile. Include your registered phone number, the subject of your request and any relevant reference, but do not send a password or full wallet credentials. Our team can then check the correct account record and explain the next step. Where local law permits, we handle requests from the support route shown near login and the cashier status area.

Team online

Account access

If phone verification or sign-in does not match your account, contact us through the support route beside login. We use the registered account details and recent device session to confirm which record needs attention, without asking you to disclose your password.

Wallet records

For a DANA, OVO, GoPay or QRIS record, share the payment reference and approximate time shown in your wallet. We compare that reference with the cashier event and explain whether the status is pending, matched or needs another account check.

Privacy changes

To ask about a correction, deletion or copy of your personal details, state the exact change you want and the phone number attached to your account. We may request an account check before discussing private records or applying a change.

DATA CONTROL POINTS

Keep Your Privacy Choices Visible

Privacy controls work best when they are tied to real account actions. We separate identity details from routine device signals, limit access to staff who need a record for support or security…

Account details

We collect the phone and account details needed for access, verification and support. The account path helps us connect your request to the right record, while a payment reference such as QRIS is used to identify a transaction status rather than to replace your account identity.

Device signals

A browser, phone model, session time and sign-in pattern may be recorded to detect unusual access. This is especially useful when you move from a mobile lobby to a desktop session and need us to distinguish a normal return from a suspicious attempt.

Cookie controls

Necessary cookies keep your account session and policy choices available as you move between login and the lobby. Optional cookies can be reviewed through the cookie control in your browser or page settings, subject to the functions you choose to keep active.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in a support record when you ask about a cashier status. We use the minimum matching detail needed to trace the event and avoid requesting your wallet password or security code.

Retention checks

We keep personal and technical records while they support account security, a payment query, service operation or a legal need. When the purpose ends, we remove, aggregate or anonymise the record according to the retention step that applies to that case.

Your request route

You can ask what details we hold, request a correction, ask about deletion where local law permits, or question a cookie choice through support. Include a clear subject and registered phone number so we can verify the request before sharing account-specific details.

Find Answers Before Opening Your Account

These Privacy Policy answers focus on the questions you may have before creating access or checking a wallet record. We explain what is collected during phone verification, how device activity and cookies fit into account security, and how you can contact us about a stored detail. The same approach applies whether you browse from a phone in Semarang, use a desktop session or check a DANA and QRIS status.

The banker123 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references, retention and privacy requests. It also explains how we use these details for account access, security, support and payment-status checks where local law permits.

We collect the account details required to create access, including your registered phone number and verification result. We may also record browser, device and session details for security. Payment references from DANA, OVO, GoPay or QRIS are handled when they are needed to trace an account event.

Phone verification helps us connect an account request to the correct person and reduce confusion during sign-in or support. It also gives our team a way to check account ownership before discussing private details, changing records or investigating a wallet status.

Necessary cookies support your active session and remember policy choices as you move between login, cashier status and the lobby. Optional cookies can be managed through the available browser or page control. Disabling some cookies may affect the account functions that rely on them.

We may store a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference when it is needed to match a cashier event or answer a support request. We do not need your wallet password or security code for that check, and we use the relevant record only for its stated purpose.

Use the privacy support route and provide your registered phone number, the detail you believe is wrong and the correction you want. We verify the account before changing anything, then explain the result. Do not include your password, wallet PIN or full security credentials in the request.

You can send a deletion request through support, and we assess it against account security, payment records and any legal retention need. Where local law permits, records no longer needed for those purposes can be removed or anonymised after we complete the account check.