Reference

Privacy Policy for Your pajero898 Account

Our Privacy Policy explains how we handle the account details, wallet records and device signals used when you open pajero898 in Indonesia.

Account dataWallet recordsCookie choicesContact route
pajero898 Privacy Policy for Your pajero898 Account
PRIVACY CONTACT

When Wallet Status Needs Privacy Help

A clear contact route matters when your account record or wallet status needs attention. We direct privacy questions through the account support path so we can match your request with the correct…

Account support path Use the support route connected with your account when you want to ask about collected details, a login record or a privacy request. Include your account contact and the subject of your request, but do not send a password or full wallet PIN.
Wallet record check For a DANA, OVO, GoPay or QRIS question, share the transaction date, wallet name and visible reference rather than a complete wallet credential. We use those details to locate the relevant record while keeping your access secret private.
Access correction request If a profile detail, device entry or account contact is inaccurate, tell us which field needs attention and why. We may ask for an account step that confirms you control the request before changing or disclosing personal details.
DATA HANDLING

Cookies, Login And Account Security

We treat this policy as an operating rule for account data, not as a generic statement about the lobby.

Account details

We may hold the contact details and verification data you enter during account creation or later account checks. These fields help us connect a privacy request to the correct account, and we ask you to keep them current when a change is needed.

Wallet references

A payment record can include the selected rail, reference, amount status and related account identifier. DANA, OVO, GoPay and QRIS names may therefore appear in an account record, while your wallet PIN and password should never be sent through support.

Device signals

When you move from login to the lobby on a mobile browser, we may record browser type, device signals and connection details used for access protection. These signals help us spot unusual account activity without treating your phone as a public identity.

Cookie choices

Cookies can keep an account path working, remember selected settings and help us understand whether a page loads correctly. You can manage cookie settings in your browser, though removing necessary cookies may affect login continuity or the way privacy choices are saved.

Retention period

We retain records only for the period needed for account operation, security checks, dispute handling or a legal duty that depends on local law. When a record is no longer needed, our process is to delete it or separate it from direct account details.

Your request

You can ask what personal data is linked to your account, request a correction or ask about deletion where local law permits. Send the request through account support, describe the record clearly and complete a control step if we need to confirm your identity.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. We keep each answer tied to pajero898 account records, browser access and local payment references rather than describing unrelated lobby features. If your question concerns a record not listed here, use the account support path and identify the relevant account step.

The pajero898 Privacy Policy covers account details, verification records, login activity, wallet references, device signals, cookies, retention and privacy requests. It applies to data handled through our services where local law permits, and the exact duties or rights can depend on local law.

Yes. Privacy Policy coverage includes operational records connected with DANA, OVO, GoPay and QRIS, such as the selected rail, account identifier, transaction reference and status. We do not need your wallet PIN or password for a privacy request, so do not send either credential.

When you open the account path from a phone or desktop, we may record browser type, device signals, connection details and access events. These details support login protection and troubleshooting. They are handled as account-related records under the Privacy Policy, not shown as a public profile.

Use the account support route and state whether you want a data copy, a correction or another Privacy Policy request. Name the account contact and describe the record, such as a device entry or wallet reference. We may ask for an account control step before responding.

We keep personal data for the period needed to operate the account, protect login access, resolve a transaction question or meet a legal duty. Retention can depend on local law. When the reason ends, we aim to delete the record or remove its direct account link.

You can manage cookies through your browser settings, including choices about stored preferences and site activity. Necessary cookies may be needed for login continuity and saving a privacy choice. If you remove them, some account paths may ask you to repeat an access step.

Contact us through the account support path and identify the incorrect field, such as a contact detail, device entry or payment reference. Do not include a password or wallet PIN. We will use an account control step where needed, and the available remedy depends on local law.