Reference

Privacy Policy for Your Account

We keep account data, wallet references, and device logs in one clear policy, so you can see what stays on record before you open an account.

Data useCookie controlWallet tracesLocal law
akaitoto Privacy Policy for Your Account
REQUEST CHANNELS

Where to Send Privacy Requests

If you want access, correction, or closure checks, send the request from the email on file and include your account ID. That lets us match the right record before anyone sees private data. Our live chat stays open 24/7, email remains in the same ticket queue, and WhatsApp is there for follow-up when the same number is already linked.

Team online

Live Chat

Use the chat button in your account and start with your registered email, account ID, and the privacy request type. Live replies stay open 24/7, and the same ticket follows up by email if we need documents.

Email Desk

Send a message to the address in our footer when you want a copy, correction, or closure check. We answer most requests the same day, then confirm the next step in writing so you can track it.

WhatsApp Follow-up

If WhatsApp is easier, send the same registered number and the privacy question in one message. We use it for follow-up only, so your request stays tied to the original ticket and does not get mixed up.

HANDLING AND RETENTION

How We Protect Your Records

Our privacy handling starts with the data you give at registration and ends with a simple request path if you want a copy or correction.

Access control

We compare the login record, session token, and device details to spot odd sign-ins. If your phone or browser changes, we may ask you to confirm the email on file before the account opens again.

Cookie settings

Essential cookies keep your session alive, remember language choice, and prevent repeated logins. If you clear them in Chrome, Safari, or a mobile browser, the next visit starts fresh and your saved session ends.

Payment traces

When you use DANA, OVO, GoPay, or QRIS, we keep the reference ID, time, and status so we can match the record to your account. We do not store your wallet PIN or login secret.

Retention windows

Records stay only for the period needed for account work, dispute checks, or legal duty. After that window, we delete or anonymise the parts that no longer need to identify you.

Change requests

To update a field, send the request from the email on file, say exactly what should change, and attach a clear screenshot or document when asked. That step helps us stop the wrong person from editing your profile.

Support trail

If you spot an unknown login, contact chat at once and include the time, device, and last screen you saw. We can freeze the session while we check the record and recover access.

Questions About Your Data

These are the questions people send before they open an account or after they change phones. We answer them in plain English, using the same steps every time: confirm identity, check the record, explain what we keep, and show how to request changes. If local law limits a request, we say that directly and stop the process there.

We take the name, contact details, login history, device signals, and any payment reference needed to match DANA, OVO, GoPay, or QRIS activity. We use it for access checks, record matching, and session safety.

We keep the transaction reference, time, and status, not your wallet PIN or secret code. That lets us trace the account record when you ask about a payment or a correction.

Essential cookies keep you signed in, remember language choice, and reduce repeated checks. If you clear cookies in Chrome, Safari, or another mobile browser, the next visit starts with a fresh session.

Send the request from the email tied to your account, name the exact field, and attach a screenshot or document if we ask for one. We use that step to stop unauthorised edits.

We keep records only for the period needed for account work, dispute handling, and legal duty. After that, we remove or anonymise what no longer needs to identify you.

Use live chat right away and tell us the time, device, and screen you last saw. We can lock the session, check the record, and help you recover access safely.

Yes. When local law sets a different rule, we follow that rule and only process the request where it is allowed. If we cannot act, we explain the reason and keep the rest secure.