Reference

Open the pucuk11 Privacy Policy

The pucuk11 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access the lobby from your phone.

Account dataWallet recordsDevice choicesContact route
pucuk11 Open the pucuk11 Privacy Policy
CONTACT ROUTES

Choose a Clear Policy Contact Path

A direct request helps us connect your Privacy Policy question to the correct account record. Use the account help route when you need to ask about a phone number, wallet reference, device signal or support message. Include the email or phone detail attached to your account, but never send a password, wallet passcode or one-time verification code. We check the request before changing data, especially when it concerns a payment record or a new device.

Team online

Account help

Use the account help route beside the cashier area for a Privacy Policy request. We can help you identify the data linked to your account, check a phone verification record, and explain the next step without asking for your DANA, OVO or GoPay passcode.

Wallet status

If a QRIS, bank transfer or virtual account reference appears incorrectly, send the date, amount reference and wallet name through support. We use those details to locate the record, while keeping your bank login, wallet PIN and one-time code outside the request.

Login concern

A new phone or browser can create a security question during account access. Tell us which device path you used and when the issue started. We can explain the data signal involved, confirm the account step, and direct you to a safer sign-in reset.

DATA PRACTICES

Explore How We Protect Your Records

We keep the Privacy Policy practical: each record has a reason connected to account access, payment matching, security or support.

Account details

We may collect your name, contact detail, phone verification result and account activity needed to provide access. These fields help us identify the correct account when you ask about a correction or request a copy of your stored personal data.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction can create a reference, status and time record. We use those fields to match your cashier request, not to obtain your wallet password, bank login or private PIN.

Cookies and devices

Cookies and similar device signals can remember a sign-in choice, maintain a session and flag an unfamiliar browser. On mobile, clearing site data may remove the saved session, so you may need to complete phone verification again.

Security checks

We compare login timing, browser details and device changes when an account access attempt looks unusual. This can pause a request for confirmation. We will not ask you to disclose a password, wallet PIN or one-time code during that check.

Retention timing

We retain account, payment and support records for as long as needed for the stated service, dispute handling, security review or applicable legal duty. When a record is no longer needed, our process removes it or separates it from direct account identifiers.

Your requests

You can contact us to ask for access, correction, clarification or deletion where that request is available under applicable rules. Include your account contact detail and the exact record you mean; we may verify ownership before making any change.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and wallet questions we hear most often before access begins. They explain what happens during phone verification, why payment references appear, how device cookies work, and how to contact us about your personal data. If your situation is different, send the account help request with the relevant reference.

The pucuk11 Privacy Policy covers data collected during account creation, phone verification, sign-in, lobby access, wallet matching and support contact. It also explains cookies, device signals, retention, security checks and the requests you can make about access, correction or deletion.

Phone verification helps us connect an account to the correct contact detail and reduce mistaken or unauthorised access. We record the verification result and related account step, but you should never send us the one-time code, password or wallet PIN in a support message.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. We use those details to match a cashier event to your account and do not need your private wallet credentials.

We may receive browser type, device signals, session details and login timing used for access, continuity and security checks. We do not need to read personal files or contacts for these functions. Clearing cookies can end your saved session and prompt another account check.

Retention depends on why the record exists, such as account service, payment matching, support history, security review or a legal duty. We keep it for the applicable period, then remove it or separate it from direct identifiers when the reason ends.

Send an account help request stating the contact detail on your account and the record you want corrected, accessed or deleted. We may ask for an ownership check before changing anything. For a wallet issue, include the transaction date and reference, never a PIN.

Yes. Account access and certain data requests depend on local law and may vary by location. We apply the Privacy Policy to the data we handle, while specific rights, retention duties and available account actions can differ where local law permits.