Reference

Privacy Policy For Your aria33 Account

aria33 Privacy Policy explains how we handle your account details, device signals, cookies and payment references while you use the site.

Account dataWallet referencesCookie choicesPhone verification

Explore Our Lobby Read FAQ

How Privacy Works Around Your Wallet

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

Our Privacy Policy covers data you provide when opening an account, confirming your phone number, signing in, contacting support or checking a wallet status. We may record account identifiers, login events, device and browser details, cookie preferences, transaction references and security signals needed to protect access.

1
For DANA, OVO, GoPay and QRIS, we use the payment reference and status supplied through the cashier flow so we can match your request without asking for an unnecessary wallet password. Bank transfer and virtual account references can also appear in account records. We retain records
2
for the period needed for security, support, dispute handling and applicable legal duties. Where access is discussed, it depends on local law. You can ask us to clarify a record or request a correction through the account support path.

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

HELP WITH PRIVACY

Get Clear Answers About Your Records

A clear contact route helps when a privacy question appears beside a login or wallet-status issue.

DATA HANDLING

What We Do With Account Data

Privacy is easier to assess when each data use has a clear purpose. We separate account access records, payment references, device signals and cookie choices so a support question does not require…

Account details

We use the details you enter for account creation, phone verification, sign-in support and account-related messages. We do not need your DANA, OVO or GoPay PIN to connect a wallet status with your account.

Device signals

Browser type, device details, session times and related security signals can help us recognise unusual access. On mobile, these records support the path from login to the lobby without requiring a separate installed application.

Cookies

Cookies can remember sign-in conditions, basic preferences and security settings. You can manage cookie behaviour through your browser controls, although restricting necessary cookies may affect account access or the way privacy choices are saved.

Payment records

A DANA, QRIS, bank transfer or virtual account reference may be retained to match a cashier request, investigate a status question and resolve a payment dispute. The record is used for that operational purpose, not as a wallet password.

Retention periods

We keep account, security and transaction records only for the period needed for access protection, support, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our handling follows the relevant deletion process.

Your requests

You can ask what account data we hold, request a correction or ask us to clarify how a record was used through the signed-in support path. Where local law permits, we may verify your phone before acting on a private-data request.

Answers Before You Open An Account

These Privacy Policy answers focus on the questions you may have before opening an aria33 account from Indonesia. We explain the records connected to phone verification, mobile access, cookies and local wallet references in plain terms. If your situation is not covered, use the support contact shown in your account area and point us to the specific record or access step you want us to check.

It covers account details, phone verification, sign-in events, device and browser signals, cookie choices, support requests and payment references. It also explains why we retain certain records and how you can request access or correction where local law permits.

We collect the details needed to create and secure your account, including the phone verification step and sign-in records. We may also record device information and session activity so we can identify unusual access and respond to an account question.

We do not need your wallet PIN for the cashier flow. We may receive a payment reference, status or time connected with DANA, OVO or GoPay so we can match the transaction and answer a wallet-status question.

A QRIS, bank transfer or virtual account reference can be attached to your account record for matching, support and dispute handling. We use the visible reference and status, not your banking password or wallet credential, when checking that payment path.

Yes. Use the support contact shown inside your signed-in account and specify whether you want access to a record or a correction. We may ask for phone verification before discussing private data, and the request depends on local law.

Cookies can retain necessary sign-in conditions, security settings and privacy choices on your browser. If you block them, the mobile path from login to the lobby may require extra checks or some account functions may not work as intended.

Contact us through the support path shown in your account area and mention the session time, device type or account step you recognise. Do not send a wallet PIN. We may use phone verification to confirm the request before discussing access records.

Privacy Policy For Your aria33 Account

Get Clear Answers About Your Records

What We Do With Account Data

Account details

Device signals

Cookies

Payment records

Retention periods

Your requests

Answers Before You Open An Account

01 What does the aria33 Privacy Policy cover?

02 What data do you collect when I open an account?

03 Does aria33 store my DANA, OVO or GoPay PIN?

04 How are QRIS and bank transfer records handled?

05 Can I request a copy or correction of my aria33 data?

06 How do cookies affect mobile access to aria33?

07 Where can I ask about an unfamiliar account session?

Related Pages