How dewawin Handles Your Account Data
This is the dewawin privacy policy — a plain read of what we collect when you open an account, why we keep it, and how long it stays...
Our Policy Posture and Jurisdiction Notes
We process your data under the rules that apply to supported regions in Indonesia, and we limit collection to what the lobby actually needs. That means your registration details, KYC documents where local law permits, session logs, and the payment references you attach to your wallet. We don't sell your information to third parties. When you use DANA, OVO, GoPay or QRIS,
we share only the minimum required with the payment processor to confirm the transfer. You can request access, correction or deletion of your account data by contacting our team, and we'll action it within the timelines our jurisdiction sets out.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
If you have a question about your data, here's how to reach the team that handles it.
How We Review This Policy
Editorial Owner
Our policy text is owned by a named editor on the dewawin team, not a generic legal template. Every revision...
Legal Review
Indonesian counsel reviews the policy against current local data rules before each publish. Where the law shifts, we update the...
Security Sign-Off
Our security lead signs off on the data-flow descriptions so what you read here matches what actually happens inside our...
Plain Language
We rewrite dense clauses into sentences you can scan on a phone. If a paragraph needs a lawyer to decode...
Version History
Older versions of this policy are archived and available on request, so you can compare what applied when you opened...
User Feedback
When you tell us a section is unclear, we track it and revisit the wording on the next review cycle...
Consistency Across Our Policy Pages
| Terms of Service | The data definitions used here match the ones in our terms, so account, wallet and session mean the same thing on both pages. |
|---|---|
| Cookie Notice | Tracking categories listed here line up with the toggles in our cookie banner — analytics, functional and required are labelled identically. |
| KYC Notice | Document handling described in this policy mirrors the KYC notice you'll see during verification, including retention windows where local law permits. |
| Payment Disclosure | References to DANA, OVO, GoPay and QRIS in our payment disclosure use the same data-sharing language you'll find in this policy. |
| Account Closure | Closure and erasure timelines on the account page match the windows quoted here so you don't get conflicting numbers. |
| Marketing Preferences | Opt-in and opt-out controls referenced here match the toggles inside your account preferences exactly. |
| Complaints Path | Escalation steps you'll read here are the same ones our complaints page lists, so a privacy issue and a service issue follow parallel routes. |
What This Policy Page Shows You
Last Updated Stamp
The top of this page carries a clear date so you know which version applies the moment you read it. We refresh the stamp every time wording changes, even slightly.
Section Anchors
Each clause has a linkable anchor, so support agents can send you to the exact paragraph that answers your question rather than asking you to scroll.
Plain-Language Summary
Every long clause is paired with a short summary box that captures the practical takeaway in one or two lines for quick phone reading.
Your Rights Block
A dedicated block lays out your access, correction, export and deletion rights, with the contact path next to each so you can act without hunting.
Retention Table
A simple table shows how long each data category stays with us — registration, KYC, session logs and payment references — under supported region rules.
Change Log
A change log at the foot of the page lists what shifted between versions, so returning readers can jump straight to the diff instead of re-reading everything.