Reference

akun demo Privacy Policy For Your Account

akun demo Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account dataWallet referencesCookie choicesAccess requests
akun demo akun demo Privacy Policy For Your Account
HELP WITH DATA

Get Privacy Policy Help Near Login

A clear contact route matters when a privacy question appears beside an account or wallet status.

Account data questions Ask us to explain the account details linked to your login, including the phone…
Wallet reference checks If a DANA, OVO, GoPay or QRIS reference appears beside your account, contact support…
Policy change requests Use the account help path to request a correction, ask about retention, or question…
HANDLING DETAILS

What We Do With Your Privacy Choices

We keep the policy practical by describing the points where information enters the account flow: phone verification, device access, cookie selection and payment status checks.

Data we receive

We may receive your account contact details, phone verification result, sign-in device signals and payment references.

Cookie controls

Cookies can remember choices made on the privacy page or help keep a sign-in session connected to the correct account.

Account protection

Phone verification helps us check account access before we discuss personal records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can show whether a payment status belongs to your account.

Retention questions

Some records remain available for account protection, payment reconciliation or legal requirements described by this policy.

Requesting a change

You can ask us to correct account details or explain how a record is used through support.

Privacy Policy Answers For akun demo

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain account records, phone checks, cookies, wallet references, device access and requests for correction in plain English. If your question concerns a record not listed here, use the support path with the account contact connected to your login.

It covers account details, phone verification, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how retention questions work and how you can request access or correction.

No. Our policy describes payment references and status details, not your DANA, OVO, GoPay or QRIS wallet PIN. When you ask about a receipt or pending status, send the reference and date shown in your account rather than private wallet credentials.

Phone verification helps us connect an account access request with the correct account and reduce mistaken disclosure of personal records. We may use the verification result when you ask about login details, a cookie choice, or a payment reference shown beside your account.

Cookies may remember your policy choice or keep a browser session associated with the correct account. You can change cookie controls in your browser. If you remove them, the page may ask you to select preferences again or repeat a login step.

Yes, you can contact support through the account help path and identify the field that needs correction. We verify that the request is connected to you before responding. We will explain if a record must remain unchanged for payment reconciliation or legal reasons.

Yes. The policy applies when you sign in from a mobile browser or desktop device. Technical session details may differ by device, while the account connection remains the same. Access to the lobby and related records depends on local law and where local law permits.

Send support the account contact, payment rail and reference visible on your receipt, such as QRIS, DANA or bank transfer. Do not include a PIN. We will explain what the record supports, why it remains available and whether a correction request can be made.