Reference

Privacy Policy for Your atlas23 Account

The atlas23 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the lobby and wallet areas.

Clear data purposesWallet record detailsAccount request pathMobile cookie choices
atlas23 Privacy Policy for Your atlas23 Account
CONTACT ROUTES

Get Privacy Policy Help Near Wallet Support

A clear contact path helps when you want to ask about the Privacy Policy or a wallet record.

Account privacy request Ask us to explain the personal data linked to your account. Include your registered phone number and request type so we can locate the correct account record without requesting your password.
Wallet record check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and timestamp. We use those fields to compare a wallet status with the matching account event.
Security concern If your phone, sign-in or account details look unfamiliar, tell us through the account help route beside the cashier path. We can review the reported event and explain the next verification step.
HANDLING DETAILS

How atlas23 Handles Your Policy Requests

Privacy work is tied to practical account events rather than broad statements. We separate sign-in checks from wallet references, use device signals to help identify unusual access and keep cookie controls available…

Account data

We may hold your registered phone number, verification result, sign-in history and account preferences. These details help us connect the right person to the right account step and reduce confusion during access checks.

Cookie controls

Cookies can remember a session and help the mobile route open the correct account area. Your browser settings can remove or block them, although some sign-in and preference functions may then need to be repeated.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us compare a payment event with your account. For bank transfer and virtual account activity, we use the reference and timestamp rather than wallet passwords.

Security checks

Phone verification comes before account access, while device and sign-in signals can help us spot an unfamiliar route. We may ask you to confirm account details before discussing private records or changing them.

Retention periods

We retain account, payment and support records for the time needed to provide account help, match transactions, protect access and meet applicable legal duties. When a record is no longer needed, our handling process removes or separates it.

Change requests

You can ask us to view or correct eligible information through the account privacy route. State the requested change and the account phone number; we verify ownership first, then explain what can be updated and why.

Privacy Policy Questions About atlas23

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an atlas23 account. We keep the wording practical: what we collect, why a payment reference appears, how cookies behave on your phone and where to send a request. If a question involves eligibility or account availability, the answer depends on local law.

The atlas23 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, wallet references, support messages and retention. It explains why we use each category, how we protect account access and how you can request a copy or correction where local law permits.

We collect the details needed for account creation and phone verification, along with sign-in and device information connected to access. If you use DANA, OVO, GoPay or QRIS, we may also receive a payment reference and status needed to match the account event.

DANA and QRIS appear because wallet activity creates records that need matching with your account. We may use a reference, status and timestamp to check a payment question. The same approach can apply to OVO, GoPay, bank transfer and virtual account activity.

Yes, you can send a data request through the account privacy route beside the cashier path. Include your registered phone number and say that you want a copy of your account data. We verify ownership first and explain any legal or security limits before responding.

Cookies can keep a sign-in session, remember a selected account area and support basic page preferences on your phone. You can block or delete them through your browser controls. If you do, some account steps may ask you to verify or choose preferences again.

We keep records for the period needed to match payments, protect account access, answer support requests and meet applicable legal duties. That period can differ by record type. When retention is no longer needed, we remove the record or separate it from direct account details.

Use the account privacy route and identify the field you want corrected, such as a phone number or account detail. Add the relevant payment reference only when the request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.