Reference

rog777 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact us about wallet status.

Account clarityWallet recordsCookie choicesSecurity requests
rog777 rog777 Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Data Request Path

A privacy question should not leave you guessing which account screen to use. Start from the support link beside the cashier area and include your account contact, the request you want handled, and any relevant receipt reference without sending a password. We use those details to locate the correct record, explain the next step, and keep wallet or login issues separate from a request about personal data.

Team online

Account data request

Ask us to confirm the personal data connected with your account. Include your registered contact so we can distinguish your request from a DANA, OVO, GoPay or QRIS status question.

Cookie assistance

If the mobile lobby behaves differently after cookie settings change, contact support through the account route. We can explain which session data is needed for sign-in without asking you to disclose a password.

Wallet record check

For a payment record question, send the transaction reference and method name, such as QRIS or bank transfer. We use the reference to find the matching account event and respond with the available status.

DATA HANDLING

What We Do With Your Privacy Choices

We keep this policy close to the account path so you can check it before opening an account or changing wallet details.

Account records

We use registration details, login events and phone verification records to connect you with your own account. Before discussing a record, we may ask you to confirm the registered contact so another person cannot request it.

Device behaviour

Browser type, device signals and session events can help us recognise an interrupted login or protect the account path. The same details help explain why a mobile lobby session may need to restart.

Cookies and sessions

Cookies can preserve sign-in state, language choices and basic session continuity. If you clear them, you may need to authenticate again before reaching account pages or checking a wallet record.

Payment references

A DANA, QRIS, GoPay, OVO, bank transfer or virtual account entry may create a reference, amount and status record. We use that trail to reconcile an account event, not to request your wallet login secret.

Security controls

Phone verification, sign-in checks and account activity signals help us identify unusual access. Keep your password private and contact us through the support route if a login event does not match your activity.

Retention and changes

We retain records for the period needed for account operation, dispute handling or legal duties. To ask for access, correction or another permitted change, use support with your registered contact and a precise request.

Privacy Policy Answers Before Account Opening

These answers focus on the questions you may search before opening an account with rog777 in Indonesia. They cover the records created by sign-in, phone verification, cookies and local payment references, plus the practical route for asking us to check, correct or explain data connected with your account.

It covers personal details, phone verification, login events, device signals, cookies, support messages and payment references connected with your account. It also explains retention, security handling and ways to request access or correction.

Yes. The policy covers references showing that a DANA, QRIS, OVO, GoPay, bank transfer or virtual account step was submitted. These records help us match a payment event with the correct account.

Phone verification helps connect account access to the contact you provided and supports security checks. We may use the record when handling a login concern or confirming that a data request comes from you.

Use the support link beside the cashier area and state that you want an account data request. Include your registered contact and avoid sending passwords, wallet PINs or other secret credentials.

You can send a correction request through the account support route. Tell us which field is wrong and provide the registered contact needed for matching; we will explain what can be changed and what verification is required.

Cookies can keep a mobile sign-in session, language choice and account path available. Clearing or blocking them may require another sign-in and can remove session continuity before you reach the lobby.

Yes. Account access and eligibility depends on local law, and our processing applies where local law permits. If a local rule affects your request, support will explain the applicable account or data step.