Reference

Privacy Policy for Your biru55 Account

biru55 Privacy Policy sets out what we collect when you open an account, use the mobile lobby, or check DANA and QRIS status.

Account dataWallet referencesCookie choicesAccess depends on local law
biru55 Privacy Policy for Your biru55 Account
CONTACT DATA CARE

Get Privacy Help Near Account Support

A clear contact path matters when a login check or wallet reference needs attention.

Account access Tell us which login step stopped you and include the account phone or email.
Wallet status For DANA, OVO, GoPay or QRIS questions, provide the payment reference and receipt details…
Privacy request Ask us to access, correct or clarify personal data by naming the request clearly.
DATA HANDLING MAP

How biru55 Handles Your Account Data

We keep this policy practical: you should be able to see why a data point is used and which account action it supports.

Account records

We use the details you submit during account opening, including contact information and verification results, to create access and respond…

Device signals

When you move from mobile login to the lobby, we may process browser, device and session signals.

Cookies

Cookies can remember a session choice, measure page function and support account security.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data.

Retention checks

We retain account and transaction records only while they support account administration, security, dispute handling or a legal need.

Change requests

You can contact us to ask for access, correction or clarification of personal data.

Privacy Policy Questions About biru55 Access

These Privacy Policy answers cover the account and payment questions we expect you to ask before opening access. They explain the data path behind mobile login, wallet references, cookies and support checks in plain language. If your situation is not covered, contact us from the account route and include only the details needed to locate your request. Eligibility and access depends on local law.

It covers personal data used for account opening, login checks, device sessions, cookies, payment references and support requests. It also explains retention, correction requests and contact steps for the Indonesia service route, where local law permits.

No wallet password or PIN is needed for our payment status checks. We may receive a transaction reference, status and account match result for DANA or QRIS, then use those details to reconcile the payment or answer support.

OVO and GoPay can create payment references linked to an account action. We use the reference, status and receipt details to check whether a transaction belongs to your account; wallet credentials remain with the relevant payment service.

Use the support contact shown inside your account area and state that you want a personal data access request. Include your account email or phone, complete the ownership check, and we will explain the records covered by your request.

Yes. Send a correction request through the account support route and identify the field that is wrong. We may ask you to complete a phone or email verification step before changing contact details or other account records.

Cookies can preserve a session choice and help the mobile path recognise your browser during login. You can adjust cookie controls in your browser, but removing required cookies may mean repeating the account access step.

Contact us through the support route displayed in your biru55 account area and select the privacy or account-data topic. Describe the request without sending wallet passwords, then provide a payment reference only when it is needed for a status check.