Reference

puncak138 Privacy Policy for Indonesia Accounts

puncak138 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity contextAccount access choicesMobile session controls
puncak138 puncak138 Privacy Policy for Indonesia Accounts
PRIVACY SUPPORT

Contact us when a privacy question stalls

A clear support route helps when you cannot identify a record or want to change an account detail. Use the support request path inside your account and include the relevant sign-in or wallet reference without sending a full password. We use the details you provide to locate the issue, verify ownership and reply about the Privacy Policy request rather than opening unrelated account activity.

Team online

Account help path

Start from the account help area when a profile detail, verification record or sign-in event looks unfamiliar. We can connect the request to the right Privacy Policy process after checking account ownership.

Wallet status query

For DANA, OVO, GoPay or QRIS references, send the receipt identifier and date through support. We use that limited context to check the record without asking you to disclose a wallet password.

Privacy request

Ask us to access, correct or clarify personal data through the account support route. We may request an account step first so changes are not made by an unauthorised person.

DATA CONTROL

Check your account security and data controls

We apply the Privacy Policy to the practical moments that matter: account creation, phone verification, mobile sign-in, wallet checks and support conversations.

Account records

When you open an account, we collect the details needed for account access and phone verification. We use them to identify your profile, protect sign-in activity and respond to requests about your stored data.

Device signals

A mobile browser may provide session, device and security signals when you sign in. These help us recognise unusual access and maintain the correct account session without treating device data as your wallet password.

Cookie choices

Cookies and similar storage can keep a session working and help us understand whether a page request belongs to your account. You can manage browser controls, though restricting them may affect sign-in and policy access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data. We use those references for matching, checks and support, not for collecting a wallet credential.

Retention approach

We keep account, security and support records only for the period needed for the stated purpose, account protection or legal duties. When a record is no longer needed, our process addresses deletion or restriction.

Change requests

To request correction, access or clarification, use the account support route and describe the record. We may confirm your identity before changing details, and access depends on local law.

Find answers about puncak138 Privacy Policy

These Privacy Policy answers address the searches we hear around account data, wallet references, cookies and access requests. If your situation is not covered, send a focused request through account support with the smallest useful detail. We will use that context to identify the relevant policy path.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access with the correct person, reduce unauthorised sign-ins and handle account requests safely. The record is handled under the Privacy Policy and applicable local requirements.

Yes. It explains that DANA and QRIS references may be used to match a wallet event, check a receipt or answer support questions. We do not ask for your wallet password through this process.

Use the support request path inside your account, describe the record you want reviewed and provide a safe reference such as a date. We may verify ownership before releasing or changing personal data.

Cookies and similar storage can keep your mobile browser session active and help connect a request to the right account. Browser controls can restrict them, although sign-in or policy access may then be affected.

We retain account, security, payment-reference and support records for the period needed for their stated purpose, account protection or legal duties. The applicable retention decision can depend on local law.

Start with the account support route and state whether your request concerns access, correction, deletion, cookies or a wallet reference. Please omit passwords and unnecessary financial credentials from your message.