Reference

puma33 Privacy Policy for Your Account

Our Privacy Policy shows exactly how puma33 handles the details connected to your account, mobile browser and wallet activity, including DANA, OVO, GoPay and QRIS selections.

Account dataWallet choicesDevice controlsYour requests
puma33 puma33 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy Policy

A clear contact route helps when you want to understand a record, correct an account detail or ask how a wallet reference is used.

Account contact Use the support contact inside your signed-in account for a Privacy Policy question.
Wallet status If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date, amount…
Access concern For a device or login concern, tell us whether you used a mobile browser…
DATA PRACTICES

What We Do With Your Account Records

Privacy choices work best when the handling steps are visible before you open an account.

Account details

We use the name, phone detail and other fields you submit to create and maintain your account.

Wallet references

A DANA, OVO, GoPay or QRIS selection can create a reference, status or receipt record.

Cookies

Cookies and similar device storage can remember a session choice or help us understand whether a login step has completed.

Device security

We may record browser, device and session signals to spot unusual account access.

Retention period

We keep personal and transaction records for as long as needed for the stated service purpose, account support or applicable…

Change requests

You can ask us to correct inaccurate account details, explain a data use or assess a deletion request through the…

Privacy Policy Questions About puma33

These Privacy Policy answers address the account, device and payment-record questions you may have before opening an account or when checking an existing session. If your situation is not covered, use the signed-in support contact and describe the exact account step involved.

It covers account details, phone verification, device and browser signals, cookies, support messages, and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your phone detail to create or verify the correct account, respond to account requests and investigate unusual access. We do not need your wallet PIN to match a payment reference.

Yes. The Privacy Policy includes technical records from the mobile browser path from login to the lobby, such as session signals and completed account steps. Browser cookie controls remain available on your device.

We may receive a wallet name, transaction reference and status needed to connect a DANA or QRIS request with your account. We use those details for matching, support and required record keeping.

Yes. Contact us through the signed-in account support path and state whether you want a correction, an explanation of data use or an assessment of removal. We verify account ownership first.

Retention depends on the purpose of the record, account support needs and applicable legal duties. We remove or separate data when it is no longer needed for those stated reasons.

Access depends on local law and is available where local law permits. If you need a location-specific answer, contact us from your account and include your current access context.