Reference

aquaslot Privacy Policy For Your Account

aquaslot Privacy Policy explains what we collect when you create an account, complete phone verification, use the mobile lobby, or check DANA and QRIS status.

PHONE VERIFICATIONCOOKIE CHOICESDANA + QRIS
aquaslot aquaslot Privacy Policy For Your Account
PRIVATE HELP ROUTE

Wallet Status Privacy Support Path

A clear support route matters when a privacy request and a wallet reference meet in the same account. We ask you to contact us from the account area where possible, so we can connect your request to the correct phone verification record without asking you to send a wallet password. Include the subject, account contact, and relevant DANA, OVO, GoPay, or QRIS reference, while hiding security codes and full credentials.

Team online

ACCOUNT REQUEST

Use the account support path to ask which personal details we hold, why a phone verification record is connected to your profile, or how to correct an entry. We may ask for account checks before releasing private details.

PAYMENT REFERENCE

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, send the transaction reference and date rather than wallet credentials. This lets us check status while limiting the sensitive material included in your message.

ACCESS CONCERN

If a login alert, device change, or phone verification issue concerns you, tell us which account path you used and when it happened. We can review the security event and explain the privacy steps available to you.

HANDLING DETAILS

How Privacy Works With Mobile Login

We keep this Privacy Policy practical by linking each data use to an account action you can recognise: opening the mobile lobby, checking a wallet status, or requesting help.

DATA COLLECTION

We may receive account contact details, phone verification results, device and browser signals, session events, support messages, and payment references. We collect these details when you create an account, sign in, use the lobby, or ask us to investigate a request.

COOKIE CONTROL

Cookies can keep a selected setting, support secure session continuity, and help us understand whether a page works correctly. Where a choice is available, you can adjust non-essential cookie preferences without sending us your DANA, OVO, GoPay, or QRIS credentials.

ACCOUNT SECURITY

Phone verification and session checks help us distinguish an authorised account path from an unusual device or login event. We do not ask for your wallet password in a privacy request, and you should never place one in a support message.

RETENTION PERIOD

We keep account, security, support, and payment-reference records for the period needed to operate the requested service, resolve disputes, protect the account, or meet an applicable legal duty. When a record is no longer needed, we remove or securely de-identify it.

YOUR CORRECTION

You can ask us to correct an inaccurate contact detail, clarify a data use, or request deletion where the law allows. Include enough account context for us to locate the record, but remove passwords, one-time codes, and complete wallet credentials before sending.

POLICY CONTACT

For a Privacy Policy question, contact support through the account route and state whether your request concerns access, correction, deletion, cookies, or a payment reference. We may verify account ownership first so private details are not disclosed to the wrong person.

Privacy Policy Questions About Your Account

These answers focus on the questions you may have before opening an aquaslot account or using the Indonesia wallet path. They explain what the Privacy Policy covers, how a request is checked, and which details are useful when you contact us. If your situation is not listed, use the account support route and describe the specific record or privacy choice you want us to examine.

The aquaslot Privacy Policy covers account contact details, phone verification, device and session signals, cookie choices, support messages, and payment references. It explains why we use those details for account access, security, service requests, dispute handling, and applicable legal duties.

We do not need your DANA or QRIS password for a privacy request or payment-status check. We use the reference and status needed to connect a request to your account. Never include a wallet password, one-time code, or complete credential in support correspondence.

Use the account support path and ask for an access request under the Privacy Policy. State the account contact and the type of record you want located, such as phone verification, cookie choice, login event, or payment reference. We may verify ownership first.

Yes, you can ask us to correct an inaccurate eligible detail through support. Tell us what appears wrong and what should replace it, without sending passwords or wallet credentials. We may request account checks before changing a contact or verification record.

The retention period depends on why the record exists. We keep details for the time needed for account operation, security checks, support handling, disputes, or an applicable legal duty. When that need ends, we remove or securely de-identify the record.

You can submit a deletion request through the account support route, and we will assess which records can be removed. Some details may need to remain for security, dispute handling, or legal duties. Access to the service depends on local law and the request outcome.

Cookies may remember essential session settings and help us measure page performance where that choice is available. You can adjust non-essential preferences through the displayed cookie control. Changing browser settings may affect your mobile login path or require you to sign in again.