Reference

visitorbet Privacy Policy for Your Account

Our Privacy Policy explains what visitorbet collects when you open an account, use DANA or QRIS, and contact account support.

Account dataCookie choicesWallet recordsAccess requests
visitorbet visitorbet Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an open chat. Start from your logged-in account and use the support contact path, including the cashier-related route when your question concerns a DANA, OVO, GoPay, or QRIS reference. We may ask for account identifiers so we can locate the correct record while avoiding requests for wallet passwords or full payment credentials.

Team online

Account contact path

Open your logged-in account, choose the support contact route, and state whether your request concerns access, correction, deletion, cookies, or a payment reference.

Wallet record check

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, provide the transaction reference and account email rather than a wallet password.

Login access request

If phone verification blocks account access, tell us which device path you used and the account contact details so we can match the request securely.

DATA CARE

What We Do With Your Data

Privacy choices work best when each data use has a clear reason. We connect account, device, cookie, and payment records only when needed to operate access, check activity…

Account creation

When you open an account, we use your submitted contact details to create the profile, send account messages, and complete…

Device signals

We may record browser, device, login time, and session signals to detect unusual access and keep the correct account path…

Cookies

Session cookies keep you signed in during an account visit; preference cookies can remember choices.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us match a cashier event to your account without…

Retention

We keep account, security, and transaction records for as long as needed for service operation, disputes, and legal duties, then…

Change requests

Ask us to access, correct, or delete eligible data through the logged-in contact route.

Privacy Policy Questions for Indonesia

These answers address the Privacy Policy points you may check before opening an account or sending a wallet request. If your case needs account-level checking, use the logged-in contact path and share only the details needed to locate your record.

It covers account details, phone verification, device and login signals, cookies, payment references, retention, security handling, and requests to access, correct, or delete eligible data.

We use your phone detail for account setup and verification before account access. This helps connect requests to the correct account and supports checks when a login attempt appears unusual.

Yes. The policy covers references for DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We use those references to match account events without asking for wallet passwords.

Session cookies help maintain your login during a visit, while preference cookies can remember selected settings. Browser controls can limit them, but some account paths may not function correctly.

Use the logged-in account contact path and ask for access to your data. Include your account email and the request type; we may verify ownership before providing account-level records.

You can request correction or deletion of eligible data through the same contact route. We may retain security, transaction, or dispute records when needed for legal duties or account protection.

Yes. Account access and eligibility depends on local law. Where local law permits, we handle privacy requests through the account contact route and explain any limits that apply.