Reference

byd108 Privacy Policy For Your Indonesia Account

Our Privacy Policy explains how we handle the details you provide when opening a byd108 account, checking DANA or QRIS status, and moving through the lobby from a…

Clear data purposesWallet record contextAccount request pathCookie choices
byd108 byd108 Privacy Policy For Your Indonesia Account
REQUEST SUPPORT

Where To Ask About Your Policy Data

A direct request is the practical way to ask what account data we hold, why a wallet reference appears, or how to correct a phone detail. Use the support path shown inside your account, especially the contact route beside the cashier area, and include the email or phone linked to your profile. We may ask for account checks before discussing private records. If you are in Denpasar or elsewhere in Indonesia, the same policy request path applies, and access remains where local law permits.

Team online

Account request

Send a privacy question through the support contact displayed after login. Include your registered phone detail and the specific record, such as a QRIS status entry, that you want us to check.

Wallet query

For DANA, OVO, or GoPay records, tell us the transaction date and wallet route without sending a password or full security code. We use those details to locate the relevant account event.

Access concern

If a login alert or device session looks unfamiliar, contact us through the account support route and change your password. We can review the related security event after confirming your account details.

DATA CONTROL

What We Do With Account Records

Privacy work is tied to ordinary account actions rather than a separate profile outside byd108.

Collection purpose

When you open an account, we may collect your contact detail, phone verification result, login events, device signals, and selected service activity. These records help us connect one account with the correct access request.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account event can leave a reference, amount status, timestamp, and account link. We use this narrow set to reconcile the transaction and handle support.

Cookie handling

Session cookies can keep your sign-in connected while you move from the account page to Live Dealer Lobby. Browser settings let you remove or restrict cookies, although some account functions may then require another sign-in.

Security controls

We use phone verification, login checks, session signals, and account review steps to reduce unauthorised access. Never share your password or one-time security code through a support message.

Retention timing

We retain account and payment references only for the period needed for service operation, security checks, dispute handling, or legal duties. After that need ends, records may be deleted, aggregated, or anonymised.

Change requests

You can ask us to correct a contact detail, explain a data use, provide an applicable copy, or consider deletion where permitted. We verify the request against your account before making a change.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear around sign-in, wallets, cookies, and account control. Each answer stays focused on how we handle your records, what you can request, and which account step helps us respond safely. Where a request affects access or eligibility, the outcome depends on local law and the details needed to confirm that the account belongs to you.

It covers account details, phone verification, login and device events, cookie use, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We may collect contact details, verification results, session records, device and browser signals, support requests, and transaction references. We use them for access, security, reconciliation, and policy requests.

Use the support contact shown inside your account and identify the detail needing correction, such as a phone number. We verify your account before changing private records.

We may pass necessary transaction references to the relevant payment route or service provider for processing, status checks, and reconciliation. Each provider may handle its own records under separate terms.

Cookies can maintain a sign-in session, remember limited preferences, and help detect unusual access while you move between account pages and the lobby. Browser controls can restrict or remove them.

We keep records for the time needed for account operation, security, disputes, or legal duties. When that need ends, we may delete, anonymise, or aggregate the relevant record.

You can submit a deletion request through the account support route. We assess it against active service, security, dispute, and legal needs, with the result depending on local law.