Reference

Privacy Policy For Your borneo33 Account

borneo33 Privacy Policy explains what we collect when you open an account, sign in, verify your phone, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesPolicy requests
Explore Our Lobby Read FAQ
borneo33 Privacy Policy For Your borneo33 Account
CONTACT YOUR WAY

Privacy Help Beside The Wallet Path

A clear contact route helps when a Privacy Policy question involves your account or a payment reference.

Account data request Ask us to explain the personal data connected with your borneo33 account, including the phone verification record and sign-in details. Include your registered contact so we can confirm ownership before discussing account data or making a change.
Wallet record query If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt code and date through our support path. We can check the payment status against the account record without requesting your wallet password or full security credentials.
Cookie assistance Tell us which browser and device you use if a privacy choice does not stay saved. We can help you check cookies, session storage and the login step on mobile or desktop while keeping the request focused on access behaviour.
DATA CONTROL POINTS

What We Do With Your Personal Data

We keep the Privacy Policy practical by tying data handling to identifiable account events. Your details help us maintain login security, match a phone verification step, reconcile wallet records and respond to…

Account security

We use sign-in details, phone verification results and device signals to identify unusual account access. If your device changes while you move from login to the lobby, we may use that event to protect the account rather than expose your stored profile.

Payment matching

A DANA, OVO, GoPay or QRIS receipt gives us a reference for matching a cashier event to your account. We use the reference and status for reconciliation, while your wallet password and private wallet credentials stay outside our requested account data.

Cookie choices

Cookies can keep a session active, remember a selected language or help us detect an unsafe sign-in pattern. You can manage browser permissions on your phone or computer; removing essential cookies may require another login before the account page opens.

Retention logic

We keep account, security and payment references only while they serve account administration, protection, dispute handling or a required operational purpose. When a record no longer serves those purposes, our handling process moves it toward deletion or de-identification.

Correction requests

You can ask us to correct inaccurate contact or account details by using the support route linked to your profile. Include the specific field and the correct value; we may request a simple ownership check before changing a sensitive account record.

Policy contact

For a Privacy Policy question, contact us from the account-linked route and describe whether it concerns collection, cookies, retention, access or deletion. We keep the request narrow, confirm which record you mean and reply with the next practical step.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account steps you are most likely to question before opening an account. We explain the connection between your profile, browser session and local payment references without turning a data request into a general platform conversation. Where a request depends on identity, we use the contact details already connected to your account. Access and eligibility depends on local law, including for customers in Indonesia.

It covers personal data used for account creation, phone verification, login security, cookie operation, payment matching and support requests. It also explains retention and how you can ask about, correct or remove eligible records connected with your borneo33 account.

These payment names appear because a wallet or QRIS action creates a reference and status that may need matching with your account. We use the minimum cashier detail needed to reconcile that event and do not ask for your wallet password.

Use the support contact path from the phone number or email linked to your account. State that your request concerns personal data, then name the record or account step. We may confirm ownership before discussing profile, verification, cookie or payment details.

Yes. Send a correction request through the account-linked support route and identify the field that is wrong, such as a phone number or profile detail. Provide the replacement value clearly; we may check ownership before applying a sensitive change.

On a mobile browser, cookies can maintain your login session, remember a preference and help protect the route into the lobby. Browser settings let you remove or restrict them. Essential cookie changes may sign you out and require phone verification again.

We retain records while they support account administration, security, payment reconciliation, dispute handling or another stated operational purpose. Retention is not indefinite by default; records move toward deletion or de-identification when they no longer serve those purposes.

Yes. Account access and eligibility depends on local law. Where local law permits, you can contact us about your personal data, cookies, retention or account changes. We will explain the available route and any ownership check needed for the request.

Related Pages

borneo33 Indonesia Access guide dewacsh Live Dealer Lobby ligadewa22