Reference

Open pg paus Privacy Policy for account clarity

pg paus Privacy Policy explains what we collect when you open an account, sign in on mobile, use DANA or QRIS, and contact our support path.

Account dataWallet recordsDevice choicesContact steps
Browse Our Lobby Read FAQ
pg paus Open pg paus Privacy Policy for account clarity
CONTACT ROUTES

Check your Privacy Policy contact path

A direct contact route helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel.

Account privacy request Use the account support path to ask what personal details are linked to your profile, why a phone verification step appeared, or how to request a correction. We may ask for an account identifier so we can protect your details before discussing the request.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, attach the payment reference and date through support. We use that detail to locate the relevant entry without asking you to disclose a wallet password, card secret or complete security code.
Cookie and device help If a mobile browser keeps an old session or a cookie choice does not appear to save, tell us the device type and browser path. We can explain the available setting or access step while keeping the request focused on Privacy Policy handling.
HANDLING PRACTICE

Explore how pg paus handles your records

We keep our Privacy Policy practical by linking each category of data to a real account action.

Account creation

When you open an account, we collect the details needed to create and maintain that profile, including contact information and the phone verification result. We use those details to associate sign-in activity with your account and to respond to a Privacy Policy request.

Payment references

A DANA, OVO, GoPay or QRIS reference can remain connected to an account record after a wallet step. Bank transfer and virtual account references may also be retained for reconciliation and support, while we avoid asking for your private wallet credentials.

Device sessions

When you move from mobile login to a lobby page, we may record device, browser and session signals used to keep access consistent. These signals can help us investigate an unfamiliar sign-in without treating your device name as a public profile.

Cookies

Cookies and similar storage can remember a session, preserve a selected setting and help us understand whether a page loads correctly. You can manage available cookie choices through your browser, although removing some cookies may require another account sign-in.

Retention

We retain records only for the period needed for the purpose described in this Privacy Policy, account security, payment reconciliation or a legal request where local law permits. A retention question can be sent through the account support path with your account identifier.

Policy changes

If we change how a data category is handled, we will update this Privacy Policy and show the revised date or notice where appropriate. You can ask what changed, request access to relevant records, or seek correction through the same support route.

Find answers about pg paus Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the practical route for access requests, corrections, cookies, device sessions and payment references. If your situation involves local eligibility, access depends on local law and is handled where local law permits.

The pg paus Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. It explains why we use each category and how to contact us about it.

Use the support path connected to your account and identify the email or phone detail attached to it. State that you are requesting access under the Privacy Policy. We may ask for an account check before sharing records, so your information is not sent to the wrong person.

Yes, you can ask us to correct inaccurate account or contact details through the account support route. Include the part that needs changing and the updated value. For a wallet record, provide the payment reference instead of a password or full security code.

Yes. Privacy Policy handling includes references created when you use DANA, QRIS, OVO or GoPay, along with bank transfer and virtual account references. We use those entries to match a payment status with the right account and to answer receipt questions.

Device and browser signals help us recognise a session, investigate unusual access and keep the mobile path from login to the lobby working correctly. They can include browser type, session timing and security events, but they are handled under the purposes described in this Privacy Policy.

You can manage cookies through the settings in your browser or device. Some cookies support sign-in and saved choices, so removing them may clear a session or require another account step. If a setting does not behave as expected, contact us through the support path.

Where local law permits, you can ask how long a category is kept and why it remains necessary. Send the request through account support with your account identifier and the record type, such as a QRIS receipt, phone verification event or device session.

Related Pages

pg paus Indonesia About Us Account information ligajp77 Access guide