Reference

Open llk21 Privacy Policy Clearly

llk21 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsDevice cookiesPrivacy requests
llk21 Open llk21 Privacy Policy Clearly
CONTACT ROUTES

Contact Us About Privacy Policy

A privacy question should have a clear route, so we keep account and data requests close to the support path.

Account privacy request Use the support contact beside your account area when you need to ask about…
Wallet data query For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, send the…
Policy change request If you want a correction, access copy, or other privacy action, state the request…
DATA HANDLING

Explore How We Handle Privacy Data

We separate the data needed for account access from the payment references used to reconcile wallet activity.

Account collection

When you create an account, we collect the contact and verification details needed to establish access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us match a wallet event to your account.

Cookie choices

Cookies can remember a session, device preference, or page setting.

Security records

We record sign-in time, device signals, and account actions to protect access and investigate suspicious activity.

Retention timing

We keep personal and payment records only for as long as needed for the stated service, account disputes, security checks…

Request verification

For access, correction, or deletion requests, we may ask you to confirm the account phone or another account detail.

Ask About llk21 Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or using a local wallet. We explain the data connected with login, payment status, cookies, device changes, and privacy requests in direct terms. If your situation is not covered, use the support route and describe the account step involved. Access depends on local law, so the action available for a request can vary by location.

It covers account details, phone verification, login activity, device signals, cookies, payment references, wallet status, support messages, retention, and privacy requests. It also explains why we use each category and when we may need to confirm account ownership.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We use these records to match a wallet event with your account and resolve status questions.

You can send an access request through the privacy support path. Tell us the account phone or contact detail connected with your login. After an ownership check, we can explain the data held and any limits that depend on local law.

Cookies may remember a session, device setting, or page preference. Your browser controls can remove or restrict them. If you clear cookies, we may ask you to sign in again, and some account steps may not behave as before.

A new phone or desktop can create a new session record, including device and sign-in signals. We use those details for account security. If access is challenged, complete the requested account verification rather than sharing a password or code.

You can request a correction or deletion through support, where local law permits. We may retain certain payment, security, dispute, or legal records for the required period, and we will explain the result after confirming your account.

Use the support contact connected with your account and identify the privacy issue, such as a login record, cookie choice, or QRIS reference. Do not send passwords or one-time codes. We may request account details to verify your request.