Reference

Privacy Policy for bordir bet Accounts

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

Account dataWallet recordsDevice accessPolicy requests
bordir bet Privacy Policy for bordir bet Accounts
CONTACT YOUR WAY

Privacy Help When Account Details Stall

A clear contact route matters when a phone check, wallet reference or data request needs attention.

Account desk Use the account support route for questions about phone verification, sign-in records or the personal details attached to your bordir bet account. We check the account path before discussing any private record and can explain which information is required for a correction request.
Wallet check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through the cashier support path rather than sharing a wallet PIN. We compare the payment record with the account status and tell you what can be corrected or retained.
Policy request For a copy, correction or deletion question, contact us through the policy support channel listed on the site. Include your verified account phone and request type; we use those details to locate the right record without asking you to disclose unnecessary wallet or device data.
DATA HANDLING

What We Keep Behind Your Login

We separate information used to operate your account from information used to understand technical problems.

Account security

Phone verification is part of the access path because it helps us connect a sign-in request with the correct account. We may record verification status, sign-in time and device signals to investigate unusual access. Never send a password, PIN or one-time code to support.

Payment records

A payment reference, amount, method and status may remain in our records so we can reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. The record supports receipt checks and account questions; it does not require us to store your wallet password.

Cookies

Cookies can keep your session connected while you move from account access to the lobby on a phone or desktop browser. They may also help us diagnose repeated sign-in failures. Browser controls let you clear or block cookies, but a cleared session can ask you to verify again.

Device signals

We may use browser type, operating system, connection details and security signals to protect account access and troubleshoot pages such as Live Blackjack Grand. These signals are handled for operational and security purposes, not as a substitute for your account identity or a request for private wallet credentials.

Retention steps

We keep personal and transaction data only while it supports account operation, dispute handling, security checks or a legal requirement. When a retention reason ends, records may be deleted, anonymised or placed beyond routine access. A deletion request may have limits where a payment or legal record must remain.

Your request

You can ask what account data we hold, request a correction, ask about processing or seek deletion of eligible information. Send the request through policy support with your verified phone and a clear description. We may confirm ownership first, then explain the result and any local-law restriction.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and access questions we hear most often from Indonesian customers. We explain what happens during phone verification, why payment references appear in account records, how browser cookies affect a mobile session and where to send a request. If your situation involves a specific DANA, OVO, GoPay, QRIS or bank transfer reference, include only the details needed for us to locate it. For eligibility or access, the outcome depends on local law.

The Privacy Policy covers information connected with your account, phone verification, sign-ins, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask about access, correction or deletion where local law permits.

We use your phone number to create and verify the account access path, help distinguish your request from another account and respond to account questions. Verification status can be recorded for security. We do not need your wallet PIN, password or one-time code in a support message.

Yes. The Privacy Policy covers payment references and status information linked with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use these details to match receipts, investigate a pending status and answer account questions without storing wallet passwords.

We may record browser type, operating system, connection details, sign-in time and security signals from the device used to access the account. This helps us investigate unusual access or a failed mobile page. We use these signals for service operation and security, not to request private wallet credentials.

Send a policy request through the support route shown on the site and include your verified account phone, the request type and a short description. We may confirm account ownership before responding. We then explain the available record, correction step or any restriction required by local law.

You can ask us to delete eligible account data through policy support. Some payment, security or dispute records may need to remain for a defined operational or legal reason. We will identify the relevant restriction and remove, anonymise or limit routine access to other records when appropriate.

Cookies can keep a browser session active and help us diagnose sign-in problems on a phone or desktop. You can clear or block them in your browser settings, but this may sign you out or require phone verification again. Cookie use and any available controls are described in this Privacy Policy.