Reference

Privacy Policy for Your anker77 Account

anker77 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Baccarat Royal or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
anker77 Privacy Policy for Your anker77 Account
CONTACT PATHS

Where Privacy Policy Questions Get Answered

A clear contact route matters when a Privacy Policy question involves your account or wallet record.

Account support Use the support link inside your account for Privacy Policy questions tied to your phone verification, sign-in record or stored profile details. We can route the request without asking you to post private account data in a public message.
Wallet records When a question concerns DANA, OVO, GoPay or QRIS, attach the relevant transaction reference rather than a full wallet password or personal message history. We use the reference to locate the record and explain what data was stored.
Access requests Ask us for a copy, correction or deletion assessment through the account support path. State the request clearly, and we will first confirm account ownership before releasing or changing personal data where local law permits.
HANDLING YOUR DATA

Account Security And Data Choices

We treat this Privacy Policy as an operating process, not a page kept apart from the account flow.

Collection

We collect details you enter during account opening and data produced by account activity, such as sign-in time, device type and wallet references. We do not need your full wallet password to investigate a DANA or QRIS receipt.

Cookie controls

Cookies can keep your session active and remember selected settings. You can adjust cookie controls in your browser, although blocking necessary cookies may affect sign-in or the page that displays your Privacy Policy choices.

Account security

Phone verification before account access gives us a practical signal when handling a data request. We may compare sign-in and device details when a request involves a changed phone number or an unfamiliar access pattern.

Retention

We keep account, transaction and support records for the period needed to operate the service, resolve a dispute, protect access or meet a legal need. After that point, records may be removed or anonymised.

Your changes

You can ask us to correct inaccurate account details or explain why a record remains stored. Send the request from your account support path, and include the specific field or transaction reference you want checked.

Data contact

For a Privacy Policy request, contact us through the support route shown after sign-in. If access is unavailable, identify the account phone number and request type so we can begin ownership checks safely.

Privacy Policy Questions About anker77

These Privacy Policy answers cover the questions we expect before account opening, especially around identity checks, local wallets, cookies and access requests. If your situation is not listed, use the support path connected to your account and describe the exact record you want us to check.

It covers personal details supplied during account opening, phone verification records, sign-in and device signals, cookie activity, support messages and transaction references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number to create and verify the account, connect you with the correct profile and handle access requests. Verification may be required before we discuss private records or change account details where local law permits.

Yes. The policy includes wallet and transaction references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account records. We use them to match status questions and receipts, not to request your wallet password.

Contact support from your signed-in account and ask for an access request. Tell us which records you need, such as profile details, cookie choices or a QRIS receipt. We will confirm ownership before responding where local law permits.

Yes. Send a correction request through the account support path and name the field that is inaccurate, such as a phone number or profile detail. We may request phone verification before changing the record to protect account access.

We retain records while they are needed for account operation, transaction checks, security, disputes or legal needs. When a record is no longer required, we remove or anonymise it according to our operating process.

Yes. Account access and eligibility depends on local law. Where local law permits, you can use the support path to ask about your account data, cookie choices, retention or a request to correct or remove records.