Reference

pg soft demo Privacy Policy For Your Account

pg soft demo Privacy Policy explains how we handle the details connected with your account, wallet status and device access.

Account dataWallet recordsCookie choicesPolicy requests
pg soft demo pg soft demo Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A privacy question should not get lost beside a wallet issue, so we separate the routes by the detail you need. Use the account help path for identity or sign-in questions, the cashier receipt path for payment records, and the privacy request route for copies, corrections or deletion questions. Include your account contact and a short description so we can locate the relevant record without asking for unnecessary data.

Team online

Account help

Ask through account help when your phone verification, login record or account contact needs clarification. We use the details already linked to your account to check the request and avoid collecting unrelated personal data.

Receipt status

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference through the cashier support path. We can compare the receipt status with the account record before replying.

Privacy request

Use our privacy contact route to ask for a data copy, correction, deletion question or cookie preference change. Tell us which account contact you use and what action you want us to check.

HANDLING DETAILS

How We Apply This Policy

Privacy work is tied to practical account events rather than a broad promise. We check phone verification before account access, record the device and sign-in signals needed to protect that step, and…

Account details

We use the contact and verification details you provide to create, protect and maintain your account. We do not need extra profile details for a privacy request, and we ask you to identify the account before releasing account-linked records.

Device signals

Login time, browser type and device signals can help us spot an unusual access attempt. These records support account protection and troubleshooting; they are not treated as a replacement for your phone verification step.

Cookie choices

Session cookies can keep an account path open and remember settings while you move between policy and account pages. You can clear or restrict cookies in your browser, though some sign-in functions may then need another check.

Wallet matching

Payment references from DANA, QRIS, OVO, GoPay, bank transfer or virtual account help us match a receipt with the right account. We use the reference for status checks, not as a substitute for account ownership checks.

Retention timing

We keep account, security and payment records for the period needed for account operation, dispute checks or applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward removal or restriction.

Policy changes

When this Privacy Policy changes, we update the page and identify the changed subject in clear language. You can contact us before continuing account access if you want to ask how a new data use affects your account.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening access. We keep the wording practical: what we collect, why a payment reference appears, how cookies behave, and where to send a request. If your situation is not covered, use the privacy contact route with your account contact and a short description.

The pg soft demo Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It also explains retention, account protection and how you can ask for a copy, correction or deletion where local law permits.

Phone verification helps us confirm that the person requesting account access is connected with the account contact supplied during setup. It also gives our support team a safer reference when checking a login issue or a privacy request.

Yes. The Privacy Policy includes payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match receipts, check a stalled status and address account questions without requesting unrelated wallet details.

The policy describes session cookies and similar browser storage used to keep account steps working, remember selected settings and check page performance. You can manage cookies through your browser, but restricting them may require another sign-in or affect account access.

Send a request through the privacy contact route and include the account contact used for phone verification. We may ask for an account check before sharing records, then explain which data can be provided under local law and how it will be delivered.

You can ask pg soft demo to correct inaccurate account data or ask whether removal is available. We first verify the account, identify the records involved and check operational or legal retention needs before confirming the action.

Where local law permits, you can ask why a particular account, security or payment record remains stored. Tell us the record type, such as a QRIS receipt or login event, and we will explain the applicable retention reason and next step.