Reference

rusa88 Privacy Policy for Your Account

Our Privacy Policy explains how rusa88 collects, uses and protects the details connected with your account, including phone verification, device access and wallet records.

Clear data purposesWallet record controlsAccount access requestsCookie choices
rusa88 rusa88 Privacy Policy for Your Account
HELP WITH PRIVACY

How To Reach Us About Your Data

A privacy request should start from the account support path so we can connect it to the correct profile without exposing details in an open message. Tell us whether you need a copy, correction, deletion request or explanation of a wallet record. When your question concerns a DANA, OVO, GoPay or QRIS reference, include only the receipt number and the account phone detail requested by support.

Team online

Account support path

Open support from your signed-in account and choose the privacy topic. This lets us match your request with the verified phone detail before discussing account records.

Wallet record query

For a payment reference, provide the relevant DANA, OVO, GoPay or QRIS receipt number. We use that narrow reference to check status without requesting your wallet password.

Access correction request

Ask us to correct a phone detail, device record or account entry through the same support route. We may ask for an account step to confirm that the request is yours.

SIX DATA PRACTICES

How We Handle Account Privacy

Privacy is managed through ordinary account operations rather than a separate download or device tool.

Account collection

When you open an account, we collect the contact and verification details needed to create that account. We do not turn a casual page visit into a full account record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are handled as transaction references. We use them to match a receipt or status with your account, not to request wallet passwords.

Device signals

A mobile browser can send device, connection and session signals that help us recognise unusual sign-in activity. These signals support account security and are handled under the Privacy Policy.

Cookie controls

Cookies can keep a signed-in session available and retain selected settings. Clear them in your browser privacy controls when you choose; a later sign-in may require phone verification again.

Retention decisions

We retain account, support and payment references only for operational, security or legal needs described by the policy. When a retention need ends, the relevant record can be removed or separated from active access.

Change requests

To request correction, access or removal, contact us through the signed-in support path. We may verify your phone detail first, then explain what can change where local law permits.

Privacy Policy Answers For rusa88

These answers address the searches we hear most often before an account is opened or a wallet record is queried. If your situation is not covered, use the account support path and keep payment references limited to the receipt details we request.

The rusa88 Privacy Policy covers account, phone verification, device, cookie, support and payment-reference data. It explains why we use each category and how you can request access or correction.

Yes. The Privacy Policy covers DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account records when they are matched with your account or a support query.

Start from the signed-in support path and complete the phone check we request. This helps us confirm ownership before discussing account data or changing a phone, device or wallet record.

You can ask rusa88 to correct inaccurate contact, verification, device or account entries through support. We may request a receipt reference or phone confirmation before making the change.

Cookies may keep your session and selected settings available on a mobile browser. You can clear them in browser controls, but the next sign-in may require phone verification and fresh account access.

We keep payment references while they serve account, security, support or legal purposes described in the Privacy Policy. When that need ends, records may be removed or separated from active account access.

You can submit a deletion request through the account support path. We assess the request against operational and legal needs, with the result depending on local law and where local law permits.