Reference

api166 Privacy Policy for Your Account

Our Privacy Policy explains what api166 collects when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet contextPolicy accessLocal-law basis
Browse Our Lobby Read FAQ
api166 api166 Privacy Policy for Your Account
CONTACT YOUR WAY

Ask About Privacy Through Account Support

A clear contact path matters when your account record or wallet reference does not look right.

Account requests Use the account support path to ask for a copy of personal details linked to your api166 account, or to report a phone number that no longer belongs to you. We first check account ownership before sharing or changing records.
Wallet references For DANA, OVO, GoPay or QRIS questions, include the visible transaction reference and approximate date rather than a wallet password. This lets us trace payment status while limiting the sensitive information included in your message.
Access concerns If Mobile Login Indonesia shows an unfamiliar sign-in, tell us the device type and account email or phone path. We can review the access record, ask for verification and help protect the account without requesting private wallet credentials.
HOW WE HANDLE IT

Explore the Privacy Controls We Use

Our privacy work follows the account steps you can actually see: phone verification before account access, payment reference checks and device-based sign-in review.

Data handling

We use contact details, verification results, sign-in events and payment references for stated account purposes. A selection such as Live Dragon Tiger Elite does not by itself require unrelated personal details, and we avoid asking for more than the account task needs.

Cookies

Cookies can keep a login preference, support session continuity and show whether a page loads correctly on your phone or desktop. You can manage browser cookie settings, although changing them may affect account access or saved preferences.

Account security

Phone verification helps connect access to the correct account. We also use sign-in and device signals to identify unusual activity. Never send us a password, wallet PIN or full bank credential when requesting privacy assistance.

Retention

We retain records only for the period connected to account operation, payment checking, security investigation or applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward deletion or removal from active systems.

Correction requests

You can ask us to correct inaccurate contact or account information through support. State what is wrong and what should replace it. We may request phone verification or another account step before making a change that affects access.

Access conditions

Our data practices do not change local eligibility rules. Account access depends on local law. If a request concerns an account used where local law permits, we explain the available data path and any identity check needed.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the practical difference between account information, payment references, device records and cookies. If your situation is not covered, use the account support path with the smallest amount of personal detail needed to identify the issue. We may need to confirm ownership before discussing records or processing a change.

It covers account details, phone verification, sign-in and device records, cookies, payment references and requests about your personal data. It also explains how we use information for account access, security and payment status checks where local law permits.

We do not ask you to send a wallet password or PIN for a privacy request. We may handle a payment reference and status from DANA, OVO or GoPay so a transaction can be matched to your account without exposing your wallet credentials.

Phone verification helps us confirm that the person requesting account access or a data change controls the account contact path. It can also help us investigate an unfamiliar sign-in before we discuss personal details or alter account records.

Contact support from your account area and state whether you want access to a record or correction of a detail. Include only the account identifier needed to locate it. We may complete an ownership check before providing or changing information.

For QRIS, bank transfer or a virtual account, we may use a reference, amount status and timing to trace a receipt. For DANA, OVO and GoPay, the same principle applies. We do not need your wallet password to check status.

Cookies may keep a sign-in preference, support session continuity and help us identify page-loading problems on mobile or desktop. You can adjust browser settings, but removing required cookies may interrupt account access or make preferences unavailable.

The policy applies to the account and data activity described on this page where local law permits. Access or eligibility depends on local law. If you ask about a location-specific concern, contact support and tell us the relevant country or region.

Related Pages

api166 Indonesia Mobile Login Indonesia Access guide FAQ About Us