Terms of Service
Account creation rules in the Terms point back to this policy for what data those rules collect. The two documents share definitions for account, session and wallet reference.
This is the dewagacor55 Privacy Policy — the document that tells you exactly what we collect when you open an account, what we keep on file once you're...
We process your data under Indonesian data-protection expectations and only where local law permits. When you register, we capture identity fields, contact details and the wallet reference you choose — DANA, OVO, GoPay or QRIS — purely to route deposits and withdrawals on your account. Session logs, device fingerprints and IP records are retained to keep your login secure and to spot
account takeover attempts. We don't sell your data to third parties, and marketing contact stays opt-in. Where supported regions require deletion or export of your records, we honour that within the windows our policy lists below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you have a question about your data, three channels reach our privacy desk directly. We staff them across Indonesia hours and route every privacy ticket through the same reviewer so nothing...
This policy is written, reviewed and dated by named owners on our side. Here's how we keep it honest.
Our privacy text is signed off by the dewagacor55 compliance lead before it goes live, not auto-generated. You can ask...
Every change to this page carries a revision date at the foot of the document. Older versions stay archived for...
We rewrite legalese into Southeast-Asian English a regular account holder can actually read. If a clause needs jargon, we add...
We say what we collect and what we don't. Wallet PINs, full card numbers and biometric data sit firmly outside...
Payment processors, KYC providers and analytics partners are listed by category in this policy. You can ask for the current...
If you disagree with a privacy decision, the policy explains the appeal route, the reviewer who handles it and the...
This Privacy Policy lines up with our Terms, Cookie Notice and KYC pages. Here's how the documents agree with each other so you don't get conflicting answers.
Account creation rules in the Terms point back to this policy for what data those rules collect. The two documents share definitions for account, session and wallet reference.
Cookie categories named here are defined in full on the Cookie Notice. Both pages use the same opt-in toggles and the same retention windows for analytics tags.
Identity-document handling described in our KYC page matches the retention clause here. Documents you upload during verification follow the deletion schedule listed in this policy.
Wallet reference checks during payouts use the data fields defined here. The Withdrawal Policy doesn't add new data collection — it relies on what this page already covers.
Marketing consent rules in promo terms defer to the consent toggles described in this policy. Turning off marketing here switches off promo emails everywhere.
The appeal route in our Complaints page picks up where this policy's privacy-dispute clause ends, using the same reviewer tier and the same response windows.
Closure deletes or anonymises the records this policy lists, on the schedule this policy sets. The Closure page references these clauses rather than restating them.
The policy layout is designed to be skimmed. These are the visible elements you'll find as you scroll, so you can jump straight to the section...
A sticky anchor menu sits at the top of the policy so you can jump to collection, retention, sharing or your rights without scrolling through clauses you've already read on a previous visit.
Each clause opens with a one-line summary in regular English before the formal wording. If the summary answers your question, you don't need to read the legal paragraph underneath.
The footer carries the current version number and the date it went live. Earlier versions are linked beside it so you can see exactly what changed and when.
A short checklist shows what you can ask us to do with your data — access, correct, export, delete — and the channel for each request, all on a single visible card.
Third-party categories appear as labelled chips rather than buried prose, so you can see at a glance which kinds of partners touch your dewagacor55 account data.
A persistent contact block keeps the privacy email and chat route in view as you scroll, so opening a request never means hunting back to the top of the page.