Reference

Open ricis99 Privacy Policy Clearly

Our Privacy Policy explains how ricis99 handles the account details you provide before access, including your phone verification and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet detailsCookie choicesAccess requests
ricis99 Open ricis99 Privacy Policy Clearly
GET POLICY HELP

Check Your Privacy Contact Path

When a privacy question affects your account, we keep the route close to the account and cashier areas so you do not need to search through unrelated pages.

Account access If you cannot reach your account or need to ask how your sign-in details are handled, use our account support path. Mention the phone verification step and the device path you used, but do not send your password or wallet PIN.
Wallet records For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, give us the date and payment rail. We can then separate a transaction reference from the personal account data connected to it.
Correction requests If a contact detail or account record needs correction, state the change clearly through support. We may ask for an account step or phone verification before changing data, so a request is matched to the right account.
DATA HANDLING

Explore ricis99 Privacy Controls

Privacy depends on clear handling at each account stage, from the first phone check to a later wallet-status question.

Account details

We use contact and verification details to create your account, confirm that an access request belongs to you and maintain sign-in security. We do not need your wallet PIN for a privacy request, and you should never include it in a message.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us trace an account event without treating the payment rail as your complete identity. Bank transfer and virtual account records are handled for matching, support and required record keeping.

Cookies

Cookies can keep your session connected while you move from account access to the lobby, including on a mobile browser. We use necessary session data for that path and may explain available cookie choices when your browser settings allow them.

Device security

Device, browser and sign-in signals help us identify unusual access, protect your account and investigate a stalled login. They are security indicators rather than a substitute for your phone verification, and they are retained only as long as the purpose requires.

Retention period

We retain account, transaction and support records for operational, security or legal reasons, then review them for removal or anonymisation. The exact period can depend on the record type, the account event and requirements that apply where you access ricis99.

Data changes

To request access, correction or an explanation of information linked to your account, contact support with the relevant account step. We verify the requester first, assess the request under local law and tell you what action we can take.

Browse Privacy Policy Answers

These Privacy Policy answers address the account questions we expect before access, especially around Indonesian wallets, mobile sessions and data requests. If your situation is not covered, use the support path and identify the account step involved. Do not send passwords, wallet PINs or unnecessary identity details when asking for help.

The ricis99 Privacy Policy covers account details, phone verification, wallet and transaction references, cookies, device signals, security handling, retention and requests to access or correct information. It also explains how we handle support questions connected with your account and payment status.

Phone verification helps us connect an access request with the correct account and reduce the chance of unauthorised entry. We may use its status during account support, but you should not send a verification code, password or wallet PIN in a privacy message.

Yes. The Privacy Policy explains how we handle references and status details returned by DANA, OVO, GoPay and QRIS. These records help match a wallet action to your account, while bank transfer and virtual account references may serve the same support purpose.

Necessary cookies can keep your mobile browser session connected while you move from login to the lobby. Device and browser signals may also support security checks. Your browser settings can affect cookie behaviour, and our support path can clarify a session issue.

You can contact us to ask what account information is connected with your request, where local law permits. We may verify your phone or account step first, then explain the available response. Include the relevant record, such as a QRIS reference, without extra sensitive details.

We keep information for the period needed for account operation, security, support or legal duties. Retention can differ between a phone verification record, a wallet reference and a support message. After the purpose ends, records may be removed or anonymised.

Yes, you can request a correction through the account support path. Tell us which field is wrong and which account step shows the issue. We may verify your access before making a change, and the request remains subject to local law.