Reference

Terms & Conditions Before Account Access

Clear account steps, DANA and QRIS references, and a defined route for wallet questions are set out in the petir36 Terms & Conditions.

Account stepsDANA and QRISLocal-law wording
petir36 Terms & Conditions Before Account Access
CONTACT ROUTES

Contact Us About Account Terms

Questions about the Terms & Conditions should reach the support route connected to your account, because we need to match policy requests with the correct login and transaction record.

Account access If phone verification or a login step stops your account request, contact us through the signed-in support route. Tell us which step appeared and the device used, so we can connect your question to the relevant Terms & Conditions clause.
Wallet status For DANA, OVO, GoPay or QRIS questions, open the support path beside the cashier area and attach the payment receipt or reference. We use those details to separate a policy question from a pending wallet-status check.
Policy requests To ask about a clause, account closure, or a change to your stored details, send a written request through the account contact route. We will identify the requested policy action and explain any verification needed before making a change.
DATA PRACTICE

How We Handle Terms Data

The Terms & Conditions explain how we connect account records, payment references, and security checks when a policy request is made.

Account details

We use the details submitted during account creation and phone verification to identify your account and apply the relevant terms. If your name or contact detail is incorrect, request a correction through the signed-in support path.

Payment records

A DANA, OVO, GoPay or QRIS reference may be connected to a transaction query. We use the receipt number and account record to check status, rather than asking you to send an unnecessary full wallet password.

Cookies

Cookies can preserve sign-in state, language settings, and page preferences on your browser. The Terms & Conditions explain their policy role; clearing them may require you to complete login or phone verification again.

Account security

Keep your password, verification messages, and device session private. If you suspect another person accessed the account, contact us through the account route promptly so the security request can be tied to the correct record.

Retention requests

You may ask how a specific account or transaction record is retained and why it remains connected to the policy. We assess the request against applicable terms and local requirements before confirming a deletion or retention step.

Policy changes

When we amend the Terms & Conditions, we publish the revised wording through the site and identify the effective point where practical. If you need a prior clause checked, contact us with the date you accepted it.

Terms & Conditions Questions for petir36

These Terms & Conditions answers focus on the decisions you make before opening an account: what acceptance means, how local wallets fit the agreement, and where to send a policy request. Read the clause itself as well, because account eligibility and available payment choices can differ where local law applies.

They cover account creation, phone verification, login security, wallet transactions, policy changes, account closure, data requests, and dispute handling. The terms also explain how DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may be used when checking a transaction.

Yes. You should read and accept the Terms & Conditions before completing the account path and phone verification. If you do not accept them, do not continue with account access. Eligibility depends on local law and the location connected to your request.

Only payment choices displayed for your account may be used. The Terms & Conditions apply to DANA, OVO, GoPay and QRIS references, as well as bank transfer or virtual account steps. Keep your receipt because support may need it for a status check.

Send a written request through the signed-in support route and identify the account detail you want corrected. We may ask for phone verification or another account check before changing it, so the request is connected to the right account record.

We publish revised wording through the site and indicate when the change applies where practical. Read the updated clause before continuing. If you need an earlier version checked, contact us with the date or transaction reference linked to your question.

Access may be paused when account details cannot be verified, security concerns arise, or a payment record needs clarification. We use the contact route to explain the next policy step where possible. Account access depends on local law and applicable account conditions.

Use the support contact path shown after login, or the route beside the cashier area for a wallet-related clause. Include the section topic, account identifier, and any DANA, OVO, GoPay or QRIS receipt reference so we can respond to the correct policy question.