Reference

Privacy Policy For Your itl4d Account

Our Privacy Policy explains how itl4d handles the details connected with your account, device and wallet activity in Indonesia.

Clear data purposesWallet activity contextPhone verification stepsPolicy access anytime
itl4d Privacy Policy For Your itl4d Account
HELP WITH PRIVACY

Where To Ask About Your Records

A direct support request gives you a practical route when a privacy question is tied to a login or wallet status. Tell us which account step is involved, such as phone verification, a QRIS receipt or a bank transfer reference, and we can locate the relevant request without asking you to post personal details publicly. We may need to confirm account ownership before discussing records. Where local law permits, you can ask for access, correction or deletion through the same support path.

Team online

Account privacy request

Use our account support path to ask what personal details are held for your itl4d account. Include the account phone number in the secure form, then complete any ownership check we request before records are discussed.

Wallet record question

For DANA, OVO, GoPay or QRIS activity, send the payment reference and approximate date through support. We use those details to find the relevant status record while keeping the wallet conversation attached to your verified account.

Correction or removal

If a profile detail is wrong or you want an eligible record removed, state the exact change in your request. We explain any account, fraud-prevention or local-law reason that means a record must remain available.

DATA HANDLING

What We Do With Policy Requests

Privacy work is connected to ordinary account operations, so we explain the handling rather than hiding it behind general wording.

Account details

We may handle your phone number, account identifiers, sign-in records and support messages to operate account access and answer a Privacy Policy request. We use the details relevant to the question instead of requesting unrelated profile material.

Cookies and device use

Cookies can remember a session or a privacy choice on your browser. Device and browser signals may help us protect the sign-in path, but a cookie setting does not replace phone verification when account ownership needs confirmation.

Payment references

A cashier inquiry may include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use that reference to trace the requested status and avoid attaching another account's payment record to your reply.

Account protection

We check account ownership before sharing private records or changing account details. Phone verification, sign-in checks and support questions help reduce the chance that another person receives your account data.

Retention approach

We keep records only as long as they serve account operation, security, dispute handling or a local-law requirement. When a retention period ends, the record can be removed or kept in a form that no longer identifies your account.

Your contact route

Send a request through account support when you want to inspect, correct or ask about your records. Mention Privacy Policy in the subject, describe the account step involved, and use the verified account route for a faster ownership check.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain what happens around account creation, wallet references, browser cookies, device checks and requests for record changes. If your question concerns a particular DANA, OVO, GoPay, QRIS or bank transfer entry, include its reference through the secure support route rather than sharing it in a public message.

The itl4d Privacy Policy covers details linked to your account, phone verification, sign-in activity, device session, support conversations and cashier references. It also explains cookies, retention, account protection and the route for asking to inspect or correct eligible records.

We use your phone number to create and identify the account, complete phone verification and help protect sign-in access. If you contact us about a Privacy Policy request, we may ask for an ownership check before discussing records connected with that number.

Yes. The Privacy Policy covers payment references shown in an account inquiry, including DANA, OVO, GoPay and QRIS. Bank transfer and virtual account references can also be checked when you ask about a cashier status, subject to the records we are allowed to retain.

Cookies may remember a browser session or your privacy choice. Device and browser signals can also support sign-in protection. Cookies do not replace phone verification, and you can ask support about a cookie-related concern through the account route.

You can request a correction through support by naming the account detail that is wrong and explaining the requested change. We confirm ownership first, then update eligible records or explain why a particular entry must remain unchanged.

You may ask whether an eligible record can be deleted through the verified support path. We assess the request against account security, dispute handling and local-law duties. If a record must remain, we explain the reason and applicable handling.

Use account support and write Privacy Policy in your request subject. Describe the relevant account step, such as phone verification, a QRIS receipt or a sign-in concern. We may request confirmation through your verified account before sharing private details.