Reference

ace555 Privacy Policy for Your Account

Our ace555 Privacy Policy explains what account details we collect, why we use them, and how you can ask us to correct or remove eligible data.

Account dataWallet recordsCookie choicesRequest support
ace555 ace555 Privacy Policy for Your Account
CONTACT PATHS

Where to Ask About Privacy Policy

A clear contact route matters when you want to understand a record rather than change a game setting. Our support path lets you ask about the ace555 Privacy Policy, identify the account data linked to your phone, or report a wallet reference that looks unfamiliar. Use the account support panel after login when possible, because the verified session helps us locate your request without exposing details in an open message.

Team online

Account support panel

Open the support panel from your logged-in account and select the privacy request path. Include your registered phone details and the question you want answered. We use the verified session to connect your request with the correct ace555 account record.

Cashier record check

If your privacy question concerns DANA, OVO, GoPay, QRIS or a bank transfer, add the receipt or transaction reference only. We can check the stored status without asking you to send a wallet PIN, password or full payment credential.

Data request route

For access, correction or deletion questions under the Privacy Policy, send a request through the account contact route. Tell us which data category you mean, such as phone verification, cookie history or payment reference, so our team can follow the right check.

HANDLING DETAILS

What We Do With Your Account Data

We keep this policy practical by describing the account events that create records and the controls around them.

Login records

We record account access details needed to identify a login session and investigate unusual activity. A new phone or browser may create a fresh security check. This helps us distinguish your normal mobile path from an access attempt that needs attention.

Phone verification

Your verified phone number connects the account step with the person requesting access. We use it for account checks and privacy requests, not as a reason to ask for your wallet PIN. Keep the number current so a correction request can be matched safely.

Cookie controls

Cookies can remember a device path, session choice or page preference. You can manage cookies through your browser settings, although removing them may require another login or make the lobby reopen without saved preferences. The Privacy Policy explains why these small files are used.

Wallet references

DANA, OVO, GoPay and QRIS activity may leave a reference, amount status and time record beside the account event. Bank transfer and virtual account records follow the same matching purpose. We use these details to reconcile status, not to collect your private wallet password.

Retention checks

We keep account and transaction records only for the period needed for account administration, security checks, dispute handling and legal duties that apply where local law permits. When a record is no longer needed for those purposes, our handling process moves it toward deletion or anonymisation.

Change requests

You can ask us to correct inaccurate account data or explain the basis for a stored record. Include your registered phone, the relevant category and a short reason. We may verify ownership before making a change, so another person cannot alter your ace555 profile.

Privacy Policy Answers for ace555 Accounts

These Privacy Policy answers focus on the questions you are most likely to have before opening or using an account. We cover the records created by login, phone checks, cookies and local wallet activity, along with the route for asking us to explain, correct or remove eligible data. Access and eligibility depend on local law.

The ace555 Privacy Policy covers account details, phone verification, login sessions, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records and how you can request access or correction.

We use your phone number to create and verify the account path, connect you with the correct login session and check ownership when you send a Privacy Policy request. We do not need your wallet PIN for this process. Keep the number current so account checks can reach you.

Yes. The Privacy Policy includes transaction references, status details and timestamps connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. These records help us match a cashier event with your account and investigate a status question without requesting private wallet credentials.

Open the logged-in account support panel and choose the data request route. State that you want a copy under the ace555 Privacy Policy, name the categories involved and provide your registered phone details. We may complete an ownership check before discussing or sending personal account records.

Yes. Send a correction request through the account contact path and identify the inaccurate field, such as a phone detail or payment reference. Explain the change briefly and attach only the relevant receipt reference. We verify the account before updating records covered by the Privacy Policy.

Cookies can keep a login session, device preference or page choice available while you move between account pages and the lobby. You can clear or restrict them in your mobile browser. After that, ace555 may ask you to log in again, and some saved path settings may disappear.

You can ask us to delete eligible personal data through the Privacy Policy contact route. Tell us which category you mean and confirm the registered account details. Some account, security or transaction records may need to remain for legal duties or dispute checks where local law permits.