Reference

demo pgshop Privacy Policy

Our Privacy Policy explains how demo pgshop handles your account details, phone verification, device access and wallet records when you use the lobby.

Clear data purposesWallet record contextAccount access choices
demopgshop.club page image
PRIVACY HELP

Get Policy Help Near Account Access

A clear contact path matters when you want to ask about your data rather than a wallet balance.

Policy questions Ask our support desk which account details, login records or payment references are connected to your Privacy Policy request, and we will explain the relevant handling step.
Correction requests If your phone verification detail or contact record is inaccurate, send the requested correction through the account help path so we can match it safely.
Wallet record checks When DANA, OVO, GoPay or QRIS status appears unclear, our support contact can check the related reference without asking you to share a wallet password.
DATA CARE PRACTICES

What Our Privacy Process Covers

We keep privacy practical by tying each record to a stated account need. Your account access, device session and payment reference help us identify the right account, while cookie controls help the…

Account records

We use contact details and phone verification to create and protect your account, then connect your request to the correct record when you ask about Privacy Policy rights.

Device signals

A browser or mobile device may provide session details such as login time and device type, helping us identify unusual access without reading private files on your device.

Cookies

Cookies can remember sign-in preferences and site settings. Your browser controls can remove or restrict them, although some account functions may then need another login.

Payment references

We may retain a DANA, QRIS, OVO or GoPay reference to reconcile account activity and answer a status question; we do not need your wallet password.

Security checks

Phone verification before account access gives us an account step to compare with login activity, while support checks help prevent a private record being changed by mistake.

Retention requests

You can ask what we retain, why it is retained, or whether a correction is possible. We assess the request against service, security and local legal requirements.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account access. They explain which records matter, how a request reaches us and what happens when a payment or device detail needs checking. If your question is not listed, use the support path connected to your demo pgshop account.

It covers account details, phone verification, device session data, cookies, payment references and support requests connected with your use of demo pgshop, where local law permits.

Phone verification helps connect account access to the correct contact detail and supports security checks. We use that step for account handling, not as permission to read private files on your phone.

Yes. The Privacy Policy explains that DANA, QRIS, OVO and GoPay references may be used to match a payment status or answer a support request without requesting your wallet password.

You can request a correction through the account help path. Include the contact detail attached to your account so we can identify the record and apply the appropriate checking step.

Cookies may remember sign-in preferences and site settings. You can manage them in your browser, but restricting cookies may require another login or affect parts of the account path.

We retain records for the period needed for account service, security, payment-status questions or legal duties. You can ask why a particular record remains and whether a change is available.

Use the support contact route shown in your account help area. Our team can identify the relevant record, explain the request path and tell you what information is needed.