Reference

Open pgsoft login Privacy Policy

pgsoft login gives you a clear Privacy Policy before you open an account, covering phone verification, browser access and wallet records for DANA and QRIS.

Account data explainedCookie choices includedIndonesia access wording

Browse Our Lobby Read FAQ

Browse Privacy Rules For DANA

pgsoft login Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy describes the account details we receive when you create access, complete phone verification or contact us about a wallet status. It also covers technical details such as your browser type, device path, login time and security events, which help us connect the right

1
account session. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, transaction references may be retained so we can match a receipt with your account request. Cookies may remember language, session status and policy choices. We limit access to these records to
2
operational needs, retain them only for stated purposes, and explain when a legal or service requirement affects deletion. Any access or eligibility wording depends on local law. Where local law permits, you can request a copy, correction or deletion through our privacy contact route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY CONTACT PATH

Contact Us About Your Privacy

A privacy question should not get lost beside a login or cashier request. Start from the account support contact path and state the email or phone connected to your account, the request…

Account privacy request Ask us to access, correct or remove eligible account data through the support contact path. Include your registered phone detail so we can verify the request before changing a record.

Wallet record question For DANA, OVO, GoPay or QRIS records, mention the payment rail and receipt reference. We can check the privacy handling of that transaction without requesting your wallet PIN.

Login data concern If a browser session or phone verification looks unfamiliar, contact account support from the cashier path and describe the device. We can direct the security check while protecting your account details.

DATA HANDLING DETAILS

Check How We Handle Account Data

We keep the Privacy Policy practical by linking each data category to an account action: opening access, confirming a phone, checking a receipt or maintaining a secure session.

Account creation

When you open an account, we use the details you submit to create access and respond to account requests. We do not need your wallet PIN for DANA, OVO, GoPay or QRIS support.

Phone verification

A phone verification step helps connect an account request to the person making it. We record the verification result and related security event rather than treating the code as a permanent profile detail.

Cookies and sessions

Cookies can keep your selected language, policy choice and login session available on a browser. You can manage browser cookie settings, although removing them may require another account check.

Security controls

We review login signals such as device type, session time and unusual access patterns to protect account records. If a sign-in seems unfamiliar, contact us before sharing any new payment detail.

Retention periods

We retain account, support and transaction references only for the operational, dispute or legal purpose stated in our Privacy Policy. When that purpose ends, records can be removed or securely restricted.

Changes and requests

You can contact us to ask for a copy, correction or eligible deletion of your data. We may verify account ownership first, then explain the result and any local-law limit.

Ask About pgsoft login Privacy Policy

These Privacy Policy answers address the account questions you are most likely to have before opening access in Indonesia. We focus on the records connected with login, phone verification, cookies and local payment references, so you know what to expect when requesting help.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use the verification result to connect an account request with the registered phone and to reduce unauthorised access. We do not treat the one-time code as a permanent wallet credential.

Where local law permits, you can request a copy of eligible account data through our privacy contact path. We first verify account ownership, then explain the records and any lawful restriction.

We may retain a payment rail, receipt reference and account link to answer a status question or resolve a dispute. We do not ask for your DANA or QRIS PIN through support.

Yes. It explains cookies used for session status, language and policy choices when you access from an Android phone, iPhone or desktop browser. Browser settings can remove or restrict them.

Retention depends on the reason for the record, such as account help, a payment receipt check or a legal requirement. We remove or restrict records when that purpose ends.

Send a correction request through account support with your registered phone detail and the field needing change. We verify the request, update eligible records and explain any local-law limit.

Open pgsoft login Privacy Policy

Contact Us About Your Privacy

Check How We Handle Account Data

Account creation

Phone verification

Cookies and sessions

Security controls

Retention periods

Changes and requests

Ask About pgsoft login Privacy Policy

01 What does the pgsoft login Privacy Policy cover?

02 Why does pgsoft login collect phone verification data?

03 Can I request my account data under the Privacy Policy?

04 How are DANA and QRIS records handled?

05 Does the Privacy Policy explain cookies on mobile?

06 How long does pgsoft login keep support records?

07 How do I correct details covered by this Privacy Policy?

Related Pages