Reference

lapakslot Privacy Policy for Your Account

The lapakslot Privacy Policy explains what account, device and wallet data we use when you open the lobby, sign in or check a DANA and QRIS status.

Account dataDevice choicesWallet recordsPolicy requests
lapakslot lapakslot Privacy Policy for Your Account
CONTACT OUR TEAM

Check Privacy Questions Beside Your Account

A clear contact route helps when your question concerns a login record, wallet reference or device setting. From your account area, take the support path and describe the policy point you need checked. Include only the details needed to locate your request; never send a password or full wallet credentials.

Team online

Account access

If a phone verification step or sign-in record looks unfamiliar, tell us the account email or phone reference shown in your profile. We can direct the privacy request without asking for your password.

Wallet record

For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference and date visible in your account. We use that narrow record to check status without requesting unrelated wallet data.

Policy request

Ask us to access, correct or remove eligible account data through the support route linked in your account area. We may verify ownership first, and any action depends on local law.

HOW WE HANDLE DATA

Browse lapakslot Privacy Controls Clearly

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

Account records

When you open an account, we use the phone verification result and core profile fields to create access records. We do not need your password in a support message, and we ask you to keep that secret.

Device sessions

A phone or desktop session can create sign-in, browser and security signals. If a device behaves unexpectedly, sign out from the account and contact support with the session time rather than sending private credentials.

Cookies

Cookies and similar browser storage can remember a session choice or help us understand whether a page loads correctly. You can manage browser storage through your device settings, though some account steps may then need repeating.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be linked to an account action so we can check a receipt and investigate an unclear status.

Retention checks

We retain account, security and transaction records only as long as needed for service operation, dispute handling or legal duties. When a retention reason ends, the record can be deleted or separated from direct account use.

Your requests

You may ask about access, correction or deletion of eligible data through our account support route. We verify the request, explain any lawful restriction and confirm the action taken where local law permits.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. We focus on the records created by sign-in, phone verification, device use and local wallet activity, so you can decide what to share and how to request a change.

It covers account profile data, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains why we use, retain and disclose each category where local law permits.

Phone verification helps connect an account to the person requesting access and helps us spot unusual sign-in activity. We record the verification result and related security event, not your private password.

Yes. A DANA or QRIS transaction reference, along with OVO, GoPay, bank transfer or virtual account records, can be used to match a receipt with your account and check a disputed status.

Use the support route in your account area and ask for a data access request. Give the account contact needed for verification, and we will assess the request under local law before responding.

You can request a correction when a profile field or account record is inaccurate. We may confirm ownership through your verified account contact, then update eligible data or explain why a record must remain.

Retention depends on the record and its purpose. Security, account and transaction data may remain for service operation, dispute handling or legal duties, after which we delete or separate it when allowed.

You can manage cookies through your browser and switch between phone and desktop, but some sign-in or verification steps may repeat. Account access and eligibility depend on local law and device security checks.