Reference

angkasa 168 Privacy Policy For Your Account

Your account details, wallet checks and device sessions are covered in the angkasa 168 Privacy Policy, so you can see what we collect before opening an account.

Clear data purposesWallet reference checksCookie choicesAccount access rights
angkasa 168 angkasa 168 Privacy Policy For Your Account
CONTACT DATA CARE

Ask Us About Privacy Policy Requests

A direct account support path helps when you want to ask about stored data, cookies or a wallet reference linked to your profile.

Account data request Tell us which account detail you want checked, such as your phone number, login email or verification record. We may ask for an account step to confirm that the request comes from you.
Wallet reference query For DANA, OVO, GoPay, QRIS or bank transfer questions, share the payment reference and date rather than a wallet password. We use those details to locate the matching account record.
Access and cookie help If a cookie choice or device session affects your account path, contact us through account support. Include your device type and browser so we can trace the relevant session without requesting private credentials.
HOW DATA IS HANDLED

Browse Your Privacy Controls With Clarity

We handle account data according to the purpose that brought it into our systems, with extra care around phone verification, wallet references and login sessions.

Account data

We may use your name, contact detail, phone verification result and account activity to provide access, answer requests and protect the profile from unusual login behaviour.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer records may include reference codes, status details and timestamps used to reconcile account activity.

Cookies

Cookies can remember session settings and help us recognise a returning device. You can manage browser cookie controls, although changing them may affect account access or saved preferences.

Account security

Phone verification, login records and device signals help us examine suspicious access. We may pause a sensitive account action until the requested identity check is completed.

Retention

We retain selected account, payment and support records only for operational, security or legal purposes. Retention length can depend on the record type and local legal requirements.

Change requests

To correct or question your data, contact account support with the relevant account detail. We confirm ownership first, then explain the available action and any legal reason for keeping a record.

Find Answers About Privacy Policy

These Privacy Policy answers address the account, wallet and device questions you may search before joining angkasa 168. We keep each answer practical: what data is involved, why a check appears, which request path to use and how local law can affect access or retention.

It covers account details, phone verification, login sessions, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity.

Phone verification helps connect the account to the correct contact detail and assists with security checks. We may request it before account access or a sensitive profile action where local law permits.

Yes. The Privacy Policy covers payment references, status results and timestamps used to match DANA, QRIS, OVO, GoPay and other listed payment activity with your account.

Contact us through the account support channel and identify the data you want checked. We may confirm your phone or email detail before responding, so another person cannot request changes to your profile.

Cookies can remember session settings and support device security on a mobile browser. You can adjust browser controls, but removing required cookies may interrupt login or return you to an earlier account step.

Retention depends on the record and its operational, security or legal purpose. Account and payment records may remain while a related duty or account matter requires them, where local law permits.

Yes. Your location does not prevent a privacy request. Send the account detail, device path or payment reference involved through support; access and any response depend on local law.