LEGAL REFERENCE

How daun123 Handles Your Account Data

This is the daun123 privacy policy — the page that tells you exactly what we collect when you open an account, why we collect it, and how long...

Indonesia-focusedPlain-language policyAccount data onlyUpdated regularlyReader-friendly
daun123 How daun123 Handles Your Account Data

Our Privacy Posture and Jurisdiction Notes

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

HELP CHANNELS

Privacy Contact Paths at daun123

If you need to reach our privacy desk — to request a data export, ask us to correct a record, or raise a concern about how we've handled your information — these...

Privacy Inbox Email our data protection desk for access requests, deletion notices or correction tickets. We acknowledge within one business day and respond fully inside the window your jurisdiction sets out for us.
Live Chat Escalation Open chat from any daun123 page, type the word privacy, and the agent routes you to a policy specialist instead of a general lobby host. Useful for quick clarifications on what we store.
Written Notice For formal complaints or regulator-style correspondence, send a written notice through the contact form marked legal. We log every submission and reply with a case reference you can keep for records.
PLATFORM TRUST SIGNALS

How We Keep This Policy Honest

A privacy policy only works if the people behind it actually review it. Here's how we keep this document accurate, current and matched to what the daun123 platform really does with your...

Quarterly Reviews

Our compliance team rereads every clause every three months, checks it against current product behaviour, and rewrites anything that no longer matches what daun123 actually collects from your account flow.

Named Data Owner

One internal owner signs off on this policy. That person is accountable when a clause is wrong or out of date, so escalations don't get lost between departments or vendors.

Vendor Audits

Every processor that touches your data — payment rails, hosting, analytics — sits on a register we audit yearly. Contracts we cannot verify get cut, and the policy updates to match.

Change Log

Material edits appear with a dated note at the foot of the page so you can see what shifted between versions instead of guessing whether the wording you read last month still applies.

Plain Language

We deliberately strip out legalese where Indonesian regulation lets us. If a sentence needs a lawyer to parse, we rewrite it until a normal account holder can read it once and move on.

Reader Feedback

Questions you send to the privacy inbox feed directly into the next revision. If three people ask about the same clause, that clause gets rewritten in the following quarterly pass.

Consistency Across Our Policy Pages

daun123 publishes several policy documents — privacy, cookies, terms, account closure — and they have to line up. Here's how this privacy page sits next to its siblings...

Same DefinitionsTerms like account, session and personal data carry identical meanings in every policy document, so a clause here matches the equivalent clause in our terms.
Shared Retention TableThe retention schedule referenced here is the same one cited in our cookie notice and account closure page, kept in one place to avoid drift.
One Contact DeskPrivacy, cookie and data requests all reach the same internal desk, so you never get bounced between teams when a question crosses two policies.
Aligned Update DatesWhen one policy changes, related pages get reviewed in the same pass and stamped with a matching revision date for easy cross-checking.
Linked Cross-ReferencesWhere this page mentions cookies, marketing or KYC, we link directly to the sibling policy rather than repeating wording that could fall out of sync.
Single Jurisdiction NoteThe supported-regions wording is identical across documents, so access rules you read here apply consistently when you open the terms or closure pages.
Unified Version TagEvery policy carries the same version tag in its footer, making it obvious at a glance whether the set has been refreshed together or one page lags behind.
PLATFORM SNAPSHOT

What This Policy Page Includes

Rather than burying the structure, here's a map of what the privacy page actually contains so you can jump to the part that matters to you. These are...

Data Categories A clear list of what we collect: identity fields, contact...
Purpose Statements Each data category is paired with the reason we hold...
Retention Windows Specific timeframes for how long each record lives on our...
Your Rights Panel A dedicated section listing the access, correction, export and erasure...
Sharing Disclosures The categories of third parties that may receive your data...
Revision History A dated change log at the foot of the page...

Privacy Policy Questions Readers Ask

We collect identity fields you submit during signup, contact details for account recovery, device and session signals for security, and payment references tied to your transactions. Each category is listed with its purpose in the data section above.

Retention varies by data category. Identity records sit with us for the period regulators expect after account closure, while session logs roll off sooner. The retention table on this page lists the specific windows attached to each field.

Yes. Email our privacy inbox or open chat and ask for privacy escalation. We confirm receipt within one business day and complete access, correction or erasure requests inside the timelines your jurisdiction sets for us.

Only with processors that help us run the account: payment partners, hosting, fraud-prevention vendors and regulators where local law requires disclosure. Every vendor sits under a written data agreement we audit yearly against this policy.

Material updates appear in the dated change log at the foot of this page, and significant shifts trigger an in-account notice the next time you sign in so you can review what moved before continuing.

Some processors operate from regional data centres outside Indonesia. Where local law permits, those transfers happen under written safeguards and only for the named purposes in this policy — never for unrelated marketing or resale.

A named internal data owner signs off on every revision and answers escalations from the privacy inbox. That accountability sits with one person so questions about wording or handling never get passed between departments unanswered.