Reference

Privacy Policy For Your ledakjitu Account

ledakjitu Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account recordsWallet activityCookie choicesAccess depends on local law
ledakjitu Privacy Policy For Your ledakjitu Account
CONTACT PATHS

Get Privacy Policy Help Through Support

A clear support route helps you act on the Privacy Policy instead of guessing which account step to take. Sign in first when you can, then use the account help path so we can connect your request with the correct profile and payment reference. If login has stalled, include the contact detail used during registration and describe the issue without sending your password or full wallet PIN. We can then explain the next verification step, locate the relevant record, and direct a correction or access request to the right team.

Team online

Account help path

Use the account help path for a Privacy Policy request tied to your profile. Include your registered contact detail, the type of request, and the relevant date. We ask for only the checks needed to confirm that the request comes from the account holder.

Payment receipt check

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record needs correction, attach the payment reference rather than a password or wallet PIN. We compare the reference with the account ledger and explain what can be changed.

Access recovery

When you cannot sign in, describe the device path and the last account step you completed. We may ask for phone verification before discussing personal data. This keeps a Privacy Policy request connected to the correct account without exposing details.

HANDLING DETAILS

What We Do With Account Data

We handle personal data for clear operational reasons: creating and protecting your account, recording wallet references, responding to support, and keeping the lobby session secure.

Collection at account opening

We collect the contact details and phone verification result you submit during account creation. These records let us identify your profile when you ask for access or correction. We do not need your password in a support message, and you should never send it.

Wallet reference records

DANA, OVO, GoPay and QRIS activity can create a payment reference, amount status, and time record beside your account. Bank transfer and virtual account checks use the same limited reconciliation purpose. We use these details to investigate status questions, not to request your wallet PIN.

Cookies and device signals

Cookies can keep a sign-in session active and remember a setting on your browser. Device signals, browser type, and security events help us detect an unusual access pattern. You can clear cookies in your browser, although doing so may require another account verification step.

Account security

Phone verification can be required before account access or before we discuss personal records. Keep your password private and use the sign-out step on a shared device. If you notice an unfamiliar sign-in, contact support through the account help path with the time and device used.

Retention and deletion

We retain account, payment-reference, and support records for the operational and legal period that applies to them. A deletion request may not remove records we must keep for security, dispute handling, or legal duties. We explain the applicable reason when a request cannot be completed in full.

Requests and corrections

You can ask for a copy of personal data, correct an inaccurate contact detail, question a cookie record, or ask how long a record is held. Send the request through the account help path. We verify identity first, then confirm the action or explain its limit.

Privacy Policy Questions About ledakjitu

These Privacy Policy answers focus on the account actions you are most likely to search for before registration or while checking a wallet record. We keep the route practical: identify the account, describe the record, and use the support path without sharing secret credentials. If your question concerns access from Indonesia, remember that availability depends on local law and applies where local law permits.

The ledakjitu Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. It explains why we use these records, how long they may be kept, and how to request action.

We use payment data mainly as a reference for matching an account entry with a wallet or bank status. A DANA, OVO, GoPay, or QRIS record may include a reference and status, while bank transfer or virtual account checks may use the same reconciliation details. We do not need your PIN.

Yes. Send a request through the account help path and identify the contact detail connected with your account. We verify your identity before releasing personal records. Your request can cover account details, phone verification status, cookie-related records, support messages, or payment references held for your profile.

Describe the incorrect field and provide the account contact detail used during registration. For a payment issue, add the DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference and date. We check the record, make a permitted correction, and tell you when the change is complete.

Yes. Cookies can keep your session active and remember a browser setting, while device signals help us investigate unusual sign-ins. You can clear cookies through your phone or desktop browser settings. After clearing them, the account may ask for login or phone verification again before access continues.

Use the account help path to request deletion and state which records you want us to assess. We review identity and retention duties first. Some account, payment-reference, security, or dispute records may need to remain for a required period, and we explain that limit in our response.

This Privacy Policy applies to our handling of your account and related records where local law permits. Account access or eligibility depends on local law, including the rules relevant to your location. If you are unsure, ask support through the account help path before submitting personal details or opening an account.