Reference

Open raffi 888 Privacy Policy details

Your account data, wallet references and device choices are covered in the raffi 888 Privacy Policy, so you can see what we collect before opening an account.

Account dataWallet recordsCookie choicesContact requests
raffi 888 Open raffi 888 Privacy Policy details
CONTACT PATHS

Contact us about Privacy Policy access

A clear contact path helps when you want to ask about your Privacy Policy rights or correct an account record.

Policy questions Use the account support link for questions about collection, cookies, retention or sharing.
Wallet records If a DANA, OVO, GoPay or QRIS reference looks incorrect, send the transaction reference…
Access changes For a correction, deletion request or copy of account data, identify the account and…
DATA CONTROLS

Switch through raffi 888 data controls

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

Collection points

We collect details when you open an account, complete phone verification, sign in, contact support or select a wallet route.

Cookie choices

Cookies can remember a session, language preference and selected device behaviour.

Account security

Login events, device signals and phone verification help us identify unusual access.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions, we handle reference and status details needed for account…

Retention approach

We retain account, security and support records only for the period needed for the stated account purpose, dispute handling and…

Request handling

Send a data access, correction or deletion request through the support link with your account identifier.

Open Privacy Policy answers for your account

These Privacy Policy answers cover the practical questions that arise before account access: which records we use, how wallet references are handled, what cookies do and how to request a change. If your question is not listed, use the support path attached to your account and describe the specific record you want us to check.

The Privacy Policy covers account creation, phone verification, login and device signals, cookies, support contacts and payment references. It also explains retention, security measures and the steps for requesting access, correction or deletion where local law permits.

Phone verification connects an account to the contact detail supplied during access and helps us protect sign-in requests. We use its status for account security and support matching, not as a reason to request your wallet PIN or banking password.

We may handle a wallet or QRIS reference, status, amount context and timing needed to match an account action with support records. Payment credentials remain with the relevant provider, and you should never place a PIN or banking password in a support message.

Use the support link connected to your account and ask for a data access copy. Include your account identifier and preferred contact detail. We may complete phone verification before releasing records, so the request reaches the correct account holder.

Yes, send the requested correction or deletion through the account support path and identify the record involved. We check the request, explain any retention requirement where local law permits, and confirm which action we can complete.

Retention depends on the type of record and its account purpose. Security, payment-reference and support records may need to remain available for dispute handling or legal duties. We remove or de-identify records when the relevant need ends, subject to local law.

Required cookies can keep your session and selected device preferences working between sign-in steps, while optional cookies may support preference choices. You can adjust browser settings on your phone, though blocking required cookies may return you to login or verification.