How pangerantoto4 Handles Your Privacy
This is the privacy policy for pangerantoto4. We wrote it to explain — in plain language — what we collect when you open an account, why we keep...
Policy Posture and Jurisdiction Notes
Our privacy practices follow the rules of the supported regions where local law permits account access. When you register, we collect your name, contact details, device fingerprint and the e-wallet handle you use to fund your balance. We hold this on encrypted servers and share it only with payment partners and regulators who have a legal right to ask. We never sell
your details to advertisers, and we never trade your transaction history. If you close your account, we keep records for the retention window the law sets, then delete them. You can ask us for a copy of what we hold at any point.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Paths for Privacy Requests
Privacy Inbox
Email our privacy desk for data export requests, deletion claims or correction notices. We aim to reply within three working days and confirm receipt the same hour your message lands.
Live Chat
Open chat from the lobby header and ask for the privacy team. The agent will route you to a senior reviewer who handles account data, consent withdrawal and marketing opt-outs.
Postal Notice
Send formal data-protection notices to our registered correspondence address. Include your account handle and a scanned ID so we can match the request to the right record without delay.
How We Review This Policy
Legal Sign-Off
Every change to this policy passes through our internal counsel before it goes live. Nothing is published until the wording matches what our compliance team has actually approved in writing.
Quarterly Audit
We re-read the policy every quarter against new regulator notices in Indonesia and supported regions. If a clause is stale, we rewrite it and timestamp the change at the foot of the page.
Encryption Standards
Account records sit behind TLS in transit and AES at rest. Our infrastructure team rotates keys on a fixed schedule and logs every administrative read against the data set.
Staff Training
Anyone who can see your data has signed a confidentiality agreement and completed our privacy module. Access is role-based, time-bound, and revoked the day someone changes team.
Vendor Checks
Payment partners handling DANA, OVO, GoPay and QRIS flows are vetted before we connect them. We require their own privacy posture to match ours, in writing, with renewal each year.
Plain Language
We refuse to hide behind legalese. If a paragraph cannot be read by a first-time account holder, our editor sends it back to counsel for a rewrite before the next publish.
Consistency Across Our Policy Pages
| Cookie Notice | Same definitions of personal data, same retention windows, same contact addresses. If a term is defined here, the cookie page uses it identically without paraphrasing. |
|---|---|
| Terms of Service | Cross-references match clause numbers exactly. When the terms mention data handling, the link points to the matching paragraph here, not a vague top-of-page anchor. |
| AML Notice | Identity-verification fields listed there are the same fields described in this policy. No surprise data points appear in one document and not the other. |
| Marketing Consent | Opt-in language matches word-for-word with the checkbox you saw at sign-up. Withdrawing consent here cancels the same flag stored in the marketing record. |
| Cookie Banner | Categories shown in the banner — essential, analytics, preference — line up with the categories named in this document. Toggle one off and the description here explains what stops. |
| Account Settings | The privacy controls in your dashboard mirror the rights listed here. Export, correct, delete and restrict appear in both places using the same button labels. |
| Complaints Path | The escalation route described here is the same one published on our complaints page. One inbox, one response window, one reference number per case. |