Reference

atm228 Privacy Policy For Your Account

Our atm228 Privacy Policy explains how we collect, use and protect the details connected to your account, including phone verification and wallet status for DANA, OVO, GoPay and…

Clear data purposesWallet record controlsAccount access requestsCookie choices
atm228 atm228 Privacy Policy For Your Account
CONTACT ROUTES

Support For Privacy And Wallet Records

A clear contact route matters when you want to ask about a receipt, login record or personal detail. Start from your account help path and include the phone number linked to your account, the relevant date and the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a full wallet password.

Team online

Account help

Use the account help route for questions about phone verification, login records, cookie choices or a request to correct your personal details. We may ask you to confirm the account step involved before discussing any private record.

Payment receipt

For a DANA, OVO, GoPay or QRIS query, send the payment reference and status shown in your wallet. We compare that reference with our transaction record and explain which data was used to trace the request.

Data request

Ask us to access, correct or remove eligible account details through support. Include a reachable contact route and a short description of the change; we verify ownership before releasing or altering private data.

CONTROLLED DATA FLOW

QRIS Cookies And Account Safety

We keep this policy connected to the account actions you can actually recognise: opening a session, checking a wallet status, entering a game such as Speed Blackjack Live, or sending a support…

Account details

We use your phone number and verification result to establish that an account request belongs to you. Contact details are also used to answer support messages, while optional details are not treated as required account data.

Wallet matching

A DANA, OVO, GoPay or QRIS reference lets us match a payment status to the correct account action. We use the reference for tracing and reconciliation, not as a substitute for your wallet password or security code.

Cookie settings

Cookies and similar device signals help keep your login session, language choice and page state available while you move through the lobby. You can ask support what signal is linked to a session and request a suitable change.

Device protection

Browser type, device signals and login timestamps help us spot an unusual access pattern. If your mobile session behaves differently from your desktop session, account support may ask you to confirm the recent access before making changes.

Record retention

We keep account, payment and support records for the period needed to operate the requested service, resolve disputes and meet applicable legal duties. When that purpose ends, the record is removed, anonymised or no longer kept where permitted.

Change requests

You can ask for a copy, correction or deletion of eligible personal details through account support. We check account ownership first, explain any limit that applies, and confirm the action taken through the contact route you provide.

Privacy Questions For Your Wallet

These Privacy Policy answers focus on the account and wallet questions you may have before opening an account. We explain the practical route for data access, corrections, cookies, payment references and account closure without turning the policy into general lobby copy. If your question is not covered, contact us through account support with the relevant account step or receipt reference.

The atm228 Privacy Policy covers account details, phone verification, device and cookie signals, payment references, support messages and security records. It explains why we use each category, how you can ask about it, and when access depends on local law or is available where local law permits.

When you select DANA or QRIS, we receive a transaction reference and status details needed to connect the request to your account. We use that record to trace a receipt or stalled status. We do not need your wallet password to investigate the payment path.

Yes, you can contact account support to request eligible account data held about you. Include your account contact route and the type of record you want, such as phone verification, login activity or a GoPay payment reference. We verify ownership before sharing private details.

Send a correction request through the account help path and describe the detail that needs changing. A phone number, contact route or profile entry may require an ownership check before we edit it. We will explain any record that cannot be changed under applicable legal rules.

Yes. The policy covers cookies and device signals used to keep a mobile login, page state and language choice connected during your session. If you move from mobile to desktop and notice a session issue, contact support so we can identify the relevant cookie or access record.

We keep payment records for the operational, dispute and legal period connected to the request. This can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. After the purpose ends, we remove, anonymise or stop retaining the record where permitted.

Yes. You can still contact us about a copy, correction or deletion request after account closure. Some records may need to remain for dispute handling or legal duties, and we will explain that reason. Access to any related service depends on local law and where local law permits.