Reference

Privacy Policy for Your iblet Account

Our Privacy Policy explains how we collect, use and protect the details connected with your iblet account, including phone verification, wallet status and payment records for DANA, OVO…

Account dataWallet recordsCookie choicesSecurity requests

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies

iblet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers information you provide during account creation, such as your phone number and verification details, plus records created when you use account access, wallet tools or support. A DANA, OVO, GoPay or QRIS reference can help us match a payment status to your

1
account, while bank transfer and virtual account records may contain a bank reference and amount. We use these details to process your request, check unusual activity and answer payment questions. We do not use payment data as a reason to send unrelated messages. The policy applies
2
where local law permits and may change when legal or operational requirements change. We will show the current wording on this page, and you can ask us to clarify a section before opening an account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Where To Ask About Your Data

A clear contact path matters when a Privacy Policy question concerns your account rather than a general explanation.

DATA HANDLING

What We Do With Account Details

The Privacy Policy is designed around the records our service actually creates: account identity, device access, wallet events, support messages and security signals.

Account collection

When you open an account, we collect the details needed for the account path and phone verification. If you contact support about access, the device type and sign-in timing can help us identify the correct record without asking for your password.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account events can create reference data. We use those references to match a status to your account, investigate a duplicate record or answer why a cashier step remains pending.

Cookies

Cookies and similar storage can remember a session, protect account access and retain a choice made on the site. Your browser controls can remove them, although account pages may ask you to sign in again afterward.

Security checks

We may examine sign-in timing, device changes and unusual account actions to protect your account. These checks support security decisions; they are not a reason for us to request your wallet PIN or full payment password.

Retention

We keep records for as long as they support the stated account, payment, security or legal purpose. When a category no longer needs to remain available, our handling follows the retention rules that apply to that record and location.

Your requests

You can ask for access, correction, clarification or deletion where applicable. Include the account phone number or another safe identifier, describe the requested change, and be ready for an account check before we disclose or alter personal data.

Privacy Policy Questions About iblet

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they open an account. They explain what to prepare, which records may appear after a wallet action and how to request help. If your situation is unusual, contact us with the smallest useful set of details and we can assess the request under the current policy and where local law permits.

The iblet Privacy Policy covers account details, phone verification, device access, cookies, wallet and payment references, support messages, security signals and retention. It explains why we use each category, how requests are assessed and when local law may affect access, correction or deletion.

Phone verification helps connect the account request with the person trying to access it and helps us handle account recovery or unusual sign-in activity. We use the verification detail for those account and security purposes, subject to the Privacy Policy and local requirements.

Yes. A DANA or QRIS action can create a reference, status, time and amount connected with your account. We use that information to match a cashier event, investigate a pending status or answer a support request. Do not send a wallet PIN.

Contact us through the account support path and state that you are making a Privacy Policy access request. Name the account identifier and categories you need, such as phone, cookie or payment records. We may verify account control before providing the applicable data.

You can ask us to correct an inaccurate account detail by describing the field and the correct value. Include a safe account identifier, not your password. We may check the request against phone verification before changing the record, where local law permits.

Retention depends on why the record exists and on the rules applying to that record. Payment references from GoPay, OVO, bank transfer or a virtual account may remain for payment matching, security or legal purposes after an account change.

Use the available iblet support route and describe the policy issue in plain English, including the account step or payment reference involved. Share only what is needed for us to locate the record. We may request an account check before discussing personal data.

Privacy Policy for Your iblet Account

Where To Ask About Your Data

What We Do With Account Details

Account collection

Payment matching

Cookies

Security checks

Retention

Your requests

Privacy Policy Questions About iblet

01 What does the iblet Privacy Policy cover?

02 Why does iblet need my phone verification details?

03 Does the Privacy Policy include DANA and QRIS records?

04 How can I request a copy of my iblet data?

05 Can I ask iblet to correct my account information?

06 How long does iblet keep payment information?

07 How do I contact iblet about a Privacy Policy issue?

Related Pages