Reference

Privacy Policy For Your lipat4d Account

Your account, wallet and device details stay connected to clear privacy choices on lipat4d.

Account dataWallet referencesMobile access
lipat4d Privacy Policy For Your lipat4d Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when your account details need correction or a wallet reference looks unfamiliar. Use the support path connected to your account and include the sign-in identifier, the affected date and the request you want us to check. You can ask about records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity without sending a full wallet password. We may ask for account details to confirm that the request comes from you.

Team online

Account correction

Use account help after phone verification if your name, contact detail or sign-in record needs a change. We review the request against the account details already held and explain the next step through the same support route.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction date and displayed status rather than a password. We use those details to locate the relevant record while limiting unnecessary payment data.

Privacy request

For access, correction or deletion questions, send a specific request through account support. We may verify your phone-linked account before discussing personal records, then explain which data can be changed or retained.

DATA PRACTICE

How lipat4d Handles Your Details

We keep privacy decisions tied to practical account activity rather than collecting details without a reason.

Account security

Phone verification helps us connect an access request with the correct account. Keep your sign-in details private, and contact support if a device you no longer use appears connected to your account.

Mobile browser data

When you open the lobby on a phone, we may receive basic browser, device and session details. These records help us diagnose sign-in or display issues without treating your device as a public profile.

Cookies and settings

Cookies can preserve a session or a language choice so you do not repeat the same account step on every page. Your browser settings can remove or restrict cookies, though some account functions may then need another sign-in.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match payment status with the correct account. We do not ask you to send a wallet password when checking a receipt.

Retention choices

We retain account and support records only while they serve the purpose described in this policy or a necessary account, safety or dispute process. A deletion request may be limited where a record must remain available.

Policy changes

If this Privacy Policy changes in a material way, we will present the updated wording on the policy page. Check the page before opening an account or continuing access, especially when using a new device.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account steps and payment records you are most likely to ask about before using lipat4d. They cover access, device behaviour, wallet references, corrections and contact requests in plain terms. If your situation is not listed, use the support route linked with your account and describe the exact record or action you want us to check.

We may collect the details needed to create and verify your account, including contact information, phone verification results and basic device or session records. We use them for account access, support and safety checks, not as a public profile.

We use payment references, displayed status and related account details to match a DANA, OVO, GoPay or QRIS request. Do not send a wallet password. Share only the receipt details needed for us to locate the payment record.

Yes. Send a correction request through the account support path and identify the record that looks wrong. We may confirm your phone-linked account before changing details, then explain whether the correction is complete or needs more evidence.

Yes. The policy covers basic browser, device and session information collected when you sign in from a phone or desktop. These details help us investigate access problems and maintain necessary settings, while browser controls can manage some cookies.

We keep records while they serve the account, safety, support or dispute purpose described in this policy. When that purpose ends, we assess removal. Some records may remain when a necessary account or payment-status process still requires them.

Use the support route linked to your account and ask for access to your personal records. Include your sign-in identifier and the area involved, such as phone verification, device data or QRIS status. We may verify ownership first.

Yes. Privacy rights, account availability and certain requests depend on local law. We apply the policy to the extent required for your location and will explain any limit if a requested change, deletion or access step cannot be completed.