Reference

Privacy Policy For Your aku33 Account

Our Privacy Policy explains how aku33 handles the details linked to your account, including phone verification, device access and wallet activity.

Account clarityWallet data contextDevice accessPolicy contact path
aku33 Privacy Policy For Your aku33 Account
HELP WITH POLICY

Support Routes For Privacy Requests

A clear request reaches the right team faster when it includes your account phone number and the subject of your Privacy Policy question.

Account contact Use the support channel shown after account access and state that your request concerns the Privacy Policy. Include the phone number on your account, but do not send your password, wallet PIN or full payment credentials.
Cashier question If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer receipt, mention the transaction date and reference only. We can check the account-side record while the payment provider keeps its separate processing record.
Access assistance When login or phone verification stalls, use the same account support route and explain the device step that failed. We may ask for limited account details to locate the request, never for your password or wallet PIN.
HANDLING YOUR DETAILS

What We Do With Account Data

Privacy Policy choices should be practical, so we describe the handling points you meet in real use: account creation, phone verification, device login, cashier checks and support contact.

Account records

We use the details entered during account opening, including your phone number, to create and maintain your aku33 access. Phone verification helps connect a login request to the account record and can reduce confusion when more than one device is used.

Device signals

Login time, browser or device signals and security events can help us identify unusual access. These details support account protection; they are not a replacement for your own password care. We may ask you to verify account ownership before discussing them.

Cookies and storage

Cookies or similar browser storage can keep a session working and remember a necessary account setting. You can manage browser storage through your device settings, although removing it may require another login or affect the page state.

Wallet references

A cashier check may show a payment reference, method and status connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use the account-side reference to investigate status, while the payment rail may retain its own record.

Retention approach

We retain records only for the operational, security and legal purposes that apply to the account relationship. Retention can vary by record type and local requirements. Ask support which category your request concerns before requesting a change or removal.

Change requests

To request correction, access or deletion where available, contact us through the account support route and identify the relevant record. We may confirm your phone number or another account detail before acting, which helps prevent another person changing your data.

Privacy Policy Questions For aku33

These Privacy Policy answers address the questions you may have before opening an account or checking a wallet status. We keep the wording tied to the actual account path, including phone verification, device access and payment references. If your situation needs a record-level answer, contact support through the route available after login where local law permits.

The aku33 Privacy Policy covers account details, phone verification, login and device signals, cookies or browser storage, support messages and account-side payment references. It explains why we use those details for access, security and cashier checks, while a payment provider may handle separate records.

Phone verification helps us connect your account access request with the correct account record. It can also help support locate your request when login stalls. We do not need your password or wallet PIN for this step, and access depends on local law.

The Privacy Policy covers the account-side reference connected with a DANA or QRIS status check, such as a method, date or transaction reference. DANA and QRIS may retain separate processing records under their own terms, so their privacy handling is not replaced by our policy.

Use the support route shown after you access your account and state that you want a Privacy Policy data request. Identify the phone number on the account and the record category, such as login, cookie or cashier reference. We may verify ownership first.

Yes, you can contact support to ask about correcting an account detail where that option is available. Give the account phone number and describe the incorrect field without sending a password or wallet PIN. We review the request against the account record before making a change.

Retention depends on the type of record and the operational, security or legal reason for keeping it. Account, device and cashier records may therefore follow different periods. Contact support with the category you mean, and we can explain the applicable handling where local law permits.

You can use the account path from a supported phone or browser where local law permits. The Privacy Policy applies to the device signals, session storage and phone verification involved in that access. If a login step fails, contact support without sharing your password or wallet PIN.