Reference

bank 303 Privacy Policy for Indonesia

The bank 303 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet data contextCookie choicesSupport requests
bank 303 bank 303 Privacy Policy for Indonesia
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps when you want to understand a record linked to your account or wallet activity. Send your request through the account support channel and include the phone number or account identifier connected with your sign-in, without sending a password or wallet PIN. We can explain the relevant Privacy Policy section, confirm which verification step is needed, and route a correction or access request for handling where local law permits.

Team online

Account data request

Ask which account details we hold and how they relate to phone verification, sign-in records or support messages. We will use the account identifier you provide to locate the correct record without asking for your password.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact support with the date and reference shown in your account. We can explain the record status while keeping wallet credentials and sensitive authentication details private.

Correction route

Tell us when your account details need correction or your contact route has changed. We may ask for phone verification before acting, so a requested change is connected to the right account and not an outside request.

DATA HANDLING

What We Do With Privacy Requests

We keep our Privacy Policy practical by connecting each data purpose to an account action: sign-in protection, phone verification, wallet status, support handling or legal duties.

Account details

We use your submitted account details to create the account record, complete phone verification and respond to requests about your access. We do not need your password in a support message, and we ask you to keep that credential private.

Device signals

Browser type, device details and connection signals can help us keep a sign-in session working and investigate unusual access. These signals support account protection; they are not a request for the contents of your personal device.

Cookie controls

Cookies can remember session choices and help pages load with the account state you selected. Your browser provides controls for clearing or limiting cookies, though changing them may affect sign-in continuity or policy display.

Wallet references

A payment reference may identify a DANA, OVO, GoPay, QRIS, bank transfer or virtual account request. We use that reference to match status and support checks, not to request your wallet PIN or banking password.

Retention steps

We retain account, verification and support records for the period needed to operate, secure and answer your account, or as required where local law permits. You may ask support how a particular record is handled.

Change requests

To request a copy, correction, restriction or deletion where available, contact support using your account identifier and describe the request. We may verify your phone before responding so another person cannot change your record.

Privacy Policy Questions You May Have

These Privacy Policy answers focus on the account steps you are most likely to ask about before opening or using bank 303 in Indonesia. They cover what we collect, why wallet references appear, how device data works, and how to request action. If your situation is different, contact support with the account identifier connected to your request.

It covers personal data connected with your account, phone verification, sign-in, device and cookie signals, support messages, and payment references. It also explains our purposes, retention approach, security handling and request process where local law permits.

DANA and QRIS can appear in account or transaction references when you use a supported wallet route. We use those references to match a request, check its status and answer support questions, while your wallet PIN remains private.

Our Privacy Policy does not ask you to send a wallet PIN, banking password or account password to support. Payment records may contain a method and reference, such as OVO, GoPay or bank transfer, for status handling.

Phone verification connects an access request with the account record you created. We may use the verification result to protect sign-in and handle a data request. If you ask for a change, we may repeat verification before acting.

Yes, contact the account support channel with your account identifier and state whether you want a copy or correction. We may confirm your phone before responding. The available action and timing depend on local law and the record involved.

Cookies can preserve a sign-in session and remember choices made in the browser. You can clear or limit them through your device settings. The policy explains the purpose of these signals, while browser changes may interrupt account access.

Send a retention question through account support and identify the record, such as a verification entry, wallet reference or support message. We will explain the applicable handling and whether a request can be made where local law permits.