Reference

Open petir62 Legal access terms

petir62 Legal terms set out how account access, DANA and QRIS records, cookies, and personal data requests are handled.

Account conditionsWallet recordsData requestsCookie choices
petir62 Open petir62 Legal access terms
CONTACT ROUTES

Contact us about Legal account questions

Questions about Legal terms are easier to resolve when you include the account step, payment rail, and message shown on screen.

Account access Tell us whether phone verification, login, or an eligibility message stopped you.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, include the receipt…
Data requests Ask through account help when you need a copy, correction, or removal request considered.
DATA PRACTICES

Switch to clear Legal data controls

We treat Legal handling as an operating process rather than a label on a page. Account details are connected to phone verification, wallet status, device signals, and payment references so we can…

Data collection

We use registration details, verified phone data, device signals, and payment references for account access, security checks, receipt matching, and support replies. We do not ask you to send unrelated personal material.

Cookie choices

Cookies can help keep an account session working and remember essential settings. Your browser controls whether optional cookies remain, while necessary session records may still operate when you return to the account path.

Account security

Keep your phone access private and check the account name before using DANA, OVO, GoPay, QRIS, or bank transfer. If a device or login looks unfamiliar, contact account help before changing payment details.

Record retention

A closure or removal request does not always erase every record immediately. Payment reconciliation, disputed receipts, security checks, and a legal duty can require limited retention for a defined operational purpose.

Correction requests

If your name, phone detail, or wallet status is wrong, send the requested correction through account help. Include only the affected field and the account step where the mismatch appears.

Who responds

Our account support route handles questions about Legal conditions, data access, cookies, and payment records. Include your account reference and avoid sharing a password, wallet PIN, or full security code.

Browse Legal answers before opening an account

These Legal answers focus on the questions we expect you to ask before account creation, phone verification, or a payment record. We keep the wording practical so you can identify the next account step, understand a data request, and contact us with the right details when access depends on local law.

Legal covers account conditions, phone verification, payment records, cookies, data handling, security checks, retention, and contact rights. It also explains that access depends on local law and may vary by eligible Indonesia region.

No. Access depends on local law, so the Legal page cannot override a restriction that applies to your location. Check the message shown during account access and contact support if you need clarification.

We use wallet status, receipt references, and account details to match a payment record and resolve a cashier question. Use your own wallet details, and ask account help about a specific record.

Yes, send the request through account help with your account reference and the field concerned. We may verify ownership first, then explain the available response and any reason a record must remain.

Legal handling may require limited retention for payment reconciliation, disputed receipts, security checks, or a legal duty. We keep the purpose narrow and can explain the relevant retention reason through support.

Essential cookies can support a working session and required settings, while optional cookies depend on your browser choices. If access behaves differently after clearing cookies, check the account path again.

Use the account help route shown inside your account and include the affected step, such as phone verification, QRIS receipt status, or a data correction. Never send a password, wallet PIN, or security code.