Reference

alpatoto Privacy Policy for Your Account

Your alpatoto Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextPhone verification detailPolicy contact route
alpatoto alpatoto Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact route helps when you want to ask about personal data rather than wallet status alone. From Semarang or elsewhere in Indonesia, use the support path shown in your account or the contact route linked from this policy. Tell us which account step, device or payment reference your question concerns so we can locate the right record without asking for unnecessary details.

Team online

Policy questions

Ask what data we hold, why it is used or which retention rule applies. Include your account phone number only through the secure contact path shown on alpatoto, not in a public message.

Access requests

Request a copy, correction or removal review through account support. We may verify the phone linked to your account before changing personal records or releasing account-related data.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the relevant transaction reference privately. We separate payment-provider records from the account details we control.

HANDLING YOUR DATA

How alpatoto Applies This Policy

We apply this Privacy Policy to practical account events, not just page visits. A phone check can confirm that the person requesting access controls the account, while device and session signals help…

Account records

We may hold your phone-linked account details, verification state and sign-in history so we can return you to the correct account after you leave the lobby or change devices.

Device signals

Browser type, device details and session timing can support fraud checks and account recovery. These signals help us distinguish a normal mobile login from an unfamiliar access attempt.

Cookies

Cookies and similar browser storage can remember session choices and help the policy page load as expected. You can adjust browser settings, although some account functions may then need another sign-in.

Wallet records

When you use QRIS or a local wallet, we may retain a reference, status and amount needed for account reconciliation. DANA, OVO and GoPay may separately retain their own transaction records.

Retention

We keep records only for the period connected to account operation, dispute handling, security checks or a legal requirement. When a purpose ends, deletion or restricted access may follow our retention process.

Change requests

To correct, access or ask about deletion of your personal data, contact us through the route linked to this Privacy Policy. We may request phone verification before acting on an account request.

Privacy Policy Questions Answered

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. They explain what we collect, how we connect records to your account and how to contact us from an Indonesian device. If your situation is unusual, use the policy contact route and describe the specific record or account step.

It covers account details, phone verification, sign-in history, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm account control before access or a data request is completed. It also helps us investigate an unfamiliar login without relying only on a device or browser signal.

Yes. The Privacy Policy explains our handling of QRIS, DANA, OVO and GoPay references, status details and reconciliation records. Each payment provider may also keep separate data under its own terms.

Use the contact route linked from this Privacy Policy and describe the records you want to access. We may verify the phone connected to your account before preparing or sending account data.

Yes. Send a correction request through account support, identify the inaccurate field and explain the change. We may ask for account verification so a third party cannot alter your records.

Retention depends on the purpose of the record, account security needs, dispute handling and legal requirements. Payment providers may retain their own records separately from the data we control.

Yes. It applies when you access the lobby from a phone or tablet, including device signals, browser storage and session data. Cookie settings or a changed device may require another account sign-in.