Reference

lipat4d Privacy Policy For Your Account

lipat4d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record clarityAccount contact pathMobile access details
lipat4d lipat4d Privacy Policy For Your Account
CONTACT YOUR WAY

Three Paths For Privacy Questions

A privacy question should not require you to explain your entire account history. We separate identity, wallet and data requests so you can reach the relevant support path with the right reference, whether you are checking a QRIS record from a phone or asking about an older account event. Please include enough account detail for us to verify the request without sending passwords or wallet PINs.

Team online

Account help path

Use the account help path for a copy of personal data, an identity correction, or a question about sign-in records. We may ask for an account step to confirm that the request comes from you.

Wallet status path

Choose the wallet support path when a DANA, OVO, GoPay or QRIS reference appears in your account history. Share the transaction reference, not your wallet password or private security code.

Policy request path

Use the policy contact path for cookie choices, deletion questions or retention concerns. Tell us which account detail you mean, and we will explain the available action where local law permits.

OUR DATA PRACTICE

Six Checks Behind Your Privacy Choices

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Collection purpose

We collect account details to create access, verify an account step and respond to support. Browsing signals around Speed Blackjack or Rocket Crash may be linked to session protection, not used as a reason to request unrelated personal details.

Cookie control

Cookies can preserve a sign-in state on your phone and help identify an unusual device session. You can clear browser cookies through your device settings, though doing so may require another account verification step.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references and status details needed to match a record. We do not ask for your wallet PIN as part of a policy request.

Account security

We use sign-in events, device signals and verification checks to help protect account access. If a session looks unusual, support may ask you to confirm account details before discussing stored personal data.

Retention choices

We retain records for the period needed for account security, transaction matching and legal duties. If you ask why a record remains after an account change, we will explain its purpose and available options.

Change requests

You can request access, correction or deletion by contacting support through the account help path. We check the request against your account, then explain the result and any limit where local law permits.

Privacy Policy Questions About lipat4d

These answers address the questions we expect you to ask before opening an account or connecting an Indonesian wallet. They focus on personal data, cookies, payment references, account verification and the practical route for a request. If your case involves a record not listed here, contact us through the policy request path and include the relevant account reference.

It covers account details, verification records, sign-in events, device signals, cookies, wallet references and support requests connected with your use of lipat4d. It also explains retention, corrections and deletion requests.

DANA and QRIS create transaction references that can appear in your account history. Our Privacy Policy explains that we use status and reference details to match activity, investigate questions and avoid requesting wallet passwords.

Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS PIN for account support. Send only the transaction reference or account detail needed for verification, and never disclose a private security code.

Use the account help path and ask for a copy of the personal data connected with your account. We may request an account verification step before releasing details, because the request must come from you.

Yes. Tell us which detail is incorrect and provide the accurate replacement through the policy contact path. We compare the request with your account record, then confirm the change or explain why another step is needed.

Cookies can keep your mobile browser connected to a sign-in session and help us identify unusual device activity. Clearing them through your phone settings may sign you out and trigger another verification step.

You can ask us to delete eligible personal data through the policy request path. Some records may remain for security, transaction matching or legal duties, and the outcome depends on local law.