LEGAL REFERENCE

How We Handle Your Account Data

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...

Account dataSession logsWallet referencesCookie controlsIndonesia scope
dewagacor55 How We Handle Your Account Data

Privacy Posture and Jurisdiction Notes

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Privacy Contact Paths

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...

Privacy Inbox Email our data desk for access, correction or deletion requests on your dewagacor55 account. We acknowledge within one business day and confirm the resolution window in that first reply.
Live Chat Escalation Open lobby chat and ask for the privacy queue. The agent flags your ticket, hands it to a senior reviewer, and you get a written follow-up in your account inbox the same day.
Account Settings Inside your account you can adjust marketing consent, refresh saved DANA, OVO, GoPay or QRIS references, and download a copy of the data we hold without writing in.
REVIEW SIGNALS

Editorial Trust Signals For This Policy

This policy is written, reviewed and dated by named owners on our side. Here's how we keep it honest.

Named Reviewers

Our privacy text is signed off by the dewagacor55 compliance lead before it goes live, not auto-generated. You can ask...

Version Dating

Every change to this page carries a revision date at the foot of the document. Older versions stay archived for...

Plain Language

We rewrite legalese into Southeast-Asian English a regular account holder can actually read. If a clause needs jargon, we add...

Scope Limits

We say what we collect and what we don't. Wallet PINs, full card numbers and biometric data sit firmly outside...

Third-Party Disclosure

Payment processors, KYC providers and analytics partners are listed by category in this policy. You can ask for the current...

Reader Recourse

If you disagree with a privacy decision, the policy explains the appeal route, the reviewer who handles it and the...

BENCHMARKED

Consistency With Our Other Policy Pages

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.

01

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.

02

Cookie Notice

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.

03

KYC Page

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.

04

Withdrawal 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.

05

Promo Terms

Marketing consent rules in promo terms defer to the consent toggles described in this policy. Turning off marketing here switches off promo emails everywhere.

06

Complaints Procedure

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.

07

Account Closure

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.

What This Policy Page Shows You

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...

Section Anchors

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.

Plain-English Summaries

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.

Revision Stamp

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.

Rights Checklist

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.

Vendor Categories

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.

Contact Block

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.

Privacy Policy — Common Questions

We hold your registration fields, the wallet reference you chose for DANA, OVO, GoPay or QRIS, your session logs and your communication history with support. Nothing outside that list sits on file against your account.

Only with processors we need to run the service — payment routing, KYC checks and security analytics. We don't sell your data and we don't pass it to marketing networks outside the consent you've toggled on.

Most account data is anonymised within ninety days of closure. Records we're required to retain for financial or anti-fraud reasons stay archived for the period local law permits, then get purged on schedule.

Yes. Email the privacy inbox or use the export tool inside account settings. We package your records in a readable file and send it to the address on your account within the response window.

Most fields are editable directly inside account settings. For locked fields tied to KYC, message the privacy desk with the correction and supporting document and we'll update the record after a quick review.

No. We store the wallet reference needed to route a transaction, never the PIN, password or full card number. Authentication happens on the DANA, OVO, GoPay or QRIS side, not ours.

Material changes trigger a notice in your account inbox and a banner on the lobby for the first week the new version is live. The revision stamp at the foot of the page confirms which version you're reading.