Reference

puma35 Privacy Policy for Your Account

The puma35 Privacy Policy explains how we handle your account details, phone verification, device signals and wallet records when you use our Indonesia service.

Clear data purposesWallet record contextAccount access stepsIndonesia policy wording
puma35 puma35 Privacy Policy for Your Account
CONTACT THE DESK

Ask About Your Privacy Policy Rights

A direct support route helps you ask about the Privacy Policy without searching through unrelated pages.

Account data request Ask us which account details we hold and why they appear in your record.
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the transaction reference, date and…
Access problem When login or phone verification stalls, use the account help link beside the cashier…
DATA HANDLING DETAILS

What We Do With Your Account Data

We separate practical account operation from unnecessary collection. Login events, phone verification and transaction references help us confirm that the right person is using the account; cookie data helps the page remember…

Account details

We may handle your phone number, verification result and account activity so sign-in and account assistance can work. A clear phone verification step links access to the correct account, while support can use the same record to investigate a failed login.

Cookie choices

Cookies and similar browser storage can preserve session settings and help us understand page performance. You can manage browser cookie controls on your device, although turning them off may affect sign-in continuity or the way policy pages load.

Security signals

We may examine device type, browser version, login time and unusual access patterns when protecting an account. These signals help us respond to a verification problem without relying only on a payment reference or asking for your secret credentials.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be matched with the account action that created it. Bank transfer and virtual account records may be checked for status and reconciliation, while full wallet passwords and banking login details are not needed for this purpose.

Retention period

We retain account and transaction records for the period needed to provide account support, resolve disputes, protect against misuse and meet applicable legal duties. When a record is no longer needed for those reasons, our handling process considers removal or further restriction.

Change request

You can ask us to correct inaccurate account data, explain a record or assess a deletion request. Send the request from your account support route, identify the relevant phone number or receipt, and state the change clearly so we can assess it under the Privacy Policy.

Privacy Policy Answers for puma35

These Privacy Policy answers focus on the questions you are most likely to have before opening or using an account in Indonesia. They cover the data connected to login, phone verification, cookies and local wallet records, along with the practical route for asking us to inspect or change a record. If your situation involves a particular receipt or access event, include that reference when contacting account support.

The puma35 Privacy Policy covers account details, phone verification, login and device signals, cookie activity, support messages and transaction references. It explains why we use those records for access, wallet reconciliation, security and account assistance, including activity connected with DANA, OVO, GoPay and QRIS.

We use your phone number to create and identify your account and to complete the clear phone verification step before account access. It also helps support locate the correct record when you ask about login, a QRIS receipt or a wallet-status issue.

Yes. The Privacy Policy covers transaction references and status records linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those details to match an account action and investigate a receipt, not to request your wallet password.

Use the signed-in account support path and state whether you want a copy, correction or another request assessed. Include the verified phone number and, if relevant, a transaction reference. We may need to confirm account ownership before discussing the record.

We keep account, security and transaction records for as long as they are needed for account support, reconciliation, misuse prevention, disputes or applicable legal duties. The period can differ by record type. You can ask support to explain the reason for retaining a particular entry.

Yes. Your mobile browser provides cookie controls that let you remove or restrict stored data. Cookies may help preserve a session or page setting, so changing them can affect sign-in continuity. Our Privacy Policy explains their purpose, while your browser manages the setting.

Contact us through the account support route linked beside the cashier area, or use the access-help path if you cannot sign in. Describe the Privacy Policy concern, add the relevant account or receipt reference and never include a password or full banking credentials.