Reference

puma33 Privacy Policy for Your Account Data

puma33 Privacy Policy explains what we collect when you open an account, move through the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet reference detailsWhere local law permits
puma33 puma33 Privacy Policy for Your Account Data
PRIVATE HELP

Privacy Help Beside Your Account Path

A clear support route matters when a privacy question appears beside a login or wallet issue.

Account questions Ask about phone verification, login records or the account details held for you. Include the email or phone reference connected with your account, but never send your password.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the payment date, amount reference and status shown beside the cashier path. We use those fields to trace the relevant record.
Data changes Request a correction or deletion assessment through our privacy contact path. We may ask for account checks before changing personal data, helping prevent another person from altering your records.
DATA PRACTICE

How We Keep Account Data Controlled

We handle this policy area through practical account controls rather than vague promises. Phone verification connects an access request to the right account, device signals help us spot unusual sessions, and cookie…

Account data

We use contact details and phone verification results to create, secure and maintain your account. You can ask what account data is associated with your login through the privacy support path.

Cookie choices

Cookies can remember session settings and help us understand whether pages load correctly. Your browser controls whether optional cookies remain, while required session cookies support account navigation.

Device signals

Browser type, device markers and login timing may be recorded for security checks. These signals help us investigate an unfamiliar session without treating a device marker as your password.

Wallet references

DANA, OVO, GoPay and QRIS records may include a reference, status and timestamp rather than your wallet password. We use these fields to reconcile a payment question with your account.

Retention approach

We retain account, security and payment records for as long as needed for account operation, dispute handling, lawful duties or a documented request assessment, then remove or restrict them where appropriate.

Request route

Contact our privacy support route to ask for access, correction or deletion assessment. Tell us which record concerns you, and we may verify account ownership before responding.

Privacy Policy Questions for puma33 Accounts

These Privacy Policy answers address the account, device and wallet questions we expect from Indonesian account holders. If your situation is not covered, use the privacy support path with the relevant account step and payment reference, where applicable.

It covers account details, phone verification, login and device records, cookies, payment references and requests about access, correction or deletion. It also explains when data may support security, payment handling or lawful requests.

Phone verification helps connect account access to the person opening the account and can reduce mistaken or suspicious access. We record the verification result and use it for account security and support checks.

Yes. The Privacy Policy covers payment references, status and timing connected with DANA, OVO, GoPay and QRIS. We use those fields to trace a receipt or stalled wallet status without requesting your wallet password.

We may record browser type, device markers, login timing and page paths linked with account activity. These details help us investigate unusual sessions, protect access and diagnose a page issue.

Use our privacy support route and identify the account record you want assessed. We may ask you to confirm account ownership before responding, so another person cannot obtain or alter your personal data.

Yes. Send a correction request through the privacy contact path and explain which detail is inaccurate. We may verify the account, compare supporting records and then update or restrict the relevant data where appropriate.

We keep these records for as long as needed for account operation, security checks, dispute handling, lawful duties or a request assessment. After that, we remove or restrict them where appropriate.