Reference

raffi99 Privacy Policy for Your Account

The raffi99 Privacy Policy shows what we collect, why we use it and how you can ask about your account details before opening access.

Clear data purposesWallet status contextAccount access choicesCookie controls
Explore Our Lobby Read FAQ
raffi99 raffi99 Privacy Policy for Your Account
ASK ABOUT PRIVACY

Get Help With Your Policy Request

A clear support path matters when you want to understand or change personal data held in your account. Use the contact route on our site and include the phone number or account detail connected with your request, without sending a wallet password or private security code. We check the request before discussing records, then explain the next step. This route covers cookie questions, phone verification data, payment references and access concerns for your raffi99 account, where local law permits.

Team online

Account data request

Tell us which account detail you want to access or correct, such as your phone number or verification record. We may ask for a matching account step before releasing details, helping us avoid sending personal data to the wrong contact.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference shown in your account and the relevant wallet name through our support route. We use those details to locate the record without asking for your wallet password.

Cookie access help

Ask us how cookies affect sign-in, saved preferences or device access. We can explain the available browser controls and the effect of clearing them, while account protection checks still apply before we discuss private account activity.

DATA HANDLING

What Our Privacy Policy Keeps Clear

We keep this policy practical by tying each data use to an account action you can recognise.

Account creation

When you open an account, we use the details you submit to create your login record and complete the stated phone verification step. We keep the record connected to your account so later access questions can be checked against the right person.

Device signals

A mobile browser or desktop session can provide basic device and connection signals linked to sign-in activity. We use these signals to recognise unusual access patterns and investigate an account request, not to replace the identity details you provide.

Cookie choices

Cookies can remember a session, language preference or selected page setting. Your browser controls let you clear or restrict them, although doing so may require another login and can remove saved choices from the current device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data tied to an account request. We use the reference to match status and receipts, while wallet credentials remain handled by the relevant payment route.

Account protection

Phone verification and sign-in checks help us confirm that a request comes from the account holder. Never send a password or one-time security code in a support message; we use account matching steps instead.

Retention and changes

Some records stay available while an account, payment question or legal obligation requires them. You can ask what remains, why it remains and whether a correction or deletion request is available where local law permits.

Privacy Policy Answers for raffi99

These Privacy Policy answers address the account questions you are most likely to have before opening access or contacting us. We focus on the records created by sign-in, phone verification, cookies and Indonesian wallet references, rather than describing unrelated account features. If your question involves a specific record, include the account detail and payment reference you can see, and we will direct the request through the appropriate policy path where local law permits.

It covers account details, phone verification, device and sign-in signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains your options to ask about, correct or request removal of personal data.

We use phone verification to create and protect your account, confirm that an access request belongs to you and reduce mistaken disclosure through support. The verification result can remain linked to the account record while it is needed for account protection or a related request.

Yes. The policy covers basic device and connection signals created when you sign in from a mobile browser, as well as equivalent records from a desktop browser. We use them to assess unusual access and handle account questions, not as a substitute for your submitted details.

We may retain the payment reference, wallet name, request status and receipt details needed to match an account action or answer a status question. We do not ask you to send a DANA or QRIS password. Requests still pass through account checks before disclosure.

You can send a correction request through our site contact route and identify the account detail that needs changing. We may ask for a matching phone or account step, then confirm whether the change is available under applicable rules and explain any record that must remain.

The period depends on the type of record and the reason it is needed. Account protection, payment matching, unresolved support questions or a legal obligation may require continued retention. Ask us which records apply to you and why they remain where local law permits.

Use the contact route shown on our site and state that your request concerns the Privacy Policy. Include your account identifier or the visible payment reference, but not a password or security code. We will explain the identity check and next step for your request.

Related Pages

raffi99 Indonesia Live Blackjack Salon About Us Volleyball Match Bet Live Dragon Tiger Diamond