Reference

puma 128 Privacy Policy and Your Data

Our Privacy Policy explains how puma 128 handles the account details you provide, including your phone verification, wallet status and device access records.

Clear data purposesWallet record contextAccount access controlsPolicy questions welcome
puma 128 puma 128 Privacy Policy and Your Data
POLICY HELP PATH

Where Privacy Questions Meet Wallet Support

A clear support route helps you act on this Privacy Policy instead of guessing which account screen to use.

Account access Use the support chat when a phone verification step, device sign-in or account detail…
Wallet records For DANA, OVO, GoPay or QRIS questions, include the visible reference and date from…
Policy changes Ask the support chat to record a correction, access request or removal question.
DATA CONTROL ROOM

How We Protect Your Account Records

We handle privacy as part of the account path, from the first phone check to a later wallet-status question.

Account details

We use your contact and verification details to create, secure and maintain account access. A phone check can connect a request to the right account, while your password remains something you enter privately rather than share with support.

Cookies and sessions

Cookies can remember a session, language choice or device preference so you do not repeat the same step on every visit. You can manage browser cookie settings, although disabling some cookies may interrupt login or policy access.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a cashier event with your account history. We use the reference for checking status and do not need your wallet PIN.

Account security

We record sign-in time, device signals and selected access events to identify unusual account behaviour. If a login looks different, we may request phone verification before discussing account data or changing an account detail.

Retention periods

We keep account, support and transaction records only for the period needed for service handling, dispute checks, security work or legal duties. When a record is no longer needed, our process is to remove it or separate it from direct account identity.

Your requests

You can ask what personal details we hold, request a correction, ask about deletion, or question a processing purpose through support chat. Include your account phone detail so we can verify the request before changing private records.

Privacy Policy Questions Answered

These Privacy Policy answers cover the account actions Indonesian customers ask about most often. They explain what happens when you open an account, use a local wallet, change devices or contact us about stored data. If your case is not listed, use the support path beside the cashier and mention the exact account step that concerns you.

The puma 128 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and ways to request access or correction.

We use your phone number to create and identify your account, complete the phone verification step and help protect access when a device changes. Support may use it to locate your request, but you should never send your password, wallet PIN or one-time security code.

Yes. The Privacy Policy covers the transaction references and status details returned when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These details help us match a cashier event to your account without storing your wallet PIN.

Open the support chat beside the cashier and ask for a data access or correction request. Include your account phone detail and describe the record you want checked. We verify account ownership first, then explain the available response and any record that must remain.

You can ask puma 128 to remove personal details through support chat. We assess the request against active account needs, security checks, transaction disputes and legal duties. Where a record must remain, we explain the reason and remove or separate it when that period ends.

A new phone or browser can create a different device signal in our access records. We may ask for phone verification before discussing private account details or changing settings. Cookies may also need to be accepted again, while your stored account history remains linked to the verified account.

Yes. Access and eligibility for services depends on local law, and this Privacy Policy applies where local law permits. You can read it from the account menu or ask support chat about a specific section before continuing with phone verification or wallet-related steps.