Reference

puncak toto Privacy Policy Made Clear

puncak toto Privacy Policy explains how we collect, use and protect the details connected with your account, mobile browser and wallet activity.

Account dataWallet referencesCookie choicesAccess depends on local law
puncak toto puncak toto Privacy Policy Made Clear
CONTACT YOUR WAY

Get Policy Help Near Your Account

A clear contact path matters when you want to ask about your Privacy Policy rights or a wallet reference linked to your account.

Privacy questions Use our displayed support route to ask what personal data we hold, why we…
Wallet references For DANA, OVO, GoPay, QRIS or bank transfer questions, share the transaction reference rather…
Access requests If you want a copy, correction or clarification, state the exact request in the…
DATA HANDLING

What We Do With Your Details

We keep this Privacy Policy practical by tying each data use to an account or support task.

Account security

Phone verification helps us confirm that an access request belongs to you. We may use device and login signals to identify unusual activity, while your password remains yours to protect and should not be sent through support messages.

Cookie choices

Cookies can remember practical choices such as a session or language setting on your browser. You can manage browser cookie controls, although removing required cookies may affect login continuity and the way policy preferences are saved.

Payment references

We record references needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the correct account. We do not need your wallet PIN or banking password to investigate a reference.

Retention checks

We keep account, security and transaction records for as long as needed for the stated account, support and legal purposes. When a record is no longer needed, our handling follows the retention process applicable to that record.

Correction requests

You can ask us to correct inaccurate account details by using the listed contact path. We compare the request with your phone verification and account record before updating information, helping prevent an unrelated person from changing your details.

Policy contact

For a Privacy Policy question, identify your account and describe the data issue in plain terms. We will explain the relevant handling, request any necessary verification and tell you if local law affects the available response.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before account access. They explain what information connects to login, how wallet references are handled, what happens on a mobile browser and how to ask for a correction or copy. If your situation is unusual, use the contact path shown on our site and include only the details needed to identify your request.

It covers information linked to your account, phone verification, login activity, device signals, cookies and payment references. It also explains how we use those details for account access, security, support and transaction checks across DANA, OVO, GoPay, QRIS and bank routes.

We use your phone number to create and identify your account and to support the verification step before account access. It can also help us locate a correction request, but you should never send a password, wallet PIN or banking password to us.

Yes. The Privacy Policy applies when you use a mobile browser to sign in, move to the lobby or save cookie choices. Device and session signals may help protect access, while browser settings let you manage optional cookies and stored preferences.

We use transaction references and status details to connect a wallet action with your account and investigate an unclear payment record. We do not need your wallet PIN. For a question, provide the reference and registered phone number through our displayed contact path.

Yes. Send a clear correction request through the contact route shown on our site, naming the field that is inaccurate. We may use phone verification and account checks before changing it, so the request is handled for the correct account.

Ask for an account data copy through our displayed support route and describe the records you need, such as login or transaction references. We may need to confirm account ownership first, and the response depends on local law and the record involved.

Contact us through the policy support route listed on the site and ask which record type you mean, such as account, security or QRIS transaction data. We will explain the applicable retention handling and any legal reason that affects the response.