Reference

Privacy Policy for aki2 slot Accounts

aki2 slot Privacy Policy sets out how we collect, use, protect and remove details connected with your account, including payment status for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet status recordsPhone check detailsPolicy request path
aki2 slot Privacy Policy for aki2 slot Accounts
CONTACT PATHS

Ask About Your Privacy Policy

A clear contact request helps us locate the right record without asking you to send a wallet password or a full payment credential. When your question concerns the aki2 slot Privacy Policy, include the account contact detail you used, the subject of the request and any relevant date. We can then check access, correction, deletion or wallet-status questions through the same account help path used for login and cashier issues.

Team online

Account contact

Use the account help route when you want to ask how your phone verification, sign-in record or profile detail is handled. We may ask for a safe account identifier so we can separate your request from another account without requesting your DANA, OVO, GoPay or QRIS password.

Cashier record

For a Privacy Policy question about a payment reference, tell us whether it concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Share the reference and date only through the account contact path, and keep your wallet PIN and banking password private.

Access concern

If a sign-in or device event looks unfamiliar, contact us through account help and mention the affected time and device. We can review the security record, explain the next account step and help you protect access without asking for a password in a message.

DATA PRACTICES

What We Do With Your Details

We keep this Privacy Policy tied to actions you can recognise: opening an account, completing the phone check, moving from login to the lobby, checking a wallet status or asking for support.

Account details

We use the contact and verification details you submit to create, protect and maintain your account. A phone verification result can confirm that an account step was completed, while your profile remains separate from the private PIN or password used by your wallet or bank.

Cookies and sessions

Cookies and session signals help keep you signed in, remember a selected page and detect an unexpected change during access. You can manage browser cookie settings on your device, but restricting them may interrupt the account path or require another sign-in check.

Device security

We may record device type, browser details, approximate session timing and security events linked to access. These records help us investigate repeated login failures or unfamiliar activity. We do not need your device passcode, wallet PIN or bank password to perform that check.

Payment references

A payment record can contain a method label, reference, amount status and time needed to match a request. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to answer status questions, not to collect private wallet credentials.

Retention choices

We retain a record only while it supports the stated account, security, support or legal purpose, subject to applicable requirements. When you ask about removal, we check whether a record must remain for a valid reason, then explain what can be changed or deleted.

Request changes

You can ask us to correct an inaccurate account detail, explain a data use, provide access to applicable records or consider removal. Send the request through account help with enough detail to identify you safely; we may verify control before making a change.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and payment-record questions you may have before opening access. They also explain what we need from you when a request concerns a device, wallet reference or account detail. If your situation is not covered, use the contact path above and quote the relevant account step.

The aki2 slot Privacy Policy covers details supplied during account creation, phone verification, sign-in activity, support requests and payment status checks. It also explains cookies, device signals, retention, security handling and the way you can ask for access, correction or removal.

Phone verification helps connect an account request with the contact detail you supplied and can reduce mistaken or unauthorised access. We record the verification result and related security event, not your phone passcode. Account eligibility depends on local law.

No. Our Privacy Policy distinguishes a payment reference or status from your private credential. We may need the method, reference and timing for a DANA or QRIS check, but you should never send a wallet PIN, banking password or one-time security code.

The policy can cover device type, browser signals, session timing and security events connected with account access. These details help us investigate repeated login failures or an unfamiliar session. We do not need your device passcode to handle an access question.

Yes. Through the account help path, you can ask us to correct an inaccurate detail, explain a use, provide applicable records or consider removal. We may verify account control before acting, and some records may remain when a valid legal or security reason applies.

Retention depends on why the record exists and whether an applicable legal, accounting, security or support need requires it to remain. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference is not kept for an unrelated purpose.

Use the account contact route and state that your request concerns the Privacy Policy. Include your account contact detail, the record type and relevant date, while leaving out passwords and wallet PINs. We will explain the next verification or response step.