Reference

Open pagoda66 Privacy Policy With Clarity

The pagoda66 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesContact requests
pagoda66 Open pagoda66 Privacy Policy With Clarity
PRIVACY CONTACT

Ask About Data Through Our Support Path

A clear contact route helps you ask what we hold, why we use it and how an account record can be corrected. Use the support path shown in your pagoda66 account or policy page, and include the email or phone detail connected to your account so we can locate the right record without asking you to send a wallet password.

Team online

Account support

Send a privacy question through the account support channel when you need to check profile details, phone verification records or a sign-in record. We use the account identifier you provide to separate your request from another person’s data.

Wallet status

For DANA, OVO, GoPay or QRIS records, tell us which wallet or reference you are asking about and the approximate transaction date. Do not include a PIN, password or full authentication code in your message.

Policy request

Use the policy contact route to ask for a copy of your stored details, a correction or clarification about cookies. We may ask account questions before responding so private data is not disclosed to the wrong person.

DATA PRACTICES

Browse the Privacy Controls Behind Your Account

Privacy depends on practical handling, not a single statement. We separate account details from support context where possible, limit internal access to operational needs and use device signals to identify unusual sign-in…

Account details

We collect the details needed to create and maintain your account, including contact information and phone verification status. Keeping your profile current helps us match a privacy request to you and reduces confusion when access is checked.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, status and timing record. We use that payment context to trace a requested account action, while wallet PINs remain outside our requested support details.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly on your mobile browser. You can manage browser cookie controls, although switching them off may affect account access steps.

Device security

We may record device type, browser signals and sign-in time to help identify unusual access. If your phone changes or a login looks different, complete the account checks shown on screen and contact support if the record is not yours.

Record retention

We keep records for as long as needed for the stated service purpose, account security, dispute handling or a legal requirement. When a record is no longer needed for those reasons, our handling process allows it to be removed or separated.

Change requests

You can ask us to correct profile data, explain a processing purpose or provide available account records through the policy contact route. We may verify your identity first, and access to a request depends on local law.

Find Answers About Privacy Policy Access

These questions address the privacy points you are most likely to check before opening an account or connecting an Indonesian wallet. If your situation is different, send the account detail and request type through our policy contact path.

The pagoda66 Privacy Policy covers account details, phone verification, device and sign-in records, cookies, support messages and wallet references. It explains why we use those records, how long they may be kept and how you can ask about correction or access.

Our privacy process does not ask you to send a DANA or QRIS PIN through support. We may retain a payment reference, status and timing connected with an account action, but you should keep wallet PINs, passwords and authentication codes private.

Use the policy contact route shown on the account or Privacy Policy page and identify the email or phone detail linked to your account. Tell us whether you want a copy, an explanation or a correction; we may verify ownership before responding.

Device and browser details help us recognise unusual sign-in patterns, keep a session working and investigate an access problem. They can include device type, browser signals and sign-in time, rather than your wallet PIN or the contents of your private device.

You can ask us to correct account details or explain whether a record can be removed through the policy contact path. Some records may remain for account security, dispute handling or legal needs, and the result depends on local law.

Cookies may keep your session active and remember selected settings on the browser you use for account access. You can adjust cookie controls in your browser, but blocking required cookies may interrupt sign-in or make certain account steps unavailable.

This Privacy Policy explains our handling of account, device, cookie and wallet records for the service. Whether you can access the service or make a specific request depends on local law, so contact support if your Indonesian situation needs clarification.