Reference

Open aksa168 Privacy Policy For Wallet Data

Our Privacy Policy explains how we handle the details you provide when you create an account, verify your phone, enter the lobby or use DANA, OVO, GoPay and…

Account clarityWallet dataDevice choicesPolicy requests
aksa168 Open aksa168 Privacy Policy For Wallet Data
REQUEST HELP

Ask Support About Privacy Requests

A direct support route helps you deal with a privacy question before it becomes an account problem.

Account privacy request Send a request through the account support path when you want to ask what…
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact us with the…
Device access concern Use support when a mobile browser or desktop session remains connected after you leave…
DATA PRACTICE

Check How aksa168 Handles Your Data

We keep the Privacy Policy practical by tying each data category to a clear use. Phone verification supports account access, device details help us identify unusual sessions, and…

Account details

We use the account details you submit to create your profile, complete the clear phone verification step and connect policy…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be stored beside a transaction record.

Cookies and sessions

Cookies can preserve a login session or a language and device preference when you move between the lobby and account…

Mobile and desktop

We may record device and browser signals when you open the account on mobile or desktop.

Retention choices

We keep personal records for the time needed to operate the account, check a payment reference, protect access or meet…

Change or deletion

Ask us to correct, export or remove eligible personal details through support.

Find Privacy Policy Answers For aksa168

These Privacy Policy answers cover the account and wallet questions you are most likely to ask before opening aksa168. Each answer points to a specific action, from checking a stored payment reference to requesting a correction. If your case involves an unusual device session or a local access question, use the support path and include only the details needed to identify your account.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and your available data requests.

Phone verification helps us connect your account to the person completing the account step and helps support identify the correct record. We use the verification status for account security, not as permission to request your wallet PIN or full payment password.

The Privacy Policy allows us to keep transaction references and status details needed to match a DANA or QRIS payment to your account. We do not ask you to place a wallet PIN or full payment credential in a support request.

Contact support through your account path and state which record needs correction, such as a phone detail, device session or payment reference. Include the verified account phone number when asked, but leave out passwords, PINs and complete wallet credentials.

We keep account, device and transaction records only while they serve an operating, security or legal purpose. After that purpose ends, we remove or anonymise the record. A support reply can explain the retention reason for a specific request.

You can send a deletion request through support and identify the account record involved. We first confirm ownership and then assess whether a record must remain for security, payment matching or a legal requirement. Access depends on local law.

The Privacy Policy applies to your account activity in Indonesia where local law permits, including a mobile session in Denpasar or a desktop session elsewhere. Eligibility and account access depend on local law, so support can clarify a location-specific request.