Cookie Policy
Our cookie page explains browser storage, device signals, and analytics tags in more detail. This privacy page connects those items to your account and explains why they matter for data handling.
LEGAL REFERENCE
Privacy Policy For Your Account
pgsoft88 keeps your casino, slots and sportsbook account privacy clear from the first tap: what we collect, why we use it, and how you can ask us about...
Indonesia privacy focusAccount data clarityQRIS referencesSupport paths
How We Handle Your Data
This Privacy Policy explains how we handle data connected with your pgsoft88 account, including sign-in details, device signals, lobby activity, support chats, verification checks, and transaction references such as DANA, OVO, GoPay, and QRIS. We use this data to run your account, protect access, answer your requests, keep records, and improve the privacy experience across our site. We may share limited data
with service partners when needed for account support, security checks, analytics, or legal duties, where local law permits. We aim to keep data only as long as needed for the purpose described here, then remove or anonymise it when retention is no longer required. If you contact us, we may ask for enough detail to confirm the account before helping with privacy
requests.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY VISITORS TRUST US
How We Check This Policy
We write this policy for the way your account actually works on pgsoft88. The checks below help us keep privacy wording clear, consistent, and tied to account flows in supported regions of...
Plain-language drafting
We avoid dense legal phrasing where a clearer sentence works better. Each section explains what data is involved, why we need it, and how you can contact us about it.
Account-flow mapping
We map policy wording against sign-in, lobby access, support, and transaction-reference screens. That helps us describe privacy handling based on real account touchpoints, not abstract promises.
Retention checks
We check whether each data category still has a valid purpose. When records are no longer needed for account, security, support, or legal reasons, we plan removal or anonymisation steps.
Access controls
We limit internal access to account data based on team need. Support, security, and operations staff see only the data required to handle your request or protect the service.
Partner due care
When service partners help with hosting, analytics, security, or payment-reference handling, we expect them to protect data and use it only for the work they perform for us.
Update discipline
When we change this policy, we update the date and keep the wording aligned with your account flow. Material changes are written so you can understand what changed.
PLATFORM COMPARISON
Consistency Across Our Policy Pages
This Privacy Policy sits beside our other legal pages, so we keep the wording aligned without copying every sentence. Each page has its own role, while privacy stays focused on data handling...
Terms page
Our terms describe account rules and service use. This privacy page stays narrower, covering personal data, retention, sharing, and how you can contact us about your account details.
Security page
Our security content explains protection steps around login, device checks, and suspicious activity. This privacy page explains the data used in those checks and why we process it.
Promotion rules
Promotion rules may ask for account history or eligibility checks. This privacy page explains how related data is handled, so reward activity is still covered by clear data-use wording.
Support centre
Support content helps you solve account issues. This privacy page explains how chat logs, email trails, and identity checks are used when you ask us for privacy help.
Regional access text
Where access depends on supported regions, our pages use similar wording. This policy adds the privacy angle, including how location signals may support security and compliance checks.
Update dates
Each legal page carries its own update date. We keep privacy updates separate, so you can see when data-handling wording changed without mixing it with other account rules.
AT A GLANCE
Policy Page Layout Highlights
This page is built so you can scan privacy points quickly before opening an account or returning to the lobby. The layout highlights what data we collect, how...
Hero privacy promise
The opening panel tells you the privacy value first, not...
Context chip row
Short chips make key account references visible without turning the...
Legal notice block
The main notice keeps data collection, use, sharing, retention, and...
Support cards
The contact cards separate chat, email, and security routes. That...
Policy signals
The trust-signal area explains how we keep the wording connected...
FAQ anchors
The question section answers common privacy concerns in direct language...
Privacy Questions Before You Join
We collect the details needed to create and protect your account, such as contact data, login records, device signals, support messages, and transaction references linked to DANA, OVO, GoPay, or QRIS.
We use account data to run the service, confirm access, process support requests, protect against misuse, keep required records, and improve privacy controls. We do not use it for purposes outside this policy.
Yes. Contact us through chat or email and describe what you want to access or correct. We may ask for proof that the request belongs to your account before we act.
We keep data only while it serves an account, security, support, legal, or record purpose. When that purpose ends, we work to delete, anonymise, or archive it according to our retention process.
We share limited data only when partners help us provide hosting, analytics, security, support, or transaction-reference services. They should use the data only for the task we assign to them.
We update the policy date when wording changes. If a change materially affects how we handle your data, we aim to make the change clear so you can decide how to continue.