Reference

rusa55 Privacy Policy: Your Data Path

rusa55 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse Aviator or Super Bingo, and use DANA or QRIS.

Account dataWallet recordsCookie choicesDevice access
rusa55 rusa55 Privacy Policy: Your Data Path
HELP WITH YOUR DATA

Get Privacy Help Near Your Account

A clear support route helps you ask about the Privacy Policy without sending sensitive wallet credentials.

Policy questions Ask how we handle account, cookie or device data through the support link on your signed-in account page; we will use your account detail to locate the relevant record.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference rather than a wallet password so we can check status with less exposure.
Change requests Request a correction or deletion by naming the account field concerned; we may confirm your sign-in detail before changing records, where local law permits.
YOUR CONTROL PANEL

Keep Account And Device Data Clear

We organise this Privacy Policy around the points you can check: what enters our systems, why it is used, how long it is retained and who can help.

Account details

We use the phone or email attached to your account for sign-in checks, account messages and request matching. Please keep those details current so a data request reaches the correct record.

Device signals

When you open the lobby on a phone or desktop browser, we may record browser type, device signals and sign-in time to identify unusual access and protect your account.

Cookies

Cookies can keep your session working and help us understand account navigation. Your browser settings let you remove or restrict them, although some sign-in functions may then need another step.

Wallet security

For DANA, OVO, GoPay, QRIS and bank transfer activity, we retain references and status rather than asking you to disclose a wallet password in support messages.

Retention period

We keep account, security and transaction records only for the period needed for service operation, dispute handling, fraud checks and legal duties, then remove or restrict them when appropriate.

Your request path

To ask who handles a record, request access, correct a field or seek deletion, use the signed-in support route and identify the account detail involved; local law determines available options.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the practical questions we hear before account access: what data is collected, how payment references are used, what happens on a mobile browser and how to ask for a change. If your request concerns a specific record, sign in first so we can match it accurately.

It covers account details, sign-in activity, device signals, cookies, support messages and transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

We use the phone or email linked to your account for access checks, request matching and account messages. Keeping it current helps us confirm that a data request belongs to you.

Yes. We record a payment reference, amount status and related account match for QRIS, DANA, OVO and GoPay activity, so support can check a receipt without asking for wallet credentials.

When you sign in through a phone or desktop browser, we may record browser type, device signals, session timing and access events to identify unusual activity and protect your account.

Sign in, open the support link beside the cashier area and name the account record you want to access or correct. Available requests depend on local law and identity checks.

You can submit a deletion request through the signed-in support path. We assess it against service, security, dispute and legal retention needs, and respond where local law permits.

We retain payment references and account records for the period needed for service operation, security checks, disputes and legal duties. After that, we remove or restrict them when appropriate.