Reference

biru303 Privacy Policy Explained Clearly

biru303 Privacy Policy tells you what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
biru303 biru303 Privacy Policy Explained Clearly
CONTACT PATHS

Where Your Policy Questions Go

A clear contact route helps you ask about personal data without searching through the lobby.

Account support link Open the support link inside your account when you need a copy of stored account details, an explanation of a verification record or help identifying the right Privacy Policy request.
Wallet receipt query For DANA, OVO, GoPay or QRIS records, send the receipt reference and approximate date through the account support path. We can check the account match without requesting your wallet password.
Access assistance If a privacy request follows a sign-in problem on mobile, tell us the device path and account step reached. We use that context to separate access trouble from a data request.
SIX DATA CONTROLS

Six Controls Behind Account Privacy

We keep the Privacy Policy practical by connecting each promise to an account action you can recognise.

Collection at account opening

We collect the details needed to create and maintain your account, including contact data and the phone verification step. We do not ask you to provide unrelated personal details merely to browse the policy.

Payment reference matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be linked to your account transaction. We use that reference for status checks and reconciliation, not to view your private wallet balance.

Mobile device signals

When you sign in through a mobile browser, we may record device and browser signals, language settings and access time. These details help us recognise unusual account access without reading unrelated content on your device.

Cookie choices

Cookies can remember a session and support the settings you select. You can manage cookie permissions through your browser controls, although refusing some cookies may require another sign-in during account access.

Retention and deletion requests

We retain account and transaction records for the period needed for account operation, dispute handling and applicable legal duties. Ask through support if you want the retention basis for a specific record explained.

Correction and access

You can ask us to check inaccurate contact data, clarify a phone verification record or provide the personal data linked to your account. Include your account identifier so we can confirm the request safely.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or sending a wallet-related request. If your situation is not covered, use the signed-in support link and describe the exact account step, device path or payment reference involved.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect the account to the contact detail you supplied before account access. We may use its status to investigate access requests, correct records and identify unusual sign-in activity.

No. Our policy concerns payment status and transaction references linked to your account. We do not need your DANA, OVO, GoPay or QRIS wallet password to check a receipt or account match.

Use the support link shown after you sign in and state that you are making a data request. Add your account identifier and the record involved, such as phone verification or a QRIS reference.

Yes. Send a correction request through the account support path, identify the inaccurate field and explain the change needed. We may ask for an account check before changing contact or verification data.

Cookies may keep your session active and remember selected settings. Your browser controls let you change permissions. If some cookies are refused, you may need to sign in again on mobile.

Yes. Access and eligibility depends on local law, and the way we respond to a data request may differ where local law permits. The policy on this page sets out our current handling approach.