Reference

lapak39 Privacy Policy for Your Account

Our Privacy Policy explains what lapak39 records when you open an account, verify your phone, enter the lobby, or use DANA and QRIS.

Phone verificationWallet recordsDevice controlsPolicy requests
lapak39 lapak39 Privacy Policy for Your Account
CONTACT ROUTES

24/7 Support For Privacy Requests

A privacy request should reach the account area through the same route used for login or wallet questions.

Account access request Use the support path beside login when you want a copy of account details…
Wallet record question Mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account when asking about a…
Device or cookie query Tell our 24/7 Support route if a new phone, browser session or cookie appears…
ACCOUNT SAFETY

Device Cookies And Account Protection

Privacy controls work best when they match the way you actually enter the account. We separate account details from technical session signals where our systems allow, retain records…

Account data

We use your account name, contact detail and phone verification status to connect the right person with the right account.

Payment matching

A DANA, QRIS or bank transfer reference lets us match a wallet event without treating every lobby action as a…

Cookies

Cookies can keep a browser session connected and remember basic access settings.

Device signals

Browser type, device markers and session timing can help us spot an unfamiliar login.

Retention

We keep records only for the period needed for account operation, payment matching, security checks or legal duties.

Changes and contact

Ask us to correct, access or remove eligible data through the support route.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before account access: payment records, device activity, cookies, retention and correction requests. If your question concerns a particular wallet or login event, include that detail when contacting our support route.

It covers account details, phone verification, device signals, cookies, wallet references, support messages, retention and requests to access or change eligible records.

We store the transaction reference and status needed to match DANA or QRIS activity with your account. We do not need identical records for every account action.

Device and browser signals help connect a session to your account and identify unusual access. A new phone may require phone verification before account access is restored.

Yes, send the request through our support route with your account reference. We may confirm your identity first, then explain which records can be provided where local law permits.

Describe the incorrect account, wallet or device record and provide the corrected detail through support. We will assess the request against account security and applicable local requirements.

Retention depends on the reason for the record, including account operation, payment matching, security checks and legal duties. Records are addressed for removal when they are no longer needed.

Yes. Account access and any related eligibility depends on local law. Our Privacy Policy explains the data used for verification, while support can clarify a specific access question.