Reference

lapakzeus Privacy Policy For Your Account

Clear data choices matter when you open an account, connect DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesPrivacy requests
Browse Our Lobby Read FAQ
lapakzeus lapakzeus Privacy Policy For Your Account
PRIVATE HELP ROUTE

Where To Ask About Privacy

A direct privacy question should reach the same support path that handles account and wallet status, so you do not need to repeat your case across separate pages.

Account privacy request Use the support route beside the cashier path to ask which account details we hold, why they are used, or how to request a correction. Include your account identifier, but do not send a password or wallet PIN in the message.
Payment record question If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record looks wrong, share the transaction reference through support. We compare it with the account ledger and may ask for a receipt before discussing the result.
Device access concern Tell us if a login appears from an unfamiliar phone or browser. We can check sign-in details, guide an account security step, and explain what device records are retained under this Privacy Policy.
HANDLING DETAILS

Six Practical Privacy Commitments

Privacy becomes easier to assess when each data action has a clear reason. We separate account identifiers from payment references where our operating records allow, limit internal access to people handling the…

Account creation

When you open an account, we collect the details needed for account setup and phone verification before access. This helps us connect your sign-in with the correct account without asking you to share a password through support.

Wallet matching

A DANA, OVO, GoPay, or QRIS reference helps us match a payment event to your account. Bank transfer and virtual account records may carry a bank reference, but we do not need your wallet PIN to check status.

Device signals

Your browser and device may provide language, screen, session, and sign-in details. We use these signals to keep a session working and identify unusual access; they are not treated as a substitute for your account password.

Cookie controls

Cookies can keep your session open, remember selected settings, and help us understand which policy page brought you to an account step. You can adjust cookie controls in your browser, although some account functions may then need another sign-in.

Retention timing

We keep account, payment, support, and security records only for the period needed for service operation, dispute handling, fraud checks, or legal duties. A deletion request may be limited when a record is still required for one of those purposes.

Change requests

You can ask us to correct an account detail, explain a payment reference, or clarify how a device record is used. We verify the requester first, then respond through the support path linked to your account.

Privacy Policy Questions From Indonesia

These answers address the privacy questions you are most likely to have before opening an account or connecting a local wallet. They cover account records, cookies, device access, payment references, retention, and request handling. If your case involves a specific transaction or sign-in, use the support route shown in your account area and keep the relevant reference ready.

It explains how we handle account details, phone verification records, device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also describes your available privacy requests and the limits that may apply where local law permits.

We do not ask you to send a DANA, OVO, or GoPay wallet PIN through our support route, and a QRIS payment check uses a transaction reference rather than your PIN. Your bank or wallet provider controls its own credentials under its separate privacy terms.

Device and browser signals help us maintain a login session, recognise a familiar access pattern, and investigate an unusual sign-in. They can include device type, browser settings, language, and session timing. We use them for account protection and service operation, not as your account password.

Send a request through the support channel shown beside the account or cashier path. State whether you want an account detail checked, a payment reference explained, or a record corrected. We first verify that you control the account, then assess the request under this Privacy Policy and local law.

Retention depends on why a record exists. Account, payment, support, and security entries may remain while needed for service operation, dispute checks, fraud review, or legal duties. When a record is no longer needed, we remove it or reduce its connection to your account where our process allows.

You can change cookie settings in your browser and, where available, through the cookie controls presented on the site. Essential session storage may still be needed for account access. If you block it, you may need to sign in again or lose selected page settings.

The policy applies to the lapakzeus account path used from Indonesia, including Medan, subject to local law. DANA, OVO, GoPay, QRIS, banks, and other payment providers may process related records under their own terms, so their privacy pages can also apply to your transaction.

Related Pages

lapakzeus Indonesia About Us FAQ Account information GoPay Withdraw Guide