Reference

royalmpo Privacy Policy For Your Account

The royalmpo Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move between the lobby and cashier.

Clear data purposesWallet activity recordsAccount access controlsCookie choices
royalmpo royalmpo Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Through The Account Route

A clear contact route helps you act on the Privacy Policy without searching through unrelated pages. We handle privacy questions alongside account and wallet checks, so your request can include the email or phone detail attached to your profile, the relevant payment reference, and the action you want us to take. Where local law permits, we can explain a data request, correct an account detail, or clarify why a record remains stored.

Team online

Account privacy request

Send your privacy question through our account support channel and include the contact detail attached to your profile. We use that step to locate the correct record, explain the Privacy Policy, and reduce the chance of discussing account data with the wrong person.

Wallet record check

For a DANA, OVO, GoPay, or QRIS question, include the payment reference and date shown in your cashier history. We compare that reference with the stored status, so we can separate a wallet issue from an account data request before replying.

Login and device query

If a new phone, browser, or login location creates an access question, tell us the device path and approximate time. Our support team can explain the security record connected with that session and outline the Privacy Policy step that applies.

DATA PRACTICES

What We Keep And Why

Privacy at royalmpo is managed through practical account controls rather than broad statements. We separate contact details, login events, wallet references, and support conversations by their operational purpose.

Account data

We collect the details you enter when opening and maintaining an account, such as your contact information and verification status. The Privacy Policy connects those details to access control, support handling, and account notices rather than unrelated advertising purposes.

Cookie handling

Cookies can keep a session active, remember a device preference, and help us identify a page problem. You can manage browser cookie settings, although changing them may interrupt login or require another account check before the lobby opens.

Payment references

A DANA, QRIS, OVO, or GoPay transaction gives us a reference, amount status, and timing needed to match the cashier event. We use that record for reconciliation and support, not to request your wallet password or private wallet login.

Account security

Login time, device type, browser details, and unusual access signals can be recorded to protect your account. If a security check pauses access, our support route can explain the next account step where local law permits.

Retention periods

We keep records only for the period needed for the stated purpose, account security, dispute handling, or a legal duty. A payment reference may remain after a session ends because it supports reconciliation and any later request about that transaction.

Changes and requests

You can contact us to ask what personal data is held, correct a detail, question its use, or request removal where local law permits. Include your account contact and a precise request so we can verify identity and respond to the right record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. They explain what happens when you open access, use a local wallet, return on another device, or ask our support team about stored data. Service access depends on local law, and our response may require an account check before we disclose or change personal details.

The royalmpo Privacy Policy covers account details, verification records, login and device events, cookies, payment references, and support conversations. It explains why we use each category, how retention works, and how you can ask about correction, access, or deletion where local law permits.

We collect the contact details and verification information you submit during the account path, plus technical details needed for a secure session. This can include device type, browser data, login time, and approximate network location. We use these details for access and support.

No. When you use DANA, OVO, GoPay, or QRIS, we keep the transaction reference and payment status needed to match the cashier event with your account. We do not need your wallet password, and you should never send that password to support.

Contact our account support channel with the email or phone detail connected to your profile and state whether you want access to a record or correction of a specific field. We verify the request first, then respond according to the Privacy Policy and local law.

Retention depends on the record and its purpose. Login events may support security checks, while payment references can remain for reconciliation, disputes, or a legal duty. The Privacy Policy does not treat every record alike, and we can explain the reason for a stored item.

A phone, tablet, or desktop can create a new device and session record used to protect account access. Returning from Bandung or another Indonesian location does not by itself change your policy rights, but an unusual login may require an additional account check.

You can ask us to remove personal data where local law permits and should identify the account record concerned. We may retain payment, security, or support records when a legal or operational reason applies, and the Privacy Policy explains why that exception may remain.