Reference

belo4d Privacy Policy for Indonesia

Our Privacy Policy explains what data we collect when you open a belo4d account, sign in from a phone or desktop, use DANA or QRIS, and contact account…

Account dataDevice choicesWallet recordsCookie controls
Explore Our Lobby Read FAQ
belo4d belo4d Privacy Policy for Indonesia
CONTACT THE TEAM

Privacy Policy Help For Account Questions

A clear support path helps when you want to understand a data record rather than simply change an account setting. Contact us through the support route shown inside your belo4d account and identify the email or phone detail attached to the request. We may ask for an account step or confirmation before discussing private records. Do not send a wallet password, one-time code, or full bank credential. We can help with account data, device sessions, cookies, payment references, and requests connected with the Privacy Policy.

Team online

Account data request

Ask us to locate the personal data linked with your account. Include your registered phone or email so we can match the request, then complete the confirmation step we provide before any private record is discussed.

Wallet record question

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks unfamiliar, send the transaction date and visible reference. We can check the record without asking you to reveal a password or one-time code.

Device and cookie help

Tell us whether the issue appeared on mobile or desktop and which browser session was affected. Our support route can explain cookie choices, sign-out steps, and the account confirmation needed for a security-related request.

DATA HANDLING DETAILS

Six Practical Privacy Policy Commitments

The practical details below show how we apply this Privacy Policy during ordinary account use. We separate account identity, device activity, cookie preferences, and wallet records so a request can be directed…

What we collect

We may collect your registration details, phone verification result, sign-in timestamps, device and browser signals, support messages, and cashier references. We use these details to provide account access, check security events, and answer a Privacy Policy request.

Why data is used

Account data supports sign-in and phone confirmation; device signals help identify unusual sessions; and payment references help reconcile DANA, QRIS, or bank transfer activity. We use each category for an operating, security, support, or legal purpose.

Cookies and sessions

Cookies can keep a session available, remember selected settings, and help us detect repeated sign-in failures. You can manage browser cookie controls, but removing required cookies may interrupt account access or require another phone confirmation.

Account protection

We protect account access through phone verification, session checks, and confirmation steps for sensitive requests. If you change devices, sign out of an old session and contact support if an unfamiliar device continues appearing in your account.

Retention approach

We keep records for as long as needed for account operation, security checks, dispute handling, and applicable legal duties. When a record is no longer needed for those purposes, we remove it or separate it from direct account identification.

Your request options

You can ask whether we hold your account data, request a correction, ask about a wallet reference, or raise a deletion question. Send the request through account support; we may verify ownership before acting on private data.

Privacy Policy Questions About belo4d

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. They explain the practical route for data requests, payment references, cookies, and access from Indonesia. If your situation is not covered, contact us through the account support path and include only the details needed to identify your request.

The belo4d Privacy Policy covers registration details, phone verification, sign-in activity, device signals, cookies, support messages, and cashier references. It explains why we use those records, how we protect them, how long they may remain, and how you can ask about your data.

Yes. The Privacy Policy applies when you sign in from a mobile browser or desktop. We may record device and browser signals for session security, while required cookies can keep the account path working. You can manage optional browser cookies through your device settings.

We receive payment references and status details needed to match a cashier request involving DANA or QRIS. We do not need your wallet password or one-time code. If a reference looks wrong, contact support with its date and visible transaction identifier.

You can ask for the account data connected with your registered phone or email. Use the support route inside your account and complete the ownership confirmation we provide. We will explain what can be supplied, subject to legal and security limits.

Send a correction request through account support and identify the detail that needs changing. We may ask you to complete phone verification before updating it. Payment references and security records may need a separate explanation because they support transaction or access checks.

You may submit a deletion question through the support path. We will assess which records can be removed and which must remain for security, dispute handling, account history, or legal duties. Access and eligibility depends on local law and the applicable request rules.

Use the support route shown after account sign-in and label the request as a Privacy Policy concern. Include your registered contact and a short description, but never send a password or one-time code. We can direct questions about cookies, devices, accounts, or wallets.

Related Pages

belo4d Indonesia About Us Pontianak Night Spins Access guide Live Roulette Elite