Reference

Privacy Policy for Indonesia Accounts

aktoto explains which account details, device signals, and payment traces we keep, and why we keep them, so you know what happens from registration to support.

DANA, OVO, GoPay, QRISDevice logsAccount changesLocal-law only

Browse Lobby Read FAQ

What This Policy Covers

aktoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This policy covers the details we collect when you open an account, confirm your identity, contact support, or load wallet records. The rules can change by jurisdiction, so what we keep, share, or delete depends on local law and is available only where local law permits.

1
If you reach us from Medan or Semarang, we still treat the same core fields the same way: name, email, phone number, device data, login time, and transaction traces from DANA, OVO, GoPay, or QRIS are used only for login, security, and withdrawal checks. We use
2
that data to run the service, protect accounts, and answer requests sent through the account menu. If local law asks us to keep a record longer, we keep only the parts required and nothing extra.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REACH THE TEAM

How to Reach Our Team

For privacy questions, the fastest path is the in-account chat, followed by WhatsApp and the email form on our Help page. We answer every day from 09.00 to 23.

In-account chat Use the chat button after login for data correction, access questions, or a blocked-session check. We can see the account context right away, which shortens the verification step when you contact us from phone or desktop.

WhatsApp Send the same request through WhatsApp if chat is not open. Keep your registered number handy, because we match it with the account before we discuss any profile change or transaction record.

Email form The Help-page form is the right path for formal privacy requests, including data copies or deletion checks where local law allows. Add your username, registered email, and the date of your last login.

CONTROLLED ACCESS PATH

Data, Cookies, and Account Safety

We log the device, browser, and IP address that reach your account so we can spot unusual access and protect password resets.

Account data

We collect the name, email, phone number, and wallet or bank reference you submit during registration, verification, and support. We use it to keep login access tied to your own profile and to answer account questions.

Cookies on device

Cookies keep the session open, store language choice, and reduce repeated checks when you move between phone and desktop. You can clear them in your browser, but some saved settings will reset.

Security checks

When a login looks unusual, we compare device type, IP address, and last access time before we unlock the account. That extra check helps us stop unwanted access without asking you for the same details twice.

Retention period

We keep transaction logs, support chats, and verification records only for the time needed to serve your account, meet local law, and settle disputes. After that period, we archive or remove them under our internal schedule.

Change requests

If you want to correct your profile, send the request from the registered email or mobile number. We verify the request first, then update the field that you point out and confirm the result back to you.

Contact path

For privacy matters, start in the account menu or the Help page so we can see the right record faster. If the case needs more checks, we ask for a fresh message from the same contact channel.

Common Questions About Privacy Policy

Below are the questions we hear most about how we collect, use, and update account data. Each answer stays tied to local law, your registered details, and the request path inside the account menu. If your phone, browser, or wallet details change, send the update from the account menu so we can match the record and keep the process clear when you move between mobile and desktop.

We collect the name, email, phone number, device data, and wallet or bank reference you submit so we can create the account, verify access, and answer security checks. We do not use more than the service needs.

We keep the payment name and transaction reference inside your record when you use DANA, OVO, GoPay, or QRIS. That helps us match deposits, support requests, and account history, then retain the file only as long as local law requires.

Cookies remember language, session status, and recent login checks on your phone or desktop. They help us reduce repeated sign-ins, and you can clear them in the browser if you want a fresh session.

Yes. Send the request from your registered email or mobile number, then tell us which field changed. We verify the request against the account first, and then we update the record where local law allows.

Only the staff who need it for support, security, payment matching, or legal handling can access the record. We do not expose your profile publicly, and any sharing follows the same local-law limits that apply to your account.

If access is not permitted in your region, we block it and keep the policy limited to the places where it is allowed. The same rule applies to account checks, support requests, and data-change handling.

Privacy Policy for Indonesia Accounts

How to Reach Our Team

Data, Cookies, and Account Safety

Account data

Cookies on device

Security checks

Retention period

Change requests

Contact path

Common Questions About Privacy Policy

01 What data do you collect when I open an account?

02 Do you keep my DANA, OVO, GoPay, or QRIS details?

03 How do cookies work on my device?

04 Can I ask you to update my details?

05 Who can see my data?

06 What happens if local law does not permit access?

Related Pages