Reference

Privacy Policy for Your Indonesia Account

paus55 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status beside titles such as Live Blackjack…

Clear data purposesWallet record controlsAccount access choicesPolicy request path
paus55 Privacy Policy for Your Indonesia Account
HELP WHEN NEEDED

Get Privacy Help Beside Cashier Steps

A privacy question should not require you to search through unrelated pages.

Account request Ask about your stored account details through the support path shown after login.
Wallet record For DANA, OVO, GoPay, QRIS or bank transfer records, send the transaction reference and…
Access concern If a privacy request follows an unusual sign-in or a stalled cashier status, contact…
SECURITY PRACTICE

Account Security From Login To Retention

Our privacy process follows the same account path you use to reach the Indonesia Mobile Lobby 504: identify the account, check the request, then apply the permitted action.

Data collected

We may receive account contact details, sign-in events, device signals and payment references. These fields help connect your request to the right account and detect access activity that needs checking.

Cookie choices

Cookies can preserve sign-in state, language preference and basic page behaviour on your phone or desktop. You can manage browser cookie settings, though switching them off may affect account access.

Login protection

Clear phone verification can be required before account access or a sensitive request is completed. We use that step to reduce mistaken changes when a device or login pattern differs.

Payment matching

A QRIS receipt, virtual account reference or bank transfer code is used to check a payment record, not to request your wallet password. We keep the matching fields limited to that task.

Retention timing

We retain records only for account operation, security checks, dispute handling or legal needs that apply to the request. When no valid need remains, records are removed or access is restricted.

Change requests

You can ask us to correct inaccurate account details, explain a data use or restrict a record where available. Send the request through support with enough detail for us to locate it.

Privacy Policy Questions About paus55

These Privacy Policy answers address the account questions you are most likely to have before opening access from Indonesia. They cover wallet records, cookies, deletion requests and the identity check used to protect your account. If your case involves a specific QRIS, DANA or bank transfer reference, use the support route beside the cashier area so we can locate the correct record.

The paus55 Privacy Policy covers account details, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how access is controlled, how long records may remain and how you can ask about correction or restriction.

For QRIS, we may receive a transaction reference, amount status, time and confirmation fields returned by the payment flow. We use those details to match the record to your account. We do not ask for your QRIS wallet password or private wallet conversation.

You can contact support through the account route and ask which personal records are held for your account. We first confirm the request is yours, then explain what can be provided or restricted under the rules that apply where local law permits.

Send a correction request from the support path shown after login and identify the field that is wrong. We may use phone verification before changing a contact detail, especially when the request comes from a new device or follows unusual sign-in activity.

Yes. The Privacy Policy explains that cookies can preserve sign-in state, language preference and basic page behaviour on mobile and desktop. Your browser controls those files, but disabling them may interrupt account access or require you to sign in again.

You can ask us to remove or restrict personal data through support. We assess the request against account security, payment matching, dispute handling and legal needs. Where a record must remain, we explain the reason and limit its use to that purpose.

Use the support route connected to your account and include a clear subject such as Privacy Policy, wallet record or cookie request. Add the relevant transaction reference when needed, but never send a wallet password. Access and eligibility depend on local law.