Reference

revo999 Privacy Policy for Your Account

Our revo999 Privacy Policy explains what we collect when you open an account, complete phone verification and use the lobby from a mobile device.

Clear data purposeWallet record detailsAccount request path
revo999 revo999 Privacy Policy for Your Account
DATA HELP ROUTE

Where To Ask About Your Data

A direct account support route helps when a Privacy Policy question concerns login history, phone verification or a wallet status check. We ask you to contact us from the account connected with the request, because that lets us compare your details safely without exposing another account. Include the payment rail, device path or date involved; for example, QRIS on mobile or a bank transfer reference.

Team online

Account access

Use the account support path when your phone verification record, sign-in detail or account contact data needs clarification. We may ask for a matching account step before discussing private details.

Wallet status

For DANA, OVO, GoPay or QRIS records, send the payment reference and status shown in your account. We use those details to locate the correct transaction without requesting your wallet password.

Data request

Ask us to correct, explain or remove eligible account data through the same support route. State the exact request and the phone or email attached to your account so we can verify it.

HANDLING DETAILS

Six Ways We Handle Account Data

Our Privacy Policy is applied through ordinary account steps rather than hidden settings. We separate contact details from payment references, limit access to staff who need a record for support or account…

Account details

We use your submitted contact details to create and maintain the account, complete phone verification and respond to account requests. Keep them accurate so a data correction can be matched to you.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace status without storing your wallet password. Transaction context may remain while a support or legal need exists.

Cookies

Cookies and similar session tools can remember sign-in state, device preferences and security events. Clearing them may require you to complete phone verification again when returning to the lobby.

Account security

We compare sign-in and device events with account activity to identify unusual access. Never share your phone verification code; our support path does not need your wallet password.

Retention

We keep account, payment and support records for the period needed for service operations, account protection or legal duties. When that purpose ends, records are deleted or changed so they no longer identify you.

Policy changes

If this Privacy Policy changes, we will present the updated wording on the policy page. You can ask what changed, request eligible corrections or raise a concern through your account support path.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers cover the account and wallet questions we expect before registration. They explain what to prepare, how to request access or changes, and which payment or device details help us locate the right record. Access remains where local law permits.

It covers account details, phone verification, sign-in events, cookies, device activity, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps connect an account request to the correct contact detail and supports account protection. We use the verification event for access checks, support matching and security review where local law permits.

Yes. We may record basic browser, device and session events when you sign in on mobile, open the lobby or return on a computer. These details help identify access issues and unusual activity.

We use DANA and QRIS references to match a payment status with your account, investigate a stalled cashier step and answer a receipt question. The reference does not give us your wallet password.

Use the account support path and state which detail is wrong, such as a phone number or contact address. We may request account verification before changing the record linked to your access.

Yes. Send a data request through the support path connected with your account, include the relevant phone or email, and specify whether you want account, cookie, payment or support records explained.

We retain records while they serve an account, security, support or legal purpose. After that purpose ends, we delete or anonymise the relevant data under our retention process, subject to local law.