Reference

Privacy Policy for Your revo999 Account

Our Privacy Policy explains what account details we collect, why we use them, and how you can ask about or change your records before opening an account.

Account dataCookie choicesWallet recordsSecurity steps
revo999 Privacy Policy for Your revo999 Account
CONTACT PATHS

Privacy Questions Reach Our Support Route

A clear contact route helps you ask about the Privacy Policy without searching through the lobby. Use the support contact displayed in your revo999 account area and include the email or phone detail tied to your account, plus the subject of your request. We may ask for a verification step before discussing private records, and you can reach us whether your question concerns a mobile login, wallet reference or account closure.

Team online

Account privacy request

Send your request through the support contact shown after login, naming the account detail you want checked. We may confirm your phone or email first so private records are not disclosed to the wrong person.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include its date and visible transaction code. We use those details to locate the relevant record without asking you to send a wallet password or secret code.

Access and deletion help

For a correction, access request or account closure question, contact support from the account page where possible. We explain which records can be changed or removed and which must remain for a stated operational reason.

HANDLING DETAILS

Six Practical Privacy Controls We Use

Privacy is handled through account processes rather than a statement alone. We separate login protection from payment references, limit staff access by operational need, and use verification before discussing account-specific details.

Data collected

We collect details you provide for an account, such as contact information and verification data, alongside technical records like browser type, device signals and login time. Payment references help us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookie settings

Cookies and similar storage can keep a session active and remember basic choices on your phone or desktop browser. You can clear them through your browser settings, although doing so may sign you out and require the account step again.

Account security

We use account verification before handling a private request and may examine unusual login or device changes to protect the account. Never send a password or one-time code through support; we only need the details required to locate your request.

Retention period

We keep records only as long as needed for the purpose described, account administration, dispute handling or a legal obligation that applies where local law permits. When a record is no longer needed, our process moves it toward deletion or secure restriction.

Change requests

You can ask us to correct inaccurate contact or account details by using the support route shown after login. Include the old and new wording where practical, and we may verify ownership before applying a change to protect your account.

Who receives data

We share account details only with service parties that help operate the requested account process, such as payment record handling or security checks, and only for the relevant purpose. We do not ask you to disclose wallet credentials in a support message.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the records you are most likely to ask about before account access. We cover wallet references, mobile browsing, cookies, corrections and removal requests so you know what to prepare when contacting us. If your situation is not listed, use the support contact inside your account and mention the exact record or login step involved.

The Privacy Policy covers details you submit, verification results, login history, device signals, cookie storage and payment references. We use them to provide account access, protect the account, answer support requests and keep records accurate where local law permits.

You should never send a wallet password, PIN or one-time code to us. Our records may contain a payment reference, status or transaction date needed for matching, but support should not require secret wallet credentials to answer a privacy request.

Use the support contact shown in your account area and state whether you want access to a record or correction of a detail. Include the account email or phone, then complete any ownership check we request before private data is discussed.

Yes. The Privacy Policy covers cookies and similar browser storage used for session continuity and basic preferences on mobile or desktop. Clearing site data through your browser can sign you out, so you may need to complete the login step again.

We retain records for the purpose that created them, including account administration, dispute handling and applicable legal duties. The period can differ by record type and local requirement; when retention is no longer needed, we delete or restrict the record.

You can contact support from the account page to ask about closure. We explain the account step, verify the request, and tell you which information can be removed and which records may need to remain for an operational or legal reason.

Start with the support contact displayed after login and describe the data concern in clear English. Mention whether it involves a device, login, DANA, OVO, GoPay, QRIS or bank reference so we can route the request accurately.