Reference

Privacy Policy for Your aurora555 Account

The aurora555 Privacy Policy explains how we handle the account, device and wallet details connected with your access to our lobby.

Account dataWallet detailsDevice accessCookie choices
aurora555 Privacy Policy for Your aurora555 Account
HELP WITH PRIVACY

Where To Ask About Your Data

A clear support route helps when a Privacy Policy question concerns your account rather than a general payment screen.

Account questions Use our account support route when you want to know what contact details, phone…
Wallet references For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, share the…
Policy requests Ask through the same support path if you want a copy of personal data…
DATA HANDLING

What We Do With Account Details

Your account details have a defined role in the Privacy Policy rather than an open-ended use. We handle information needed for account access, phone verification, security checks, support replies and payment-status matching.

Account creation

When you open an account, we collect the details needed to create your sign-in record and support phone verification. The Privacy Policy explains the purpose of each requested field, so you can distinguish account requirements from optional browser preferences before continuing.

Device signals

A mobile browser or desktop session may provide device and connection signals used to protect account access and investigate unusual sign-in activity. We describe that handling in the Privacy Policy; these signals are not a request for your device password or private files.

Cookie choices

Cookies can remember session settings and choices made on the site. You can manage available browser controls and ask support how a cookie category relates to your visit. Changing a preference may affect convenience, but it does not erase an account record automatically.

Payment matching

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may keep transaction references needed to match a wallet or cashier event. We do not need your wallet PIN to investigate a receipt or confirm which account action occurred.

Account protection

Phone verification and sign-in checks help us confirm that an account request comes from its owner. If you report an access problem, we may ask questions tied to your account history before changing details, which reduces the chance of an unauthorised change.

Retention requests

The Privacy Policy explains why certain records remain available and when they can be removed or amended. Contact us with the relevant account step, payment reference or cookie concern, and we can assess a deletion, correction or access request under applicable rules.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect from someone deciding whether to open an aurora555 account. They explain the practical link between account access, device behaviour, local wallets and data requests without replacing the full policy text. If your question concerns a particular receipt, phone number or sign-in event, use the support path with only the details needed to locate that record. Eligibility and access depend on local law.

The aurora555 Privacy Policy covers account creation, phone verification, sign-in activity, device signals, cookies, support contacts and payment references. It explains why we use each category, how retention works and how you can ask about access, correction or another data choice.

We use phone verification to help connect an account request with its owner and protect later access changes. The Privacy Policy describes the related record and purpose. If your phone detail is incorrect, contact support after keeping your account identifier ready.

Yes. The Privacy Policy explains that we may handle payment references or status details linked with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account steps. We use those references to match account activity, not to request your wallet PIN.

You can contact our support route to ask what personal data is linked with your aurora555 account. We may verify ownership before responding, then assess the request under applicable rules. Include a useful account identifier, but do not send your password.

The Privacy Policy explains that mobile or desktop sessions may provide device and connection signals for account protection and unusual sign-in checks. We do not need access to private files or your device password. Browser settings can also affect cookie preferences.

Send a correction request through support and identify the account field or payment reference that needs attention. We may ask for ownership checks before changing it. The Privacy Policy explains how we assess corrections and whether a record must remain for a stated purpose.

Yes. Access, eligibility and some data requests depend on local law. We apply the Privacy Policy to the relevant account context and explain any required limits through support. You can still ask us to clarify which rule or purpose affects your request.