Reference

puncak303 Privacy Policy For Your Account

Our puncak303 Privacy Policy shows what we collect when you open an account, sign in, use DANA or QRIS, and browse titles such as Andar Bahar.

DANA recordsCookie choicesAccess requests
puncak303 puncak303 Privacy Policy For Your Account
CONTACT ROUTES

Ask Us About Your Privacy Policy

A direct request helps us resolve a data question without sending your account details through an open chat.

Privacy request Send a request through the privacy contact route in account help. We use your registered phone number to locate the account and may ask for a verification step before releasing personal records.
Wallet record check For DANA, OVO, GoPay or QRIS questions, provide the transaction reference rather than a wallet password. We compare the reference with our ledger and explain the record connected to your account.
Access assistance If you cannot sign in to submit a request, tell us the device path you used, such as an Android browser or desktop browser. We use those details to verify the access event.
DATA PRACTICES

Cookies, Security And Account Access

We keep this policy practical: the same account steps that protect your sign-in also help us answer a data request accurately.

Account details

We use your registered phone number, verification status and sign-in events to maintain the account record. Before changing or disclosing that record, we check that the request comes from the account holder.

Transaction records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are kept with the related account entry. We use them to reconcile receipts, investigate wallet status and answer record questions.

Device signals

An Android browser, iPhone browser or desktop session can create technical logs such as IP address, browser type and security events. These signals help us identify unusual access without reading unrelated device content.

Cookie controls

Cookies help preserve sign-in state and remember selected site settings. You can manage browser cookie controls, although turning them off may affect account access and prevent us from keeping your selected preference.

Retention periods

We retain account, security and transaction records only for the period needed for the stated purpose, dispute handling or a legal duty. When a record is no longer needed, our process removes or anonymises it.

Change requests

You can ask us to access, correct or clarify personal data through the privacy contact route. Include the requested change and registered phone number; we verify ownership before making an account update.

Privacy Policy Questions For Your Account

These answers cover the searches we receive most often about the puncak303 Privacy Policy. They focus on account records, wallet references, cookies, device access and requests for changes. If your case involves a specific receipt or sign-in event, use the privacy contact route and include only the details needed to locate it.

It covers account details, verification records, device and browser logs, cookies, game session records, payment references and support requests created when you use puncak303 where local law permits.

DANA and QRIS references help us match a deposit or receipt to the correct account. We use the reference for reconciliation and status checks, not to request your wallet password.

Yes. Send an access request through the privacy contact route in account help, include your registered phone number and state which record you need. We verify ownership before responding.

Describe the inaccurate field and the correction you want, then submit it through the privacy contact route. We may request an account verification step before changing your registered details.

Yes, cookies may preserve sign-in state and selected settings on an Android browser. Your browser controls can restrict them, but sign-in and saved preferences may then work differently.

Retention depends on the record, its support or dispute purpose and any applicable legal duty. When continued storage is no longer needed, we remove or anonymise the record.

Use the privacy contact route shown in account help and explain that sign-in is unavailable. Include your registered phone number and device path, but never send a password or wallet PIN.