Reference

akasia899 Privacy Policy For Your Account

Our akasia899 Privacy Policy explains what account, device and wallet details we collect when you open an account, sign in and use the lobby.

Account dataWallet recordsCookie choicesPhone verification
akasia899 akasia899 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Cashier Path

A clear contact route helps you question a record without sending unnecessary details.

Account access If your phone verification or sign-in record looks wrong, contact support from the account…
Wallet status For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate…
Privacy request To request a copy, correction or deletion assessment, state the exact account detail involved…
DATA HANDLING

What Our Privacy Controls Cover

Your privacy choices are connected to ordinary account actions, so we explain them in practical terms.

Collected details

We may record your phone number, account identifier, sign-in time, device type, browser signals and verification result.

Cookie settings

Cookies can remember a session, language choice or security state on the device you use for the lobby.

Account security

We use phone verification and sign-in checks to reduce the chance of another person entering your account.

Retention period

We keep account, verification and payment-reference records only for the service, safety and legal purposes described in this Privacy Policy.

Request changes

You can ask us to correct inaccurate account details or assess a deletion request through the privacy contact route.

Who can ask

We respond to the account holder or an authorised representative after an identity check.

Privacy Policy Answers For Indonesia

These answers address the privacy searches we hear most often before an account is opened or a wallet record is queried. They cover the data connected to phone verification, device use, cookies, payment references and account requests. If your question concerns a specific DANA, OVO, GoPay or QRIS event, include its reference through the support path so we can check the relevant record. Availability depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, payment references and privacy requests. It also explains why we use each category, how long records may remain, how security checks work and how you can ask for access or correction.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a payment-status question with the correct account event, and we do not ask for your wallet PIN.

Phone verification helps us confirm that the person opening or entering an account controls the linked number. It also supports privacy requests, because we need to avoid giving account details or changing records after an unverified message.

We may record device type, browser signals, sign-in time and security-related identifiers. These details help recognise a session and investigate an unfamiliar account event. You can clear browser data, but a later sign-in may require another verification step.

Use the available support channel from your account and identify the field you believe is wrong. Include your linked phone number and a short explanation. We confirm the request before changing a record, and we may ask for an additional account step.

You can submit a deletion request through the privacy contact route. We assess which records can be removed and whether a payment reference, security record or legal duty requires temporary retention. We explain the result and any limit that applies.

Access is limited to people handling account support, payment-status checks, security work or related legal duties. A support contact must pass an identity check before we discuss private records, and we do not treat an unverified message as authority to disclose them.