Reference

Privacy Policy for biru138slot Accounts

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

Account dataWallet referencesDevice accessYour choices
biru138slot Privacy Policy for biru138slot Accounts
CONTACT DATA CARE

How To Ask About Your Privacy Policy

A clear contact route helps you control the details attached to your account. When login or wallet status stalls, use the support path shown beside the account and cashier areas, then describe…

Account access If you cannot reach your account, contact us through the available support route and include the phone number linked to your account. We use that step to locate the correct record, check recent device activity and avoid disclosing account details to an unverified person.
Wallet status For a DANA, OVO, GoPay or QRIS reference, share the transaction date, amount shown in your account and the wallet status displayed to you. Do not send a wallet PIN. We use the receipt reference to investigate the record without requesting secret credentials.
Privacy request To request access, correction or deletion of eligible personal data, state the request clearly and provide the account phone number. We may verify ownership before responding, explain any legal or security reason for retention and confirm the result through the account contact path.
SECURITY PRACTICES

How We Handle Your Account Data

We treat privacy as an operating step rather than a page you read once. Phone verification helps us connect requests to the correct account, while device and session records help us investigate…

Account details

We may store the contact details used during account opening, including your phone number and verification result. These records support login assistance and ownership checks. Please keep your phone number current so a privacy request reaches the account you intend to manage.

Device records

When you use a mobile browser or desktop browser, we may record device type, browser signals, session times and network clues. These details help us recognise unusual access and troubleshoot a page that does not load correctly without reading private files on your device.

Cookies

Cookies and similar browser storage can remember a session preference, help maintain account access and show whether a page request completed. You can manage browser storage through your device settings, although removing it may require you to verify the account again.

Payment references

A wallet or bank record may include a reference, amount, timestamp and status connected with DANA, QRIS, bank transfer or a virtual account. We use those fields to match the account step. We do not request your DANA, OVO or GoPay PIN.

Retention period

We keep account, security and transaction records for the period needed to provide support, investigate disputes, protect account access or meet applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account identifiers where practical.

Change request

You may ask us to correct an inaccurate phone detail, clarify a device record or explain a payment reference. Send the request through the account support path. We verify ownership first, then tell you whether the change can be made and what evidence is required.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before registration: what we collect, why a phone check is needed, how payment references appear and how you can contact us. The same approach applies when you browse on mobile, return from a desktop browser or ask about a record connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Access depends on local law.

The biru138slot Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can request access or correction.

Phone verification helps us confirm that an account request comes from the account holder. It supports login recovery, privacy requests and checks against unfamiliar access. We use the verification result for account administration and security, and we do not ask you to share a phone security code in a public message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, such as a status, timestamp, amount and receipt reference. We use those details to reconcile an account step. Wallet PINs and secret credentials should never be sent to our support team.

We may receive browser type, device category, session time, approximate network details and security signals from a mobile or desktop browser. This helps us identify unusual access and diagnose failed sessions. We do not need private files on your device to perform these account-security checks.

Use the account support path and state whether you want access, correction or deletion of eligible data. Include the phone number linked to your account, but never include a wallet PIN or password. We verify ownership, assess the request under applicable rules and explain the outcome.

We retain records for the period needed for account support, security investigations, transaction disputes or applicable legal duties. The period can differ by record type. When continued storage is not needed, we remove the record or separate it from direct account identifiers where practical.

You can ask through the support route connected with your account and cashier area. Describe the Privacy Policy question, provide your account phone number for verification and avoid secret credentials. We can clarify stored data, payment references, cookies, retention or a request to update your details.