Reference

atom368 Privacy Policy For Indonesia Accounts

Our Privacy Policy explains what account, device and wallet details we collect when you open an atom368 account, check Baccarat or Starlight Princess, and use DANA, OVO, GoPay…

Account dataWallet recordsDevice signalsPrivacy requests
atom368 atom368 Privacy Policy For Indonesia Accounts
REQUEST ROUTES

Privacy Help Beside Your Account Path

A clear contact path matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Policy questions Ask us which account, login or payment records relate to your Privacy Policy request. Include your registered phone number and the date of the DANA, OVO, GoPay or QRIS activity.
Data correction Tell us which profile detail needs changing and why it is inaccurate. We may request an account verification step before updating the record connected to your atom368 access.
Wallet records For a cashier history question, identify bank transfer, virtual account or QRIS and the related transaction reference. We use those details to check the matching account record.
DATA HANDLING

What We Do With Your Privacy Data

Our handling choices are tied to practical account events rather than broad profile building. Login security, wallet matching and policy requests each create different records, and our retention approach follows the reason…

Account details

We use your phone number and account details to identify the correct account, complete the clear phone verification step before access, and answer a Privacy Policy request without mixing records.

Device signals

Browser, device and session signals help us spot unusual sign-ins across mobile and desktop paths. They support account security and are not treated as wallet credentials.

Cookie choices

Cookies can keep a session working and help us understand which policy page or account step was opened. Your browser settings can restrict cookies, though some access steps may change.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help reconcile cashier activity. We use the reference needed for checking, rather than asking for your wallet password.

Retention timing

We retain account, security and transaction records for the period needed for their stated purpose, account support and legal requests. The current Privacy Policy explains the applicable retention context.

Change requests

To request access, correction or deletion where available, contact support through the account help route beside the cashier path. We verify ownership before discussing or changing personal data.

Privacy Policy Answers For atom368

These Privacy Policy questions cover the account and payment situations you are most likely to search before opening access. We keep the answers tied to real steps, from phone verification and mobile sessions to wallet references and requests for data changes.

It covers account details, phone verification, device and session signals, cookie use, payment references and support requests connected with your atom368 access in Indonesia.

We may collect your phone number, account details, verification response, browser and device signals, session events, and transaction references from DANA, OVO, GoPay, QRIS or bank transfer.

No. Our payment matching uses the transaction reference needed to connect cashier activity with your account. We do not need your DANA, OVO, GoPay or QRIS wallet password.

Use the support route beside the cashier path and state which account detail is inaccurate. We may complete an ownership check before correcting the record or discussing its status.

Cookies may keep your login session working and record which policy or account step you opened. Browser controls can restrict them, although some access functions may respond differently.

We keep each record for the period needed for its stated purpose, account security, payment checking, support handling or legal requests. The current Privacy Policy gives the relevant retention context.

Yes, where local law permits. Send a request through the account support path with your registered phone number and the record type, such as device access or QRIS activity.