Reference

penjaga88 Privacy Policy At A Glance

Our penjaga88 Privacy Policy shows what we collect before and after your account opens, why phone verification is needed, and how wallet records from DANA, OVO, GoPay and…

Clear data categoriesWallet record contextAccount privacy requestsMobile browser guidance
penjaga88 penjaga88 Privacy Policy At A Glance
CONTACT ROUTES

Where To Ask About Your Privacy

A privacy question should not require you to search through payment screens. We provide a support path from the account area and keep it close to the cashier path, so you can ask about a phone verification record, a wallet reference or a browser session in context. Include your account contact and the issue you want checked, but never send a wallet password or full payment credential. Where access is discussed, our response remains subject to local law.

Team online

Account privacy request

Use the account support route to ask what personal data is connected with your profile or to request a correction. We may ask for a phone verification step before discussing account-specific records, so a stranger cannot obtain details using only a copied username.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account entries, share the visible transaction reference and date through support. We can compare the status held against your account without asking for a wallet PIN, password or complete payment credential.

Device and cookie help

If a mobile browser keeps an old session or cookie, contact us from the account support path and describe the device behaviour. We can explain which browser data to clear and which account step may be needed before access is restored.

DATA PRACTICE

Controls Behind Your Account Data

Our privacy work follows the same practical path you see when an account opens: identify the account, check the phone verification result, record the access event and limit staff visibility to the…

Account details

We use the contact details you provide to create and maintain your account, identify your requests and send account-related replies. Phone verification is checked before account access and may be referenced when we need to confirm that a privacy request came from you.

Wallet separation

Payment handling records show whether a DANA, OVO, GoPay, QRIS, virtual account or bank transfer entry matches your account. Our policy does not require us to collect your wallet password, PIN or complete card-style credential to reconcile that status.

Cookie choices

Cookies and similar browser storage can keep a session recognised, remember selected settings and help us detect an unusual login pattern. On Android or iPhone, you can clear site data through your browser settings; doing so may require phone verification again.

Security checks

We record sign-in time, browser and device signals to protect account access and investigate a suspicious session. If an account step or identity check changes, we may pause the request until the available details match the account record.

Retention period

We keep account, transaction-reference and support records only while they serve account security, reconciliation, dispute handling or a legal requirement. When a purpose ends, records are deleted or changed so they no longer identify you where that process is practical.

Changes and contact

You can ask us to correct account details, explain a stored record or clarify how a cookie and device signal was used. Send the request through the account support route, identify the relevant account step and avoid including wallet passwords or private credentials.

Privacy Policy Questions From Indonesia

These answers address the searches we receive before an account is opened: what penjaga88 stores, how a payment reference is used, what happens on a shared device and how to ask for a change. We keep each answer tied to the Privacy Policy rather than describing unrelated lobby features. If your situation involves access or eligibility, the outcome depends on local law.

The penjaga88 Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages and payment-status references. It explains why we use each category, how we protect account access, how long records may remain and how you can request correction or clarification.

Yes. Our Privacy Policy covers the transaction reference, visible status and reconciliation details linked to DANA and QRIS, along with OVO, GoPay, virtual account and bank transfer records. We do not ask for your wallet password or PIN to match a payment with your account.

Phone verification helps us confirm that the person requesting account access or a privacy change is connected with the account record. It can also help us investigate an unfamiliar session. We request only the verification step needed for that check, not your wallet credentials.

You can send a correction request through the account support route and identify the detail that needs changing. We may ask for an account contact or phone verification before making the change. This protects your record from an unauthorised edit and keeps the request auditable.

Cookies may keep your session and selected settings available, while device signals can help us detect unusual access. You can clear site data in your Android or iPhone browser settings. After clearing it, the account may ask for phone verification before access continues.

We retain account, support and payment-status records while they are needed for security, reconciliation, dispute handling or a legal duty. Once the relevant purpose ends, we delete or anonymise them where practical. A request can ask us to explain the category and purpose of a stored record.

Use the support path inside your account and describe whether your request concerns account details, a cookie, a device session or a DANA, OVO, GoPay or QRIS reference. Do not send passwords or PINs. We may confirm your account contact before sharing account-specific details.