Reference

robot88 Privacy Policy for Your Account

robot88 Privacy Policy explains what we collect when you open an account, use a mobile browser and check wallet status for DANA, OVO, GoPay or QRIS.

Clear collection purposesWallet reference detailsDevice access choicesAccount change requests
robot88 robot88 Privacy Policy for Your Account
POLICY HELP ROUTES

Privacy Help Beside Wallet Status

A clear support route matters when your Privacy Policy question concerns a login record, a wallet reference or a device session. Start from the support link inside your account and include the email or phone detail attached to your account, plus the relevant transaction reference if your question concerns DANA, QRIS or bank transfer data. We use those details to locate the right record without asking you to post private credentials in a public channel.

Team online

Account support path

Use the support link after login for a Privacy Policy request about your name, phone detail, email address or account record. We may ask you to confirm an account step before discussing personal data, so the request reaches the correct account.

Cashier data check

For DANA, OVO, GoPay, QRIS or bank transfer questions, send the payment reference shown in your cashier history. We can compare that reference with the account record and explain what data is retained for matching and status checks.

Device access request

If a phone or browser session appears in your account history, tell us the device path and approximate login time through support. We can explain the related record and help you request a correction without asking for your password.

SIX DATA CHECKS

Six Privacy Checks Behind Live Baccarat Salon

We handle Privacy Policy requests through practical checks rather than broad promises. Account records, wallet references, cookies and device sessions each serve a different purpose, and our team uses the smallest useful…

Account details

We may hold the name, phone detail, email address and verification status you provide during account opening. These fields help us connect a request to the right account and explain which details can be corrected through support.

Cookies and sessions

Cookies and session records can keep login state, language choice and device continuity working in a mobile browser. You can clear browser cookies, but doing so may require another account login before your saved session is recognised.

Wallet references

DANA, OVO, GoPay and QRIS activity can create references used to match cashier status. For bank transfer or virtual account checks, we may retain the bank route and reference needed to resolve a receipt question.

Account security

We use login history, verification steps and device signals to identify unusual access. If you move from a phone to desktop, a fresh confirmation may be requested before account details or payment records are discussed.

Retention controls

We keep records for the period needed for the stated account, payment or security purpose, then assess whether continued storage is needed. A retention question can be sent through the support link with the relevant account detail.

Change requests

You can ask us to correct inaccurate account data, explain a recorded payment reference or clarify how a device session was used. Include the account contact detail so we can verify the request before making a change.

Seven Privacy Policy Questions for robot88

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording practical: what we collect, why a device record appears, how wallet references are matched and how you can ask for a correction. If your situation is not covered, use the account support path and describe the exact record you want checked.

It covers account details, verification records, device sessions, cookies, payment references and support messages connected with your use of the site. It also explains why we use those records, how retention is assessed and how you can ask about access or correction.

Our payment matching process uses a wallet route, reference, status and timing details rather than your wallet password. If we need to check a DANA, OVO, GoPay or QRIS record, send the reference through account support and never send a private credential.

A device or browser record helps maintain a login session and identify unusual account access. It can show that a phone browser or desktop session reached the account at a certain time. We use that signal for account security and related support checks.

Open the support link inside your account and state which field is inaccurate, such as your phone detail, email address or verification status. Include the account contact detail used at opening so we can verify the request before changing the record.

For bank transfer or virtual account activity, we may keep the bank route, transfer reference, status and timing needed to match a cashier record. This can include BCA, BRI, Mandiri or BNI context when that detail is part of the payment trail.

Yes. Send an account data request through support and identify the account contact detail connected with it. We can explain the relevant categories, such as login, device, wallet reference or support records, subject to verification and rules that depend on local law.

The Privacy Policy is available on this page, while account access and eligibility depend on local law. If you are in Indonesia, use the account support path for a location-specific question and tell us whether it concerns login, payment data or a deletion request.