Reference

Privacy Policy for bucin4d accounts

bucin4d Privacy Policy explains what we collect when you open an account, browse Lightning Roulette or Starlight Princess, and use DANA or QRIS.

Account dataWallet recordsCookie choicesRequest access
bucin4d Privacy Policy for bucin4d accounts
REQUEST HELP

Contact routes for data requests

A clear support path helps when your account record or wallet reference needs attention.

Account support channel After login, send a Privacy Policy request through the account support path.
Wallet receipt check For DANA, OVO, GoPay or QRIS records, attach the transaction reference rather than private…
Account access issue If phone verification blocks your request, tell support that the issue concerns data access.
SIX DATA CHECKS

Six safeguards around your account data

We handle this policy area through defined account steps rather than broad promises. Sign-in, phone verification, wallet references and device signals each serve a different purpose, and we…

Account creation

We collect the details needed to create and verify your account, such as your phone number.

Device signals

Your browser and device may create technical signals during login.

Cookies

Cookies can keep a session working and remember practical choices.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us match a status to your…

Retention

We retain account, security and transaction records only for the period needed for the stated purpose, account support and legal…

Change requests

You may ask about a correction, copy or eligible removal through support after login.

Privacy Policy questions Indonesian account holders ask

These answers address the searches we hear most often about the bucin4d Privacy Policy. They cover account creation, wallet references, cookies, device activity and requests to see or change data. If your question concerns a specific receipt or verification step, use the support path after login and avoid sending secret credentials.

It covers account details, phone verification, device signals, cookies, wallet references, support requests, security records and retention. It also explains how to request access, correction or eligible removal where local law permits.

Yes. When you use DANA, OVO, GoPay or QRIS, we may handle payment references and status details needed to match activity with your account. We do not need your wallet password.

Phone verification helps confirm account ownership before access or a data request is processed. If verification stalls, contact support after login and describe the issue without sending your password.

You can send a copy request through the account support channel after login. Include your account phone number and request wording; we may verify ownership before releasing eligible records.

Cookies help maintain a sign-in session and remember practical browser choices. You can change cookie settings in your browser, but some account and policy-page functions may then work differently.

We retain transaction, account and security records for the period needed for their stated purpose, support checks and applicable legal duties. A retention question can be sent through support.

Yes, where local law permits. Send a correction request after login with the affected field and supporting detail. We verify ownership first, then assess the requested change against our records.