Reference

Privacy Policy For Your adslot Account

Our Privacy Policy explains how adslot handles the details linked to your account, wallet activity and device access.

Account dataWallet recordsCookie choicesYour requests
adslot Privacy Policy For Your adslot Account
CONTACT OPTIONS

Privacy Questions Through Account Help

A clear contact route helps you act on this Privacy Policy without searching through the lobby.

Account Wallet Help Use Account Wallet Help for questions about data connected to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We can check the relevant account reference without asking for your wallet PIN or complete security code.
Phone Verification If your Privacy Policy request relates to phone verification, tell us which account step stopped and the device path you used. We may ask for limited account details to confirm that the request comes from you before discussing personal records.
Policy Request For a copy, correction or deletion question, describe the specific record and your requested action. We assess the request against account security, transaction records and local requirements, then explain the next step through the available support route.
DATA PRACTICES

How We Handle Your Account Details

Privacy depends on practical controls, not vague promises. We separate account access records from the payment references needed for reconciliation, limit internal access to operational needs and use account checks before discussing…

Account collection

We collect details you provide during account creation and phone verification, plus records created when you sign in or request help. These details help us connect the correct account to your access request and prevent another person from receiving account-specific data.

Payment references

For DANA, OVO, GoPay and QRIS, we use payment references and status details to match activity with your account. Bank transfer and virtual account records serve the same operational purpose. We do not need your payment PIN to check a status.

Cookies and devices

Cookies and device signals can keep a sign-in path working, remember selected settings and help identify unusual access. Your mobile browser and desktop browser may create separate records, so a change on one device may not appear immediately on the other.

Account protection

Phone verification is an account step before access to personal records. We may ask you to confirm account details when you request a correction or deletion. Never place a password, wallet PIN or full verification code in a support message.

Retention period

We keep personal details only for the period needed for the purpose described in this Privacy Policy, account security, dispute handling or required transaction records. When a record is no longer needed, we remove it or use a form that no longer identifies you.

Change requests

You can ask us to review inaccurate account details, explain a data use, provide available access or remove eligible information. State the account step and record involved. We may verify your identity first, and access depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and wallet questions you may have before opening an account. We keep the wording practical: what is collected, how a request works, what happens on mobile, and why payment references appear in account records. If your situation is unusual, use Account Wallet Help and describe the exact step you need us to check.

The adslot Privacy Policy covers account creation, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use those details for account access, wallet reconciliation, security and requests connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We collect the details you submit for your account and phone verification, along with technical records created during sign-in and browsing. We may also receive support and transaction references. We use these details to connect activity to your account and protect personal records from improper access.

DANA and QRIS records help us match a payment status or reference with the correct account. Similar references can arise from OVO, GoPay, bank transfer or a virtual account. We need the operational status, not your wallet PIN, to investigate a cashier question.

Use Account Wallet Help and state which account detail appears incorrect and what change you want. We may ask for phone verification or another account check before discussing the record. We assess the request under this Privacy Policy and where local law permits.

You may request removal of eligible personal data through the policy contact path. Some records may need to remain for account protection, transaction reconciliation, dispute handling or legal requirements. We explain which information can be removed and which retention reason applies.

Cookies can support sign-in continuity, remember selected settings and help us identify unusual access. If you move from a mobile browser to desktop, the two devices may hold different cookie records. You can manage browser settings, although some account steps may then need to be repeated.

The Privacy Policy describes our data handling, but it does not override access or eligibility rules. Those conditions depend on local law. If you are in Indonesia, including Makassar, check the current access position before opening an account and contact Account Wallet Help for a policy question.