Reference

Privacy Policy For Your ads189 Account

Our Privacy Policy explains how we handle the account details, device signals and wallet records connected with your ads189 access.

Account dataWallet recordsCookie choicesSecurity requests
ads189 Privacy Policy For Your ads189 Account
CONTACT PATHS

Privacy Help Near Your Account

A privacy request should be easy to send, especially when a login or wallet status is unclear. We route privacy questions through the same account-help path used for payment receipt and status checks, so you can identify the affected account without sharing a password. Use the Email Support Desk when you need a copy of stored details, a correction, or clarification about cookies. Include your account identifier and the subject of the request; we will ask for additional proof only when needed to protect your account.

Team online

Email Support Desk

Send a privacy request through Email Support Desk with your account identifier, the data question and a preferred reply address. We use those details to locate the correct record without asking you to send a password.

Account access check

If your privacy request concerns a locked login, tell us whether the issue appeared after phone verification or a device change. We compare the request with account records before discussing personal data.

Wallet status trail

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment receipt reference rather than full wallet credentials. This helps us trace status while limiting sensitive details.

DATA PRACTICE

How ads189 Handles Policy Requests

We separate account access records from the content needed to operate the lobby, and we limit internal handling to the purpose described in this Privacy Policy.

Account data

We may collect your account identifier, contact details and phone verification status when you open access. These fields help us connect a request to the correct account and prevent another person from receiving your data.

Device signals

Your mobile or desktop browser can provide session, device and security signals during login. We use them to spot unusual access and resolve a failed account path, not to request your private device content.

Cookie choices

Cookies can keep a session active, remember selected settings and help us understand which policy page brought you to a request. You can ask us to explain or adjust non-essential cookie use.

Wallet records

A DANA, OVO, GoPay or QRIS transaction may leave a reference, amount status and timestamp in account records. Bank transfer and virtual account references can be handled in the same limited way.

Retention period

We keep account, security and payment references only for as long as needed for access support, dispute handling, fraud checks or applicable local duties. You may ask why a particular record remains stored.

Change requests

To request access, correction or deletion, contact Email Support Desk with the relevant account detail. We verify ownership first, then explain the action available and any record that must remain for a stated reason.

Privacy Policy Questions About ads189

These Privacy Policy answers focus on the practical questions you may have before opening an account or sending a data request. We explain what happens during phone verification, how payment references are handled, why a mobile device can create session records and which route to use when you want a correction or access request. Where access or eligibility is discussed, it depends on local law.

It covers account and contact details, phone verification status, device and session signals, cookie settings, lobby activity records and payment references. For DANA, OVO, GoPay and QRIS, we generally use transaction status and reference details to connect a request to your account.

Phone verification helps us confirm that the person requesting account access matches the account record. It also gives our support team a safer way to check a privacy request. We do not ask you to send a password through Email Support Desk.

Yes. A mobile or desktop browser can create records such as session time, device signals and login status. We use these details to investigate failed access or unusual activity. We do not use this process to inspect private files, photos or unrelated device content.

We may retain a DANA or QRIS reference, status and timestamp when you connect a payment request to your account. These details support receipt checks and wallet-status questions. Avoid sending full wallet credentials; a receipt reference is normally enough for our first check.

Yes. Contact Email Support Desk with your account identifier and describe whether you want access or a correction. We verify account ownership before sharing or changing records. If a record must remain for security, dispute handling or local duties, we explain that reason.

We retain records for the period needed to provide account support, investigate security issues, handle payment disputes or meet applicable local duties. The period can differ by record type. You can ask why a specific account, cookie or wallet reference is still stored.

The policy is intended for our Indonesia access flow, including account steps and local wallet references, but access and eligibility depends on local law. If a local rule affects your account or request, we will explain the relevant limitation through our available support path.