Reference

paus188 Privacy Policy for Your Account

Our Privacy Policy explains what paus188 collects when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPrivacy requests
paus188 paus188 Privacy Policy for Your Account
PRIVACY HELP PATH

Where To Ask About Your Data

A clear contact path matters when you need to ask about personal data, an account record or a wallet reference.

Account access If phone verification or sign-in blocks a privacy request, use the support route beside login. We can identify the account step involved without asking you to post private details in an open message.
Wallet records For a DANA, OVO, GoPay or QRIS reference, contact support through the cashier path and provide the transaction reference. We use that detail to locate the relevant record and explain its handling.
Data requests Ask us to access, correct or remove eligible personal data through the available support contact. We may verify account ownership first, then explain what action can be taken under local requirements.
HANDLING YOUR RECORDS

How We Manage Privacy Requests

We keep this policy practical by linking each privacy choice to a real account event: login, phone verification, device use, wallet status or support contact.

Account details

When you open an account, we handle the details needed to create access and complete phone verification. Keeping those fields accurate helps us match a privacy request to the correct account.

Device signals

A phone or desktop session can create login, browser and device signals. We use these details to recognise unusual access, protect the account path and investigate a sign-in concern you report.

Cookies

Cookies and similar storage can remember sign-in choices, page preferences and session activity. You can manage browser permissions, although changing them may affect access to account pages or policy controls.

Wallet references

Payment records may show a wallet name, bank route, amount reference or status needed for reconciliation. We handle DANA, QRIS, OVO, GoPay and bank references for that operational purpose.

Retention

We retain records only for the period needed for account security, support handling, transaction reconciliation or legal duties. When a record is no longer needed, our handling process addresses its removal or restriction.

Changes and contact

To request a correction, copy, restriction or eligible removal, contact us through the support route beside login. Tell us the account step and request type; ownership checks may be required.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we expect before account access, including phone verification, device activity, local wallets and requests for a copy or correction. If your situation is unusual, use the support route beside login and describe the specific record involved.

It explains how we handle account details, phone verification, device signals, cookies, support messages and transaction references connected with DANA, OVO, GoPay, QRIS or bank routes.

Phone verification helps connect an account request to the person seeking access and reduces mistaken disclosure. We may use the verification event when handling login, correction or data-access requests.

Yes. The policy covers payment references supplied through DANA, QRIS, OVO, GoPay, virtual account and bank transfer, including status details needed to reconcile an account transaction.

You can submit a data-access request through the support route beside login. Tell us which account record you mean, and we may verify ownership before explaining the available copy or limits.

Contact support with the field that needs correction and the account step where it appears. We may request phone verification or another ownership check before changing personal account details.

We keep records for account security, support handling, transaction reconciliation or legal duties for the period needed for those purposes. Retention can vary by record type and local requirements.

It applies to personal data handled through the service, while access and eligibility depends on local law. Your location, account activity and the requested feature can affect the applicable handling.