Reference

Open putra62 Privacy Policy Before Account Access

Our putra62 Privacy Policy explains what account, device and payment details we use when you open the lobby, including records linked to DANA, OVO, GoPay and QRIS.

Account dataCookie choicesPayment recordsAccess requests
Explore Our Lobby Read FAQ
putra62 Open putra62 Privacy Policy Before Account Access
CONTACT PATHS

Ask About Privacy Through Your Account

A clear contact path helps you act on the Privacy Policy without sending personal details into an unrelated channel. Start with the support route shown after sign-in, describe the request in plain English, and include only the account reference needed to locate your record. We may ask for a verification step before discussing account data, changing a detail or confirming a deletion request.

Team online

Account support

Use the support path inside your signed-in account for a Privacy Policy question. We can explain which record is involved, confirm the request category and tell you what verification step is needed before we disclose account-specific details.

Cashier records

If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, point us to the cashier receipt and its status. We use that reference to separate a payment record from unrelated lobby activity.

Access request

Ask for a copy, correction or removal through the account support route. We record the request, check that it comes from the account holder and explain any retention reason or local-law condition before completing the next step.

DATA PRACTICE

Check How We Handle Your Data

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Account details

When you open an account, we use the details submitted during the account step and the phone verification result to create an identifiable record. We do not treat a casual visit to the lobby as the same as a verified account action.

Device signals

A phone or desktop session can produce sign-in time, browser or device signals and security events. These details help us investigate an unusual login or repeated verification attempt without requiring you to describe every device used.

Cookie controls

Cookies can remember selected settings and support account continuity on the same device. You can review browser controls or the available cookie prompt, although removing cookies may require another sign-in or make certain preferences unavailable.

Payment matching

A DANA, OVO, GoPay or QRIS reference is handled as a transaction record linked to the relevant account step. Bank transfer and virtual account references may be checked against the receipt and status you provide to support.

Security checks

Before we reveal account data or change a personal detail, we may compare your request with phone verification and recent sign-in information. This step reduces the chance that a person using your device can obtain your account records.

Retention requests

We retain some records for security checks, transaction disputes or legal duties, even after a request to remove other details. Ask support which category applies, and we will explain the reason and any available restriction.

Find Privacy Policy Answers Quickly

These Privacy Policy answers cover the account questions we expect before you open access from Indonesia. They explain what to prepare, how payment references are treated, what cookies do and how to reach us when a request needs account-level checking. If your situation is different, use the signed-in support path and ask us to apply the policy to your specific record.

The putra62 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It also explains access, correction, deletion and retention requests, including situations where the outcome depends on local law.

Use the support route inside your signed-in account and ask for a data copy under the Privacy Policy. Include your account reference, complete the requested verification step and specify whether you need account, device, cookie or payment records.

Yes, you can ask support to correct an inaccurate account detail. We first confirm that the request comes from you, identify the affected record and explain whether a phone verification or payment reference must remain unchanged for security or transaction handling.

DANA and QRIS activity can create a reference, amount, status and timing record connected to your account step. We use those details to match receipts and investigate disputes. Ask support about a specific entry rather than sending full wallet credentials.

It explains that cookies may remember selected settings and help maintain a session on your phone or desktop. Browser controls can remove them, but you may need to sign in again. Cookie removal does not automatically erase account or payment records.

Retention depends on the record and why it is needed. Security events, payment references and dispute material may remain for account protection or legal duties. Contact support with the record type, and we will explain the applicable retention reason.

You may submit a deletion request through account support. We verify the requester, identify the data and explain what can be removed. Some records may need to remain for security, transaction disputes or legal duties where local law permits.

Related Pages

putra62 Indonesia bola009 asian99 rajabaccarat Access guide