Reference

royalbola Privacy Policy for Your Account Data

Our Privacy Policy explains what royalbola collects when you open an account, use the mobile lobby, or connect a local wallet.

Clear data purposesWallet record contextAccount request pathMobile privacy choices
royalbola royalbola Privacy Policy for Your Account Data
PRIVACY HELP ROUTES

Where to Ask About Privacy Policy

A clear contact path matters when an account record or wallet reference looks unfamiliar. We route Privacy Policy questions through account support, where you can identify the relevant sign-in, receipt or verification…

Account support Ask about a phone number, verification record or sign-in event through the account support route. We may request account identifiers so we can separate your request from another account safely.
Wallet status For DANA, OVO, GoPay or QRIS references, include the receipt reference and approximate time. We use those details to investigate the record without asking you to disclose a wallet password.
Policy questions Send a specific question about collection, cookies, retention or correction through our contact route. We will explain which Privacy Policy section applies and what request details are needed.
DATA PRACTICE

How We Handle Account Privacy

Privacy Policy choices should match the way your account actually works. We separate sign-in records, device events, wallet references and support conversations so each request can be checked against its purpose.

Account records

When you open an account, we record the details needed for access and verification. Keeping your phone number current helps us match a correction request with the right account.

Device signals

Browser type, device details, IP address and session events can be recorded when you sign in. These signals help us examine unfamiliar access without collecting the contents of your device.

Cookies

Cookies and similar storage can keep a session working and help us understand technical errors. Your browser settings can control some cookies, although changing them may affect account access.

Wallet references

DANA, OVO, GoPay, QRIS and bank transfer records may show a reference, amount status and time. We use them for matching, receipt checks and account support rather than wallet-password access.

Retention

We keep personal records for the stated purpose, account protection, dispute handling or a legal requirement. When a record is no longer needed, our process addresses removal or secure restriction.

Change requests

You can ask us to correct account details, explain a data use or address a deletion request. Include your account contact and the exact record so we can assess it properly.

Privacy Policy Answers for royalbola

These Privacy Policy answers cover the questions we expect before you open an account or connect a wallet. They explain the practical route for access, correction, deletion and contact, while the full policy remains the reference for any specific request. If your situation concerns local eligibility, access depends on local law.

It covers account details, verification records, device and session signals, cookies, wallet references and support messages collected while you use royalbola services. It also explains purposes, retention and request routes.

Device and browser signals help us recognise an unusual sign-in, keep a mobile session stable and investigate technical errors. We use these signals for account protection and service diagnosis, not to read private device content.

Yes. The policy covers payment references connected with DANA, OVO, GoPay and QRIS, including status, receipt reference and timing used to match account activity or answer a support request.

Contact account support with the account phone number or another identifying detail and describe the record that needs correction. We may ask for verification before changing information linked to account access.

You can send a deletion request through our privacy contact route. We assess the request against account security, unresolved disputes and any legal retention duty, then explain what can be removed or restricted.

We keep each record for its stated purpose, account protection, dispute handling or a legal requirement. The applicable period can differ by record type, so contact us for a request about a specific item.

Use the account support or privacy contact route and describe the exact concern, such as cookies, a verification record or a QRIS receipt reference. Do not send your wallet password or full security code.