Reference

Open royal228 With Clear Privacy Terms

Your royal228 Privacy Policy explains what we collect when you create an account, sign in, and connect DANA, OVO, GoPay or QRIS.

Clear data purposesWallet checks explainedMobile policy accessAccount contact path

Explore Our Lobby Read FAQ

Check How Your Account Data Moves

royal228 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to create and protect your account, including contact information, sign-in records, device signals, verification results and payment status. When you use DANA, OVO, GoPay or QRIS, we may receive a transaction reference, amount status and time from the payment flow; we

1
do not treat your wallet PIN as a lobby detail. Bank transfer and virtual account records may also be matched to your account so we can resolve an unsettled receipt. We use cookies and similar tools for sign-in continuity, security checks and page preferences. Access and
2
eligibility depends on local law, and this Privacy Policy applies to our handling of data connected with your royal228 account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT OPTIONS

Contact Us About Privacy Questions

A direct support route helps you ask about the Privacy Policy without placing sensitive details in a public message. Open the support chat from your account area and tell us whether your question concerns sign-in records, a DANA or QRIS reference, cookie settings, or a correction request. We may ask you to confirm account ownership before discussing personal data, and you should never send a wallet PIN or full authentication code.

Team online

Account chat

Use the support chat linked from your account area when you want to ask how royal228 stores sign-in records, device details or phone verification results. We may request an account identifier so we can answer about your own data rather than disclose details to the wrong person.

Wallet receipt

For a DANA, OVO, GoPay or QRIS receipt, share the transaction reference and visible status only. We compare that reference with the account record and can explain which data is retained for payment matching. Do not include your wallet PIN, password or one-time authentication code.

Correction request

If your phone, email or account detail needs correction, contact us through the same support path and describe the change clearly. We verify account ownership before editing records, then confirm whether the request is completed, needs more evidence, or is limited by a legal or security requirement.

DATA PRACTICES

Explore How We Protect Your Records

Our privacy process follows the account actions you can see: phone verification before account access, wallet status checks at payment points, and device signals that help identify unusual sign-ins.

Account details

We use your phone or contact details to create the account, send access-related messages and complete the clear phone verification step before entry. If those details change, ask support to update them after ownership checks. We do not need your wallet PIN for this account process.

Device signals

When you move from mobile login to the lobby, we may record device, browser and sign-in time signals. These records help us spot unusual access and protect your account. They are security context, not a request for unrelated files, photos or contacts on your device.

Cookies

Cookies can keep a sign-in path working, remember a language or page preference, and support security checks. You can manage cookies through your browser settings, but restricting them may require a fresh login or make some policy and account pages behave differently on mobile.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references needed to match a payment with your account. The record can include status, amount and time. It helps us trace a receipt without asking you to reveal a wallet PIN.

Retention period

We keep personal data for as long as it supports account security, payment matching, dispute handling or applicable legal duties. When a record no longer serves one of those purposes, our handling process can remove or separate it. Support can explain the reason for a retained record.

Your request

You may ask for a copy of account data, correction of an inaccurate detail, or clarification about deletion by contacting support from your verified account path. We check identity first, describe any restriction, and respond through the contact route connected with your account rather than an unverified address.

Find Answers About Privacy Policy

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening royal228. We keep the route practical: check the policy from mobile or desktop, use the verified support chat for a personal request, and mention the relevant payment reference when your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

The royal228 Privacy Policy covers data connected with account creation, phone verification, sign-in, device signals, cookies, support requests and payment references. It explains why we use those details, how we protect them, how retention works, and how you can request access or correction.

We do not need your DANA or QRIS wallet PIN for account or payment matching. We may retain a transaction reference, status, amount and time so support can connect a receipt with your account. Never send a wallet PIN or one-time authentication code in chat.

Yes. Use the verified support path and identify the phone, email or other account detail that is inaccurate. We confirm account ownership before making a change, then tell you whether the correction is complete or whether a security or legal reason limits the request.

Ask support for a copy of the personal data connected with your account and make the request from your verified account route. We may ask for an account identifier or phone confirmation. The response can cover sign-in, device, cookie, support and payment-reference records we hold.

We retain payment references for as long as they are needed for payment matching, account security, dispute handling or applicable legal duties. This can include DANA, OVO, GoPay, QRIS, bank transfer and virtual account status. Support can explain why a specific record remains available.

Yes. Your mobile browser controls cookie settings, so you can restrict or remove them through its privacy menu. Some account pages may then require a new login or lose a saved preference. Security-related cookies can affect access checks, so read the prompt before changing them.

The policy describes our data handling for supported account access in Indonesia, while eligibility and access depends on local law. If you are unsure whether an account path is available in your area, contact support before submitting personal details or connecting a wallet.

Open royal228 With Clear Privacy Terms

Contact Us About Privacy Questions

Account chat

Wallet receipt

Correction request

Explore How We Protect Your Records

Account details

Device signals

Cookies

Payment records

Retention period

Your request

Find Answers About Privacy Policy

01 What does the royal228 Privacy Policy cover?

02 Does royal228 store my DANA or QRIS PIN?

03 Can I ask royal228 to correct my account data?

04 How can I request a copy of my Privacy Policy data?

05 How long does royal228 keep payment records?

06 Can I change cookie settings on my phone?

07 Does the Privacy Policy apply everywhere in Indonesia?

Related Pages