Reference

amperaslot Privacy Policy For Your Account Data

Our Privacy Policy shows what we collect when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS, plus how we use those details…

Account choicesWallet detailsDevice accessPolicy requests
amperaslot amperaslot Privacy Policy For Your Account Data
PRIVATE HELP PATHS

Get Account Privacy Help Beside Wallet Support

A direct support route helps you ask about a record without sending sensitive credentials in an open message. From your account support area, tell us whether your question concerns phone verification, a DANA receipt, QRIS status or a device sign-in. We use the details you provide to locate the relevant record and keep the request tied to your account.

Team online

Account support area

Open the support path after signing in and describe your Privacy Policy question. Include the account phone number or transaction reference, but never send a password, wallet PIN or one-time verification code.

Wallet status request

For DANA, OVO, GoPay or QRIS questions, share the visible receipt reference and date. We can compare that record with the account event without asking you to disclose private wallet credentials.

Access clarification

If a device sign-in or phone check is blocked, describe the screen message through account support. We may ask for a verification step so we discuss the correct account without exposing another person’s data.

HANDLING YOUR RECORDS

Privacy Choices For Mobile And Account Security

We keep this Privacy Policy practical by linking each data practice to a visible account action.

Account data

We use details such as your phone number, account settings and verification state to maintain your sign-in path. We do not need your DANA, OVO, GoPay or QRIS wallet PIN to match a payment record.

Cookies and browsers

Cookies can remember a session, support security checks and keep account choices available on your device. If you block them, the lobby may ask you to sign in again or repeat a verification step.

Device signals

We may record browser type, device details, approximate network data and sign-in events to identify unusual access. These signals help us protect your account without treating them as wallet credentials.

Security checks

Phone verification is required before account access, and a new device may trigger another check. Keep your password private and contact account support if a sign-in event does not look familiar.

Retention choices

We retain account, payment and support records only while they serve security, reconciliation, dispute handling or legal needs. When a record is no longer required, we remove it or use a form that does not identify you.

Changes and requests

Ask us to access, correct or clarify your personal data through account support. State the request clearly, and we may confirm your identity before changing a phone number or releasing account records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy questions address the account actions you are most likely to check before opening an account. We cover wallet references, mobile browsing, phone verification, cookies, retention and requests for access or correction, with the same account support path used for policy help.

The amperaslot Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to confirm identity before account access and to connect a support request with the correct account. We may ask for another check when a new device or unusual sign-in appears.

No. Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS wallet PIN. We may receive a transaction reference, amount or status so we can match a payment event to your account.

We may collect browser type, device details, approximate network data and sign-in events. We use these signals for account security and session handling, not as a substitute for your password or wallet credentials.

Cookies can keep a session active and support security checks. If you restrict them in your browser, you may need to sign in again or repeat phone verification, while your policy rights remain available through account support.

Yes. Send a correction request through the account support area and identify the field that needs changing. We may confirm your identity before changing phone details or disclosing records connected with your account.

We keep records while they support account security, payment matching, dispute handling or legal duties. After that need ends, we remove or anonymise them, subject to any retention duty that depends on local law.