Reference

rubah4d Privacy Policy For Your Account

rubah4d keeps this Privacy Policy practical: you can see what account details, wallet records, device signals and cookie settings we use before opening an account.

Account detailsWallet recordsDevice accessCookie choices
Explore Our Lobby Read FAQ
rubah4d rubah4d Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Wallet Status

A clear contact path helps when a privacy request and a payment reference meet in the same account. Use our support route for questions about account records, cookie choices, phone verification or wallet status; include only the details needed to locate your account. We may ask you to confirm account ownership before discussing or changing personal records.

Team online

Account privacy request

Ask support to explain, correct or remove account details where local law permits. We first check the account step and phone verification status so a request is handled for the right person.

Payment record question

If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks wrong, send the receipt reference through support. We use it to trace status without requesting your wallet password.

Device access concern

Tell us when an unfamiliar browser or phone appears on your account. We can review the sign-in trail, ask for an ownership check and help secure access before discussing stored account details.

HANDLING PRACTICES

Privacy Controls From Login To QRIS

We handle this policy area through ordinary account controls rather than vague promises. Login records, wallet references and device signals help us connect an action to your account, while your requests give…

Account details

We use details such as your account identifier and phone verification result to create access, protect the sign-in step and respond to account requests. We do not need your wallet password to check a payment reference.

Cookies and browser signals

Cookies and browser signals can help keep your session connected and remember selected settings. You can manage cookie controls in your browser, although changing them may affect login continuity or policy preferences.

Account security

We compare sign-in activity with device and browser signals to notice unusual access. If a new phone appears, contact support and complete the ownership check before asking us to change account records.

Wallet reconciliation

Payment references from DANA, OVO, GoPay and QRIS help us match a status to the correct account. Bank transfer and virtual account references serve the same matching purpose when those routes are selected.

Retention approach

We retain account, support and transaction references only for the period needed for account operation, dispute handling, security checks and legal duties. Retention can vary by record type and local legal requirements.

Changes and requests

You can ask who handles your record, request a copy, correct an error or ask about removal where local law permits. Support may request phone verification or another ownership check before acting.

Privacy Policy Questions For Your Account

These Privacy Policy answers cover the searches we hear most often before account access: what we collect, why wallet references appear, how cookies work and how to request a change. If your case involves a specific login or payment reference, use the support path above so we can check the relevant record.

It covers account details, phone verification, login activity, device and browser signals, cookies, support messages, payment references and retention. It also explains your request options where local law permits.

DANA and QRIS can provide a transaction reference or status connected with your account. We use that reference to reconcile a payment and investigate a mismatch, not to request your wallet password.

Our Privacy Policy does not require your OVO or GoPay wallet password for payment matching. We handle the account-linked reference or status needed to check the selected payment route.

We may handle browser type, device signals, login timestamps and related access records. These details help identify an unusual sign-in, connect a session and protect your account during a support request.

Contact support with your account identifier and explain whether you want a copy, correction or removal request. We may confirm phone verification and account ownership before changing or releasing records.

Retention depends on the record and the reason it was kept, such as account operation, security checks, payment disputes or legal duties. The Privacy Policy allows periods to vary where local law requires.

Yes. Open your mobile browser settings and adjust cookie controls for the site. Some choices may affect session continuity or saved preferences, while account and payment records remain governed by this Privacy Policy.

Related Pages

rubah4d Indonesia Secrets of Cleopatra FAQ Access guide Lightning Roulette