Reference

atm288 Privacy Policy For Your Account

atm288 Privacy Policy explains what we collect when you open an account, use the Live Dealer Lobby, or check DANA, OVO, GoPay and QRIS status.

Account dataCookie choicesWallet recordsPhone verification

Explore Our Lobby Read FAQ

DANA, QRIS And Your Privacy Policy

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

Our Privacy Policy covers the details needed to create and protect your account, confirm a phone number, process a wallet request, and answer a support question. When you select DANA, OVO, GoPay or QRIS, we may record the payment reference, amount, status and time so a

1
pending cashier step can be checked without guessing. Bank transfer and virtual account records are handled for the same account-reconciliation purpose. We also receive technical details such as browser type, device settings, IP address and login events to identify unusual access. We use this material for
2
account operation, security, legal duties and service messages, not for unrelated purposes. Access depends on local law, and the policy applies where local law permits your account activity.

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

HELP PATH

Get Privacy Policy Help From Your Account

A policy question should have a practical route, especially when a wallet status or login event appears unfamiliar. We keep support close to the account area so you can ask about data use, request a correction, or query a payment record without sending sensitive details through an unrelated channel. Your account step helps us match the request to the right record.

Team online

Account support

Open the support route after signing in and state that your question concerns the Privacy Policy. We use your account details to locate the relevant login, cookie choice or wallet record.

Wallet query

For DANA, OVO, GoPay or QRIS questions, include the visible reference and date rather than your wallet password or full security code. This lets us check status while limiting exposed data.

Access request

Ask us to correct, export or clarify account data through the same support path. We may verify phone ownership before changing records, because a policy request must come from the account holder.

CONTROL DETAILS

How atm288 Protects Account Data

Privacy work is part of the account flow, not a separate page you need to decode later.

Account security

Phone verification is requested before account access is completed. Login events and device signals help us spot an unusual route, while your password and security codes should remain private and never be placed in support messages.

Cookie choices

Cookies help retain sign-in state, remember selected settings and measure page operation. You can manage browser cookie controls, although restricting them may require another login before the lobby opens.

Payment separation

DANA, OVO, GoPay and QRIS references are used to match a request with its account status. We do not need your wallet password to check whether a reference is pending, accepted or awaiting confirmation.

Device behaviour

On mobile, we may record browser and device signals when you move from login to the Live Dealer Lobby or Fishing God. These signals support security checks and are not a substitute for your account credentials.

Data retention

We keep account, payment and security records only for the operational, dispute and legal periods that apply to them. When a record no longer needs retention, our handling follows the applicable deletion process.

Policy changes

If our Privacy Policy changes in a material way, we will present the updated wording through an account or site notice. You can contact support to ask which section changed and when the update took effect.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account questions that arise before or after you connect an Indonesian wallet. If your situation is not covered, use the account support path and describe the specific record, device event or payment reference you want us to check.

It covers account details, phone verification, device and browser signals, cookies, wallet references, support requests, retention and policy changes connected with your atm288 account.

We use phone verification to confirm account ownership before access is completed and to help resolve an account request. It also reduces the chance of an unauthorised person changing your records.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including status, amount, date and matching details needed to reconcile an account request.

You can request a correction through the signed-in support route. We may ask for phone verification or another account check before changing a record, so the request is linked to you.

Cookies can retain sign-in state and selected settings. If you block them in your mobile or desktop browser, you may need to authenticate again before opening the lobby.

We retain payment and account records for the operational, dispute and legal periods that apply. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references follow that process.

Sign in and use the account support route, then identify the policy section or record involved. Do not send a wallet password or full security code when asking for help.

atm288 Privacy Policy For Your Account

Get Privacy Policy Help From Your Account

Account support

Wallet query

Access request

How atm288 Protects Account Data

Account security

Cookie choices

Payment separation

Device behaviour

Data retention

Policy changes

Privacy Policy Answers For Your Account

01 What does the atm288 Privacy Policy cover?

02 Why does atm288 collect phone verification data?

03 Does the Privacy Policy cover DANA and QRIS data?

04 Can I ask atm288 to correct my account data?

05 How do cookies affect my atm288 account access?

06 How long does atm288 keep payment records?

07 Where can I ask about the atm288 Privacy Policy?

Related Pages