Reference

Privacy Policy For Your raffiwd Account

Our Privacy Policy explains how we handle the account details behind Baccarat, Ganesha Fortune and Aviator access, including phone verification and wallet records for DANA, OVO, GoPay and…

Account detailsWallet recordsCookie choicesSecurity requests
raffiwd Privacy Policy For Your raffiwd Account
POLICY HELP ROUTES

Get Help With A Privacy Request

A clear request path helps us act on your Privacy Policy questions without exposing account details to the wrong person. Start from the support contact available inside your raffiwd account and include the phone number linked to access, the subject of your request and any relevant payment reference. We may ask for an account step or verification detail before discussing personal data. If you cannot sign in, use the account-access contact route shown on the site and describe the problem without sending a full password or wallet PIN.

Team online

Access request

Ask us to explain the personal data connected with your account. Include your linked phone number and the account step you completed so we can check identity before sharing any private record.

Correction request

If your name, phone detail or wallet status is wrong, tell us which entry needs attention. We compare the request with the account record and may ask for phone verification before changing it.

Payment query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, send the payment reference rather than a wallet PIN. We use that reference to trace status while limiting unnecessary data exposure.

DATA HANDLING DETAIL

What We Protect And Retain

Privacy Policy choices work best when the handling steps are visible. We separate account access data from payment references where the process allows, use device signals to spot unusual sign-in behaviour and…

Account records

We use your name, linked phone number and verification result to connect the right person with the right account. These details support sign-in checks and help us respond to a Privacy Policy access request.

Wallet references

DANA, OVO, GoPay and QRIS status details can be recorded with a payment reference. We use those records to match a cashier event, resolve a mismatch and avoid asking you to resend sensitive wallet credentials.

Device signals

Your browser or phone may provide session and device signals when you sign in. We use them to identify unusual access patterns, protect account sessions and check why a login path stalled.

Cookie controls

Essential cookies keep account sessions and policy choices working. Browser settings can limit optional cookies, although changing them may affect saved preferences or require you to repeat an account step.

Retention periods

We keep each record only for the period needed for its purpose, account security, payment reconciliation or a legal duty. When retention ends, we remove, anonymise or securely restrict the record.

Policy changes

If this Privacy Policy changes in a material way, we place the updated wording on this page and may show an account notice. Check the page before using the lobby or updating wallet details.

Privacy Policy Questions About raffiwd

These Privacy Policy answers cover the requests we expect before account access: what we collect, why payment references appear, how cookies work and how you can reach us. We keep the answers tied to the actual account flow, from phone verification through a DANA or QRIS status check. If your situation is different, send the question through the support contact shown inside your account, where local law permits.

It covers data collected during account opening, phone verification, sign-in, lobby access and support. It also explains how we handle device signals, cookies, DANA, OVO, GoPay, QRIS, bank transfer and virtual account references connected with your account.

We use your phone number to create the account link, complete the required verification step and help protect sign-in access. It also lets us match a support request to the correct account before discussing private records.

Yes. The policy covers payment references and wallet status connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use them for matching, status checks, security and dispute handling.

You can ask what personal data is connected with your account through the support contact shown in your account area. Include your linked phone number and request type. We may verify identity before providing records, where local law permits.

Send a correction request through the account support path and identify the entry that is inaccurate, such as a phone detail or account name. We compare the request with your verification record before applying a change.

Retention depends on the type of record and its purpose. We keep account, security and payment references for the period needed to protect access, reconcile a status, handle a dispute or meet a legal duty.

Use the account-access contact route displayed on the site and describe your request without sending a password, wallet PIN or full payment credentials. We can ask for safer verification details before discussing your Privacy Policy request.