Terms of Service
The Terms page sets the contract; this privacy policy sets the data handling. Both documents use the same defined terms so your account, lobby and payment references mean the same thing in either text.
This is the pos4d7777 privacy policy — the page that explains what we collect when you open an account, why we hold it, and how long it stays...
We process your personal data where local law permits and only within supported regions. For Indonesia account holders, that means your identity details, device fingerprints, deposit references and lobby activity are held under the data-protection rules that apply to our operating licence. We don't sell your data to third parties. We share it with payment partners only to settle DANA, OVO, GoPay
and QRIS transactions, and with regulators when they ask in writing. You can request a copy, a correction, or a full deletion of your account record at any time — we action verified requests within thirty days. Cookies on our brand pages are limited to session, preference and fraud-prevention categories, and you can clear them from your browser without losing access.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you have a privacy question, these are the channels that reach our data team directly rather than general support.
Our legal desk re-reads this policy every quarter and after any product change. Revision dates sit at the top of the page so you can see exactly when wording last shifted on data handling.
We rewrote the policy in Southeast-Asian English so Indonesia readers don't need a lawyer to parse it. Defined terms are kept short, and we link each section to the part of your account it affects.
A real person owns this policy — our Data Protection Officer signs off every revision. Their contact route is published above rather than buried behind a generic support form.
The wording here matches the data conditions of our operating licence. Where local law permits stronger reader rights, we apply the stronger standard rather than the minimum on the licence sheet.
Every data-access or deletion request is logged with a ticket reference. You can ask for that reference in writing, and we keep the audit record for the period our regulator expects.
We list our processors — payment partners, fraud screens, hosting — and review their contracts annually. None of them get more data than they need to settle a DANA, OVO, GoPay or QRIS movement.
The Terms page sets the contract; this privacy policy sets the data handling. Both documents use the same defined terms so your account, lobby and payment references mean the same thing in either text.
Our cookie notice expands the cookie paragraph here. The two pages share the same category labels — session, preference, fraud — so what you accept in one place reflects accurately on the other.
KYC explains which identity documents we ask for. This privacy policy explains how long we keep them and who inside the company can see them after your account passes verification checks.
If a privacy answer doesn't satisfy you, the complaint procedure page shows the escalation route. We reference the same thirty-day clock so the deadlines stay aligned across both documents.
Closing your account triggers the retention clock described here. The closure page lists the steps; this page lists the data categories that are erased and the ones we must keep for regulator reporting.
Opt-in choices for promo emails sit on the preferences page. This policy explains the lawful basis behind each channel and how we record withdrawal of consent when you flip a toggle off.
The security page details encryption and storage. This privacy policy points at it for technical depth instead of repeating it, keeping both documents short and consistent on the same control set.