How planet123 Handles Your Account Data
This is the planet123 privacy policy. We wrote it to explain, in plain language, what we collect when you open an account with us, why we collect it...
Our Privacy Posture and Jurisdiction Notes
We process your personal data only where local law permits and within supported regions for our services. The categories we keep are limited to what your account actually needs: identity details for verification, contact details for security alerts, transaction references for your DANA, OVO, GoPay and QRIS movements, and device signals to keep the lobby stable. We don't sell your data to
third parties. Where we share information with payment partners or compliance bodies, that sharing is bound by contract and limited to what each partner needs to complete the task you requested. You can request access, correction or deletion of your record at any time, subject to retention rules we're legally required to follow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to Reach Our Privacy Team
If you have a question about this policy, or you'd like to act on a data right, our privacy contacts are listed below. We aim to respond within a few working days...
Why You Can Rely on This Policy
This document is reviewed by people who actually run the platform — not pasted from a template. Below are the editorial trust signals behind every clause you read...
Reviewed Quarterly
Our compliance leads revisit each clause every quarter. If a payment partner changes terms or a regulator updates guidance, the...
Named Owner
A single accountable owner signs off every revision. That person reviews scope, retention windows and third-party links so the wording...
Plain Language
We rewrite legal phrasing into sentences you can read on a phone. Where a technical term is unavoidable, we explain...
Change Log
Every material edit is recorded with a short note explaining what changed and why. You can ask for the change...
Limited Sharing
Data leaves our systems only for verification, payment routing or legal duty. Each partner is bound by a written agreement...
Local Awareness
We pay attention to Indonesia-specific expectations around DANA, OVO, GoPay and QRIS transaction references, and we keep retention aligned with...
Consistency Across Our Policy Pages
This privacy policy sits alongside our terms, cookies and account closure pages. We keep the wording consistent so you don't have to cross-check three documents to understand a...
| Privacy vs Terms | Privacy explains what we collect; Terms explain what you agree to. Where they overlap — like account verification — both pages use the same wording so there's no contradiction. |
|---|---|
| Privacy vs Cookies | The cookies page lists each tracker with its lifespan. This privacy policy summarises why those cookies exist and points back to the cookies page for the full per-cookie breakdown. |
| Privacy vs KYC | KYC notices describe the documents we ask for. Privacy explains how those documents are stored, who reviews them and when they're deleted from our verification archive. |
| Privacy vs Payments | Payment pages cover DANA, OVO, GoPay and QRIS flows. Privacy covers the transaction references those flows generate and the retention window we apply to them. |
| Privacy vs Marketing | Marketing preferences are managed in your account settings. Privacy explains the legal basis we rely on and how withdrawing consent feeds back into our messaging system. |
| Privacy vs Closure | Closing your account doesn't erase every record instantly. Privacy lists the retention categories we're required to keep, and the closure page lists the steps to trigger deletion. |
| Privacy vs Security | Security pages describe the controls we run. Privacy explains how those controls protect the data categories listed here, so the two documents read as one continuous story. |
What Defines This Policy Page
These are the visible elements that shape how the privacy page works on planet123 — the building blocks you'll notice as you scroll through, designed so the policy...