Reference

roma99 Privacy Policy For Your Account

Your DANA, OVO, GoPay and QRIS activity deserves a clear record of what we collect and why.

Account dataWallet referencesCookie choicesRequest support
roma99 roma99 Privacy Policy For Your Account
CONTACT DATA TEAM

Privacy Questions From Your Account

A direct support path helps when your Privacy Policy question concerns a login record, wallet reference or device entry.

Account access If you cannot access your account, tell us the registered contact detail and device…
Wallet status For a QRIS, bank transfer or virtual account question, send the payment reference and…
Data request To ask for a copy, correction or deletion of eligible personal data, state the…
ACCOUNT SAFEGUARDS

What We Do With Your Data

Privacy work is tied to practical account steps rather than broad promises. We separate payment references from wallet secrets, use sign-in checks to identify unusual access and keep…

Collected details

We may handle your name, contact detail, account credentials, sign-in time, device signals and transaction references.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show status, amount reference and timing.

Cookie controls

Cookies can remember a browser setting, maintain an account session or flag unusual sign-in behaviour.

Account security

Keep your contact detail current and do not share your password or verification code.

Retention period

We keep personal and transaction records only while needed for account administration, security checks, dispute handling or a lawful obligation.

Changes and requests

You can ask about the data connected to your account, request a correction or seek removal where eligible.

Privacy Policy Answers For roma99

These Privacy Policy answers address the account, payment and device questions you may search before opening an account. If your situation is not covered, use the support path with the contact detail connected to your roma99 account.

It covers account details, sign-in records, device signals, cookies, payment references and how long those records may be kept. It also explains how to request access, correction or removal where local law permits.

No. When you use DANA or OVO, we handle the payment status and reference needed to match the request. Your wallet password and verification code should remain private and must not be sent to support.

QRIS, bank transfer and virtual account activity can create a reference, status or time record linked to your account. We use those details to reconcile a request and investigate a missing or mismatched status.

Use the support route connected to your account and ask for a data copy. Include your registered contact detail and the type of record you need; we may verify ownership before providing eligible data.

Yes, where local law permits. Send the correction request through account support and identify the inaccurate field, such as a contact detail. We may ask for verification before updating the account record.

We retain account, security and transaction records for as long as needed for administration, dispute handling, safety checks or a lawful obligation. After that, we delete or anonymise them when appropriate.

Yes. Your browser or device settings can limit or remove cookies. Some account functions may then ask you to log in again, and certain session or security features may not work as intended.