Reference

Privacy Policy For Your jago landak Account

jago landak Privacy Policy explains what we collect when you open an account, sign in from a mobile device, check wallet status or contact support.

Account dataWallet recordsDevice controlsCookie choices
jago landak Privacy Policy For Your jago landak Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path helps you ask about Privacy Policy records without searching through the lobby. Start from the support link connected to your account area and include the email or phone detail used during registration. We may ask you to confirm an account step before discussing personal data, which keeps a request from being redirected to the wrong person. If a wallet status involving DANA or QRIS appears in your account history, mention the route and date so we can locate the relevant record. From Bandung or elsewhere in Indonesia, use the same account path.

Team online

Policy questions

Use the account support path for questions about this Privacy Policy, including what we store, why a record appears and whether a particular cookie is active. Include your registered contact detail so we can match the request before discussing account data.

Access requests

Ask us to provide, correct or restrict personal data through the support route shown after account access. We may request a verification step before changing records, especially when the request concerns phone details, wallet history or a sign-in device.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, state the wallet route and the related account event. We can then separate payment-status records from general lobby activity and respond to the part of your request covered by this policy.

DATA PRACTICE

What We Do With Your Private Details

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account records

We use registration details, verification responses and sign-in history to maintain account access and investigate suspicious activity.

Wallet activity

Selecting DANA, OVO, GoPay, QRIS, bank transfer or a virtual account creates route and status records linked to the account…

Device signals

A mobile browser can send session, browser and device signals used to recognise an unusual sign-in pattern.

Cookies

Cookies can keep an account session available and show whether a page works as expected.

Retention

We keep personal records while they support account security, wallet reconciliation, support handling or a legal requirement.

Your request

To request access, correction, restriction or removal, contact us through the support route linked to your account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account events you are most likely to question: registration, wallet selection, mobile access, cookies and support requests. We keep the wording direct so you can decide what to ask before opening an account or returning to the lobby. If your situation is not covered, use the account support path and refer to the specific record or device event.

It covers account details, verification events, sign-in and device signals, wallet-route records, cookies, support cases, retention and requests about your personal data. It applies to the jago landak pages and account actions covered here, where local law permits and access depends on local law.

When you choose DANA or QRIS, we record the selected route and its account-related status so we can trace a payment question, confirm an account event and protect the session. We do not use that selection as permission to access unrelated wallet content or device files.

Yes. Send an access request through the support path linked to your account and identify the registered email or phone detail. We may verify ownership before responding, then explain which records can be supplied and which must remain restricted under applicable local requirements.

Tell us which account detail is incorrect, such as a phone or email record, through the account support route. We may ask you to complete a verification step before editing it. Security and legal records may retain the earlier change event while the current detail is updated.

Yes. The Privacy Policy covers session, browser and device signals used to recognise unusual sign-ins and maintain account security. We do not need access to private files, contacts or unrelated applications. Cookie and browser settings can affect how your mobile session is remembered.

We retain records while they support account security, wallet reconciliation, support handling or a legal requirement. After that purpose ends, we remove, anonymise or restrict the record according to its data type. A request through support can ask how a particular record is being retained.

Use the support link connected to your account and state whether you want access, correction, restriction or removal. Include the registered contact detail and the relevant event, such as a GoPay selection or mobile sign-in. We may verify ownership before discussing personal data.