Reference

Privacy Policy For Your royaleboss Account

royaleboss Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity explainedAccount access choicesIndonesia policy context
Explore Lobby Read FAQ
royaleboss Privacy Policy For Your royaleboss Account
HELP PATHS

Privacy Questions Near Your Wallet Status

A clear contact path helps when you want to ask about Privacy Policy or check which account detail is stored.

Account data request Use the account support route to ask what personal details are connected with your profile, including phone verification status and sign-in records. We may ask for an account step to confirm that the request comes from you before discussing private information.
Wallet reference check For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate transaction details through support. We use that context to locate the relevant status without asking you to disclose your wallet password or private security code.
Access and correction If a stored name, phone detail or account record appears incorrect, contact support and explain the change you need. We review the request against your account verification details and tell you what can be corrected where local law permits.
DATA PRACTICE

Inside royaleboss Privacy Policy Controls

Our handling process follows the account actions you take rather than treating every detail as permanent profile content.

Account details

We collect details you provide during account opening and phone verification, such as contact information needed for access. These records let us connect a support request to the correct profile and help prevent another person from changing account information.

Payment references

Wallet activity can create references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account processing. We use those references to match status and investigate receipts; the payment provider remains responsible for information it handles in its own service.

Device sessions

When you sign in on a mobile browser or desktop, technical session data can show device type, time and security events. We use it to maintain the account path from login to the lobby and to investigate access that does not match your normal activity.

Cookies and storage

Essential cookies or local storage may keep a session active, remember a necessary setting or support account navigation. Clearing browser data can remove these records and may require you to sign in again or repeat an account verification step.

Retention decisions

We retain account, security and transaction references only for as long as they serve access, dispute handling, fraud prevention or legal obligations. Retention can differ by record type, and we explain the applicable position when you make a specific data request.

Your contact rights

You can contact us to ask for access, correction or clarification about personal data connected with your profile. Send the request through support from the relevant account; we may verify ownership first and then explain the available action where local law permits.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the account and wallet questions we expect you to ask before using royaleboss. They cover the data created by registration, phone verification, mobile sessions and payment references. If your situation is different, contact support from the relevant account so we can assess the record and the request under the applicable local rules.

It covers account details, phone verification, sign-in and device records, cookies, payment references and support messages connected with your use of royaleboss. It also explains why we use those details, how retention works and how you can request access or correction where local law permits.

Phone verification helps us connect account access with the person opening the profile and gives support a way to check ownership before discussing private records. We may use verification status during a login or data request, but you should never send a one-time code in a support message.

Yes. Privacy Policy covers the payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. We use these details to match a receipt or investigate a pending status, while the payment provider handles data within its own service.

A mobile browser or desktop session can produce technical details such as device type, session time and security events. We use them to keep your account path working and identify unusual access. They are not used as a public profile, and clearing browser storage can end your session.

Contact support from the account connected with the record and describe the name, phone detail or other information that needs correction. We may ask for an account verification step before changing anything, then explain whether the request can be completed where local law permits.

Retention depends on the type of record and why it is needed. Account, security and transaction references may remain for access support, dispute handling, fraud prevention or legal obligations. When you ask about a specific record, we can explain the relevant retention position under applicable rules.

You can contact us with an access request about personal data connected with your account. Use the account support path and provide enough detail for us to locate the profile. We verify ownership first, then respond with the information and limitations that apply where local law permits.

Related Pages

royaleboss Indonesia MotoGP Grand Prix Account information FAQ About Us