How ajr88 Handles Your Account Data
This is the ajr88 privacy policy, written for the Indonesia lobby you actually use. We explain what we collect when you open an account, why we hold it...
Policy Posture and Data Handling Scope
We collect what's needed to run your account: identity details at sign-up, device and session data while you're in the lobby, and transaction references when you move money through DANA, OVO, GoPay or QRIS. Where local law permits, we keep these records for the retention windows our compliance team sets, and we share them only with regulated processors who help us settle
wallet transfers, verify identity, or investigate fraud. Outside supported regions, access may be limited and certain processing paused. You can reach our privacy desk to request a copy, ask for corrections, or close your account; we respond within the windows the policy commits to and confirm every action in writing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Editorial Trust Signals Behind This Policy
Six checkpoints sit behind every clause you read here.
Quarterly Policy Review
Our compliance team revisits the full document every quarter, checking each clause against current Indonesian data practice and the wallet rails we connect to. Changes are dated and stored in a public revision log.
Named Data Owner
A single privacy lead signs off on every revision, so the document isn't a committee draft. You can request their contact through the privacy desk if a question needs escalation beyond standard support agents.
Processor Register
We list the regulated processors handling DANA, OVO, GoPay and QRIS settlements alongside identity-verification partners. Any addition triggers a policy refresh before that processor touches account data.
Plain-Language Drafting
Clauses are rewritten in en-ID English so you don't need a legal background to follow them. Where a technical term is unavoidable we add a short bracketed explanation in the same paragraph.
Retention Windows Published
Every category of data has a stated retention window. Nothing sits on our servers indefinitely without a documented reason, and expired records are purged on a rolling monthly cycle.
Audit-Ready Logs
Access to account data is logged at the staff level. If you ask who viewed your file, we can produce that trail within the response window the policy commits to.
Consistency Across Our Sibling Policy Pages
This privacy page lines up with the other legal documents in the ajr88 footer.
| Terms of Service | Defines the account contract; this page explains the data side of that same relationship without repeating contractual clauses. |
|---|---|
| Cookie Notice | Lists the trackers in the lobby; this page covers what happens to data once a cookie has fed it into your account record. |
| AML Statement | Sets out anti-money-laundering checks; we explain here how the resulting verification data is stored and for how long. |
| KYC Disclosure | Describes documents requested at sign-up; this page handles where those documents live afterwards and who can open them. |
| Marketing Preferences | Lives in your account panel; this page is the legal basis for honouring whatever toggle position you leave it in. |
| Complaints Procedure | Routes service issues; privacy-specific complaints land with the named data owner referenced in the trust section above. |
| Regional Access Notice | Confirms supported regions; we mirror that scope so data handling never extends beyond where the lobby is offered. |
What This Policy Page Actually Shows You
Six visible elements define the layout you're reading right now.