Reference

biru777 Privacy Policy For Your Account

Our biru777 Privacy Policy shows what we collect when you open an account, sign in from a mobile browser, or select DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record clarityAccount access controlsRequest paths
biru777 biru777 Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Get Policy Help Beside Account Access

A clear contact route helps when a Privacy Policy question is separate from a stalled login or wallet status. Start from the support path beside the account area and include the phone number linked to your account, the request type and any relevant receipt reference. We use those details to locate the correct record without asking you to resend unrelated data.

Team online

Account privacy request

Ask about the personal records connected to your account, including phone verification or device signals. We may request an account step to confirm that the request comes from you.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and date. We use the smallest useful set of details to check status.

Access correction path

If your name, phone detail or account record needs correction, send the precise field and reason through support. We assess the request under local requirements before changing stored data.

DATA HANDLING PRACTICE

See How We Handle Your Records

We keep this policy practical by linking each data category to an account action you recognise. Phone verification supports account ownership, payment references help reconcile wallet status, and device signals help identify…

Account data

When you open an account, we store the details needed to create and maintain it. Phone verification can be used to confirm ownership before account access and during a sensitive request.

Payment references

A DANA, OVO, GoPay or QRIS selection can create a transaction reference and status record. Bank transfer and virtual account checks use matching reference details rather than unrelated account content.

Cookies and storage

Cookies or browser storage may remember session choices and help us detect loading errors. You can manage browser storage through your device settings, although some account functions may then need another sign-in.

Session security

We use login events, phone checks and device signals to protect account sessions. If a sign-in looks unusual, we may ask you to repeat an account verification step before access continues.

Retention periods

We retain records only while they support account operation, payment reconciliation, security checks or a legal duty. When a record is no longer needed for those purposes, our processes address its removal.

Your policy request

You can ask about access, correction, deletion or processing through the support path. Tell us which record you mean, and we may verify your account before responding where local law permits.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the searches we hear around account creation, mobile access and local wallet records. If your question concerns a specific transaction or phone verification event, include that reference through the support path so we can address the correct account.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, payment references and support requests connected with your biru777 account, subject to applicable local requirements.

Yes. The Privacy Policy covers references and status details created when you choose DANA, OVO, GoPay or QRIS. Bank transfer and virtual account references are handled for the same account and payment checks.

Phone verification helps us confirm account ownership before access and during sensitive privacy requests. It also helps separate your account record from another person’s request when local law permits the check.

We may record browser, device and session signals needed for sign-in continuity, page loading and security checks. Cookies can retain session choices, and you can manage them through your mobile browser settings.

You can contact support and specify the account records you want to access. We may verify your phone or account step first, then assess the request under applicable law and available retention duties.

Use the privacy contact path and name the exact field that needs correction, such as a phone detail or account identifier. We check ownership and update eligible records where local law permits.

Records remain while needed for account operation, payment reconciliation, security, support handling or a legal duty. After those purposes end, our retention process addresses deletion or removal according to applicable requirements.