Reference

ledak388 Privacy Policy for Your Account

VIP Baccarat, Ganesha Gold and QRIS account records are covered by the ledak388 Privacy Policy, so you can see what we collect before opening an account.

Clear data purposesWallet record controlsCookie choicesAccount access rights
ledak388 ledak388 Privacy Policy for Your Account
PRIVACY HELP PATH

Switch From Login Help To Privacy Support

A clear contact path matters when a privacy request follows a login or wallet question.

Account access request Use the support path connected to your account when you need a copy of…
Wallet record query For DANA, OVO, GoPay or QRIS questions, provide the payment reference and approximate date.
Policy change request Ask us to correct an account detail, withdraw a suitable permission or remove eligible…
DATA HANDLING DETAILS

Browse How Your Privacy Is Managed

We keep the Privacy Policy practical by connecting each data use to an account step.

Account details

We use your submitted contact and account details to create your profile, send account-related messages and respond to requests.

Phone verification

Before account access, a phone verification step may connect your sign-in attempt with the correct profile.

Device signals

Browser and device signals can be recorded around login, wallet status checks and account changes.

Cookie settings

Cookies can keep your session available and remember selected settings.

Retention checks

We retain account, security and transaction references for the period needed for service operation, dispute handling or legal duties.

Policy contact

Send privacy questions through the account support route and describe the action you want: access, correction, deletion or purpose clarification.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the searches we hear most often from people considering an Indonesia account. They explain wallet references, cookies, device checks, account requests and local access in direct terms, so you know what to expect before registration.

The ledak388 Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet references, support messages, retention and requests to access, correct or remove eligible records.

No. We use transaction references and account matching details for DANA, OVO and GoPay activity. We do not need your wallet PIN, so you should never place it in a support message.

QRIS, bank transfer and virtual account references help us identify which account activity belongs to a transaction. The Privacy Policy explains this use so payment matching is distinct from access to your banking credentials.

Yes, send an access request through the account support route. We may verify ownership first, then explain which records can be provided and whether any legal or security reason limits the response.

Use the privacy support path and name the detail that needs correction, such as a phone contact or account field. Include enough context to locate it, but do not send a wallet PIN.

Cookies can maintain a login session and selected settings, while device signals help identify unusual account access. Browser controls can remove optional cookies, but required settings may be needed for account tools.

You can request deletion through support, and we will assess which records are eligible. Some account, security or transaction references may need to remain for legal or dispute reasons where local law permits.