Reference

puji388 Privacy Policy Explained Clearly

puji388 Privacy Policy explains what we collect when you open an account, use the mobile lobby and select DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
puji388 puji388 Privacy Policy Explained Clearly
CONTACT THE DESK

Browse Privacy Help Through Your Account

A clear contact path helps when your account details, wallet status or access request needs attention. We ask you to include the account identifier connected with your request, the device path you used and the relevant date, without sending a password or private wallet PIN. Our support route can check whether a request concerns login, phone verification, DANA or QRIS records, then explain the next step under this Privacy Policy.

Team online

Account request

Use the support path linked to your account when you need a copy, correction or clarification of personal data. Include your verified phone detail and the request category so we can match the enquiry without asking for your password.

Wallet record

If a DANA, OVO, GoPay or QRIS status appears incorrectly, tell us the rail, amount reference shown in your account and approximate time. We use those details to locate the payment record while keeping your wallet credentials out of the request.

Access concern

When login or phone verification stalls, contact us through the account support route and describe whether you used mobile or desktop. We can separate a device issue from a data request and explain what this Privacy Policy allows us to change.

DATA HANDLING

Switch Through Six Privacy Safeguards

We handle Privacy Policy requests around the actual account journey rather than treating every enquiry as a payment matter.

Collected details

We may collect your phone detail, account identifier, login timestamps, device type, browser signals and actions needed to load the…

Cookie choices

Cookies and similar device signals can help keep a session connected, remember a selected setting and show whether a page…

Account security

Phone verification is part of account access, and device or login signals can help us notice an unusual session.

Payment separation

A payment status is not the same as full wallet access.

Retention choices

We retain account and transaction-related records only for the period needed for account operation, security checks, dispute handling and applicable…

Change requests

You can request access, correction or clarification by giving your account identifier and the detail you want checked.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. We keep the wording practical: what we collect, why a device path matters, how wallet references are handled and how to contact us. For a case-specific answer, use the support path attached to your verified account.

The puji388 Privacy Policy covers account creation, phone verification, login activity, device signals, cookies, support requests and payment-status references. It explains how we use those records for access, security and account assistance, including activity connected with DANA, OVO, GoPay and QRIS.

We may collect your phone detail, account identifier, login timestamps, browser or device signals and details you send to support. If you use a wallet or bank route, we may retain a payment reference and status needed to match the transaction with your account.

Yes. The Privacy Policy covers the payment references and status details needed to reconcile DANA and QRIS activity with your account. It can also apply to OVO, GoPay, bank transfer and virtual account records, but we do not ask you to send a wallet PIN.

Phone verification links an account access request to the contact detail you provide and helps us distinguish an unusual login from a normal device session. We use the result for account protection and support checks; access depends on local law and the applicable account process.

You can ask for access, clarification or correction through the support path connected with your account. State the record or field you want checked and provide the account identifier. We may verify account control before responding, and some changes depend on local law.

Retention depends on the type of record and why we need it. Account, security, support and payment-status data may be kept for account operation, dispute handling and applicable legal duties. Ask support about a specific category and we will explain the relevant retention position.

Open the account support route and describe your Privacy Policy question in clear terms. Mention whether it concerns login, cookies, phone verification, DANA, QRIS or another record, plus the device path and date. Do not include your password, one-time code or wallet PIN.