Reference

pgr007 Privacy Policy, Made Clear

The pgr007 Privacy Policy explains what account, device and wallet data we collect, why we use it and how you can ask about it.

Account dataWallet recordsCookie choicesContact path
Explore Our Lobby Read FAQ
pgr007 pgr007 Privacy Policy, Made Clear
CONTACT WHEN NEEDED

Get Help With Privacy Policy Requests

A clear contact route matters when your account data or wallet record needs attention. Start from the signed-in support area and describe the Privacy Policy request in plain English, adding the account phone detail and the relevant payment reference where available. We use those details to locate the correct record without asking you to send a full wallet credential. For access questions, we may first confirm your account step and phone verification status.

Team online

Account data request

Use the signed-in support path to ask what account data is held for your pgr007 profile. Include the phone detail linked to your account so we can distinguish your request from another account with a similar name.

Wallet record query

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference shown in your account. We can compare the wallet status with the related account record and explain which data was used for the status check.

Access correction

When your phone detail or account record needs correction, contact support from the account area and state the exact change. We may ask for a verification step before changing personal data or discussing a protected account record.

DATA HANDLING DETAIL

What We Do With Your Privacy Choices

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We collect the account details needed to create and maintain your profile, including your phone contact and verification result. This lets us associate a support request with the correct account before discussing access, wallet status or a personal data change.

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, amount status and time record connected to your account. We use those details to trace a cashier result; do not send your wallet PIN or full wallet password to us.

Cookies and sessions

Cookies and similar session data can remember that your mobile browser has passed an account step, helping the lobby and account area load consistently. You can manage browser cookie settings, though changing them may interrupt sign-in or session continuity.

Account security

Phone verification is checked before account access, and we may ask for another account detail when a privacy request concerns protected data. These checks reduce the chance that another person can obtain or change your account record.

Retention approach

We keep account, support and payment-status records for as long as needed for the purpose described here, account security and applicable legal duties. When a record is no longer needed for those purposes, our handling process addresses its removal or de-identification.

Changes and questions

You can ask us to explain, correct or update personal details through the signed-in support path. Tell us which field is wrong and include the relevant account step; we may confirm phone ownership before completing a requested change.

Privacy Policy Answers for pgr007

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about personal data. We explain the practical records created by phone verification, mobile sessions and Indonesian wallet activity without asking you to share sensitive wallet credentials. If a request concerns account access, the result depends on local law and where local law permits.

The pgr007 Privacy Policy covers account details, phone verification, device and cookie data, support messages, and payment-status records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use those records and how you can ask about them.

We may receive a payment reference, status, time and account connection when you use DANA, OVO, GoPay or QRIS. We do not need your wallet PIN for a status check. Bank transfer and virtual account records can also be linked to the relevant account action.

Yes. Send a correction request through the signed-in support area and identify the exact account field that needs changing. We may confirm your phone detail or another account step first, because a personal data change should not be made from an unverified request.

The Privacy Policy covers device and session details that help us recognise a mobile browser, maintain sign-in continuity and investigate an access issue. Moving from mobile to desktop may create separate session data. Browser cookie settings can affect how those sessions work.

We retain account, support and payment-status records while they serve the stated purpose, help protect account access or are needed for applicable legal duties. When those reasons end, our process addresses removal or de-identification rather than keeping the record without a purpose.

Open the signed-in support area and describe your Privacy Policy request, using your account phone detail and a payment reference only when relevant. We can then locate the correct record, explain its use and ask for a verification step before discussing protected data.

Account access and any related data handling depend on local law and apply where local law permits. If your location or eligibility affects access, we will use the account and support details available to assess the request, without asking for unnecessary wallet credentials.

Related Pages

pgr007 Indonesia Live Roulette Gold FAQ Serie A Over Under Account information