Reference

Privacy Policy For Your agung711 Account

agung711 sets out how we collect, use and protect the account, wallet and device details connected with your access to Sic Bo, 21bet and Royal Fishing.

Account clarityWallet recordsDevice controlsPolicy access
agung711 Privacy Policy For Your agung711 Account
POLICY HELP ROUTE

Get Clear Answers About Your Data

You can ask us about the Privacy Policy without guessing which department handles your request. Start with the policy contact route, include the account detail needed to locate your record, and avoid sending wallet passwords or full payment credentials. If your question follows a DANA or QRIS status issue, the cashier support path can connect the policy question with the relevant receipt reference. Access and eligibility questions are handled where local law permits.

Team online

Policy contact route

Use the contact path shown with our Privacy Policy to ask what data we hold, why it is used, or how long a record remains. Include your account identifier and the subject of your request so we can locate the right record without asking for unnecessary wallet details.

Cashier status help

When a privacy question relates to a DANA, OVO, GoPay or QRIS receipt, keep the reference number and approximate time ready. Our support path can compare that reference with the account record while keeping your wallet PIN and complete payment credentials out of the request.

Account access check

If a device change or phone verification step blocks your policy request, tell us which sign-in step stopped and whether you are using mobile or desktop. We may ask for account verification before discussing personal data, and any access decision depends on local law.

DATA HANDLING

Keep Control Of Account Details

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account data

We may collect your name, contact detail, account credentials and verification responses when you create or maintain an account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount, status and time record.

Cookies and devices

Cookies can keep a session connected and help us understand whether a sign-in is continuing on the same browser.

Account security

We use sign-in history, phone verification and unusual-device signals to reduce the chance that another person reaches your account.

Retention timing

We retain each category only while it supports the purpose described in the Privacy Policy, account administration, a transaction query…

Changes and requests

You may ask us to access, correct or clarify personal data connected with your account.

Privacy Policy Answers For agung711

These Privacy Policy questions cover the account steps Indonesian customers most often need to understand before sending personal or payment-related details. Each answer points you back to the relevant request path, device behaviour or wallet record, so you can decide what to share and how to ask us for clarification.

The agung711 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references, support requests, retention and data changes. It explains why we use each category and how you can contact us about a record connected with your account.

We may collect the contact details, credentials and verification responses needed to create and protect your account. We can also record sign-in time, device type and account actions. We use those details for access checks and account administration, not to request your DANA or wallet password.

Yes. The Privacy Policy covers records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These may include a reference, status, time and account match needed to check a receipt. We do not need your wallet PIN for that process.

Cookies can keep your browser session connected and help us recognise whether access continues on a familiar device. If you clear cookies, change browser settings or move from phone to desktop, you may need to sign in and complete phone verification again.

Use the policy contact route shown on the Privacy Policy page and describe the account record you want to access or correct. Include your account identifier, but do not send a password or wallet PIN. We verify the requester before responding, and the result depends on local law.

We keep account, payment-reference and security records only for the period needed for their stated purpose, account administration, dispute handling or a legal duty. The exact period can vary by record type. When it is no longer needed, we remove it, anonymise it or restrict use.

Yes. Tell us the approximate sign-in time, device type and account detail connected with the question through the policy contact route. We may request account verification before discussing the record. If the request concerns access or eligibility, the outcome depends on local law.