Reference

buku 4d Privacy Policy For Clear Account Control

buku 4d Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Live Roulette Grand or use DANA and QRIS at…

Account dataWallet recordsDevice choicesYour requests
Explore Our Lobby Read FAQ
buku 4d buku 4d Privacy Policy For Clear Account Control
REQUEST HELP

Get Privacy Support Near Your Account Path

A clear support route helps when you want to ask about the Privacy Policy rather than troubleshoot a game. Sign in, open the account help area near the cashier path, and describe the request you want us to handle. Include the account step involved, such as phone verification, a QRIS reference or a device sign-in, but do not send a password or full wallet credentials. We use the details you provide to locate the relevant record and respond through the support route available inside your account.

Team online

Account privacy request

Use the support link inside your account to ask what personal data we hold, why it is used, or which record relates to your phone verification. We may ask you to confirm account ownership before discussing private details.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the visible transaction reference and approximate date. We can compare that detail with the account record without asking you to reveal a wallet password.

Device access concern

For an unfamiliar phone sign-in or a browser session you do not recognise, contact us through the signed-in account path as soon as possible. We can review the access record and explain the next account-security step.

DATA HANDLING

What We Do With Your Privacy Choices

We keep this policy practical by linking each data category to an account action you can recognise. Phone verification supports account access, device signals help us assess unusual sign-ins, and transaction references…

Account details

We collect the details you enter during account creation and the phone-verification result used to connect you with that account. Keep your contact details current so a privacy request can be matched without exposing another person’s record.

Mobile and browser data

When you move from login to the lobby on a phone, we may record device, browser, language and session signals. These details help identify unusual access and keep the correct account session active without reading unrelated files on your device.

Cookies and storage

Our pages may use cookies or local storage to remember a session choice, load the privacy page correctly and understand basic page performance. You can manage browser storage through your device settings, although some account functions may then need another sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions can create references, amounts and status records. We use these details to match an account action with a cashier result, not to request your wallet password or private banking login.

Retention and deletion

We retain account, access and transaction records only as long as needed for account administration, security, dispute handling or legal duties. A deletion request may be limited when a record must remain for a transaction or legal reason.

Change requests

You can ask us to correct a phone number, clarify a data use, provide a copy of relevant account data or explain a retention decision. Send the request through the signed-in support path, and we may verify ownership before acting.

Privacy Policy Answers For buku 4d Accounts

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access. We keep the wording tied to real actions, such as phone verification, mobile sign-in, QRIS records and requests made from your account. If your question concerns eligibility, remember that access depends on local law and may require an account or location check before we can respond.

The buku 4d Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and transaction references. It explains why we use each category, how long records may remain, and how you can ask for access, correction or deletion.

We collect the details you submit during the account step, together with the phone-verification result needed to connect you to that account. We may also record sign-in time, browser or device signals, and support messages related to your account activity.

Yes. The Privacy Policy covers references and status details created when you use DANA, OVO, GoPay or QRIS. We use them to match a wallet action with your account and cashier record. We do not need your wallet password for that matching process.

Sign in and use the support path inside your account to request access to relevant data or correction of an account detail. Tell us whether the request concerns phone verification, device access or a payment reference. We may confirm account ownership first.

On a mobile browser, cookies or local storage may keep a session choice, help the Privacy Policy page load correctly and provide basic page-performance signals. You can manage storage in your phone or browser settings, but clearing it may require another sign-in.

You can ask about deletion through the account support route. We assess the request against account administration, security, dispute handling and legal duties. A transaction or access record may need to remain when a legal or security reason requires continued retention.

Access depends on local law. We may use account or location checks before allowing access, and the Privacy Policy explains how related data is handled. If a check blocks your request, contact support from the available account path for clarification.

Related Pages

buku 4d Indonesia Basketball IBL Bet FAQ About Us Account information