Reference

Privacy Policy For Your biru 138 Account

Our Privacy Policy explains how we handle the account details, phone verification, device signals and payment records connected with biru 138.

Clear data purposesWallet record clarityPolicy contact pathMobile access context
Explore Our Lobby Read FAQ
biru 138 Privacy Policy For Your biru 138 Account
CONTACT YOUR WAY

Where To Ask About Privacy Policy

A clear contact route matters when a phone number, wallet reference or device record needs attention.

Account support path Use the support contact shown inside your logged-in account for a Privacy Policy question, correction request or access request. Include your registered phone number and a short description, but never send your password, one-time code or complete wallet credentials in the message.
Payment record help If a DANA, OVO, GoPay or QRIS entry looks incorrect, share the transaction date, visible reference and wallet name through the account support route. We can compare the record with the account activity without requesting your private wallet PIN or unrelated payment history.
Login privacy request When phone verification or a recognised-device check blocks access to your privacy settings, contact us from the account path available after login. Tell us which device and browser you used so we can separate an access issue from a request to change stored data.
SIX DATA CHECKS

Inside biru 138 Data Handling

We keep this policy connected to the steps you actually take, from phone verification before account access to wallet status checks after a payment reference is created.

Account details

We use your registered contact details to identify the account, send account-related messages and respond to a privacy request. Before changing a key detail, we may ask for an account step such as phone verification so another person cannot redirect access.

Device signals

Your browser, device type, approximate connection data and login time can help us recognise unusual access. A mobile session may create a new security record after a browser change; this signal supports account protection and is not treated as a profile of unrelated browsing.

Cookies and sessions

Cookies or similar storage help keep your signed-in path working, remember language or display choices and connect a session to the right account. You can clear browser storage, although doing so may require phone verification again before account access continues.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep references, amounts and status details needed to match an account transaction. We use these records for reconciliation and support, not to request your wallet PIN or banking password.

Retention timing

We retain account, security and transaction records for as long as needed for the stated purpose, dispute handling and applicable legal duties. When a record is no longer needed, our handling follows deletion, anonymisation or restricted-access procedures appropriate to that record.

Changes and access

You can ask what personal data is linked to your account, request a correction or question a use described in this Privacy Policy. Send the request through the logged-in support path with enough detail to locate your account; we may verify ownership before making a change.

Privacy Policy Questions For Indonesia

These answers cover the searches we hear most often about the biru 138 Privacy Policy, from phone verification and cookies to wallet references and correction requests. We keep each answer tied to a real account step, so you know what to prepare before contacting support. Access remains where local law permits, and requests are handled through the account contact route.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how records support account access and transaction matching, and how you can ask for access, correction or clarification.

Phone verification helps confirm that you control the account before access or a sensitive account change. It also helps us investigate an unusual login from a new mobile browser. We do not ask you to place a password or wallet PIN in a support message.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match an account transaction, resolve a receipt question and maintain required records.

Cookies or similar browser storage can keep your session active and remember selected settings. Clearing them may sign you out or trigger phone verification again. You can manage storage in your browser settings, while our policy explains why session data is used.

You can request access to data linked with your account or ask us to correct an inaccurate detail through the logged-in support path. Include your registered phone number and the specific record concerned. We may verify account ownership before releasing or changing data.

Retention depends on the purpose of the record, dispute handling needs and applicable legal duties. Account security and payment references may need to remain available after a transaction for reconciliation. When no longer needed, records may be deleted, anonymised or restricted.

The Privacy Policy is intended for account activity connected with our Indonesia service, but access and eligibility depend on local law. If you are in Jakarta or another location, check the applicable rules before opening an account and use our support path for a policy question.

Related Pages

biru 138 Indonesia era77slot liga356 FAQ Access guide