Reference

Privacy Policy For Your Wallet Data

api123 Privacy Policy explains what we collect when you open an account, use the mobile browser, verify your phone, or connect DANA, OVO, GoPay and QRIS.

Phone verificationWallet detailsMobile browserPolicy access
Browse Our Lobby Read FAQ
api123 Privacy Policy For Your Wallet Data
ACCOUNT ASSISTANCE

Get Policy Help Through Your Account

A direct support route helps when you want to ask what a field means, correct a contact detail, or check a wallet reference connected with your account. Sign in through the mobile browser or desktop browser, open the account support area, and include the email or phone detail used for verification. If you are in Medan or elsewhere in Indonesia, the same request path applies; access depends on local law.

Team online

Data access request

Ask us to identify the personal data connected with your api123 account. Include your verified phone detail and the subject of the request so our account support team can locate the correct record.

Correction request

If your contact detail or account label needs changing, send the requested correction through account support. We may ask for phone verification before changing information that affects login or wallet matching.

Payment record query

For a DANA, QRIS, OVO, GoPay, bank transfer, or virtual account reference, attach the receipt number rather than your wallet password. We use the reference to check status without requesting unrelated account content.

HANDLING DETAILS

Your Data Choices On api123

We keep privacy decisions practical: you can ask what we hold, why it is used, and which account step created it.

Account data

Registration and phone verification details help us recognise your account and reduce mistaken access. We use the contact route you provide for account messages and policy requests, not for unrelated identity collection.

Wallet matching

DANA, OVO, GoPay and QRIS references are used to match a payment status with the correct account action. Bank and virtual account references serve the same reconciliation purpose without exposing your wallet password.

Browser cookies

Cookies can preserve a login session, remember a language choice, or show us which policy page was opened. You can restrict cookies in your mobile or desktop browser, although some account steps may then need repeating.

Security checks

We examine login signals, device details, and unusual account activity to protect access. If a request affects your account or payment record, we may repeat phone verification before making a change.

Retention approach

We keep account, payment-status, and support records only while they serve account operation, security, dispute handling, or legal duties. When a record no longer has that purpose, we remove it or separate it from your identity.

Your request route

Use account support to request access, correction, deletion, or a copy where local law permits. Describe the request clearly and include your verified contact detail so we can respond about the right account.

Privacy Policy Questions Before Registration

These Privacy Policy answers focus on the account decisions you are most likely to make before registration or while using the lobby. We explain wallet references, browser cookies, phone verification, retention, and request handling in plain language. If your question concerns a specific record, use the account support path with the contact detail used for api123 access.

The api123 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment-status references. It explains how we use those records for access, security, wallet matching, replies, and legal duties, with handling depending on local law.

Our Privacy Policy concerns the payment status and reference needed to match your account action. We do not need your DANA, OVO, GoPay, or QRIS wallet password for that purpose. Keep wallet credentials inside the relevant payment service and never send them through support.

Phone verification helps us connect an account request to the correct account and reduce mistaken access. The Privacy Policy treats the verification record as account-security data. We may ask for it again before changing contact details or handling a sensitive data request.

Open account support from the mobile or desktop browser and state whether you want access, a copy, or a correction. Include the verified phone detail used for registration. Where local law permits, we will use that request to locate and assess the relevant record.

The Privacy Policy does not use one fixed period for every record. We keep information while it supports account operation, security, payment reconciliation, dispute handling, or legal duties. When the purpose ends, we remove the record or separate it from your identity.

Yes. Your mobile or desktop browser normally provides cookie controls, and you can restrict or clear stored cookies there. Our Privacy Policy explains that some session or account steps may need repeating after restriction, because the browser may no longer remember that state.

Use the support area inside your api123 account and describe the Privacy Policy request, such as access, correction, deletion, or payment-record clarification. Include your verified contact detail and receipt reference when relevant. Service access remains subject to local law.

Related Pages

api123 Indonesia Access guide About Us api123 Casino FAQ