LEGAL REFERENCE

Our Legal Notice, Plain And Direct

This is the dapatduit legal hub. We've written our policies in clean language so you can read them once and know where you stand before opening an account...

TermsPrivacyEligibilityAcceptable UseCookies
dapatduit Our Legal Notice, Plain And Direct

Policy Posture And Jurisdiction Wording

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

HELP CHANNELS

Reaching Our Policy Desk

Privacy Mailbox Write to our privacy address when you want...
Terms Queries If a clause in our terms reads unclear...
Compliance Line For jurisdiction questions, supported-region checks or account-eligibility doubts...
REVIEW SIGNALS

How We Maintain Editorial Policy Trust

Drafted In-House

Every clause on this legal hub is drafted by our own policy writers, not lifted from a template. That means the wording matches how dapatduit actually runs, and we can answer for any line in it.

Dated Revisions

Each policy page carries a last-updated stamp at the foot. When we change a clause, the stamp moves and a short note describes what shifted, so you can track the history of our terms.

Legal Review

Indonesian counsel reviews material updates before they go live. We don't push silent changes to terms or privacy wording without that pass, and we keep the review log on file.

Plain Language

We rewrite clauses that read like boilerplate. If a paragraph confuses our own support team, it gets sent back. The aim is policy you can read in one sitting.

Version History

Older versions of terms and privacy stay archived. If you signed up under a previous wording, you can request that archive copy through the policy mailbox at any time.

Single Source

This legal hub is the single source for our policy wording. Anything quoted elsewhere — email, chat, social — defers to what's published here on the dapatduit domain.

SIDE BY SIDE

Consistency Across Sibling Policy Pages

01

Terms vs Privacy

Terms covers the rules of using your account; privacy covers what we store. They reference each other where they overlap so you don't read conflicting wording on the same topic.

02

Privacy vs Cookies

Privacy is the umbrella; the cookies notice sits beneath it and explains session, preference and analytics tags specifically. Both pages share definitions to keep terminology consistent.

03

Eligibility vs Terms

Eligibility lists who may open an account in supported regions. Terms then describes how that account behaves once opened. Reading both gives you the full picture before sign-up.

04

Acceptable Use vs Terms

Acceptable use is a focused subset of terms — one-account rules, identity honesty, no automation. We split it out because it's the section most readers want to find quickly.

05

KYC vs Privacy

KYC wording explains what documents we may ask for; privacy explains how those documents are stored and retired. The two pages cite each other on retention windows.

06

Complaints vs Support

Complaints is a formal escalation path with timelines; support is everyday help. The legal hub points to complaints when a matter needs a written record rather than a chat reply.

07

Cookies vs Marketing

Cookies governs what we set in your browser; marketing preferences govern what we send to your inbox. Both honour the same opt-out controls inside your account settings.

What Defines This Policy Hub

Clear Section Index

The legal hub opens with a section index so you can jump to terms, privacy, cookies or acceptable use without scrolling through unrelated wording. Each entry shows its last revision date in line.

Reader-Friendly Type

We set policy pages in a wider line height than the lobby so dense paragraphs stay scannable on phones. Tables of definitions break the wall-of-text feel where clauses get technical.

Anchor Links

Every clause has its own anchor. When support cites a paragraph, you receive a direct link that opens at that line, not the top of a long document you then have to scan.

Change Notes

A short change note sits at the head of each policy page. It summarises the latest revision in one sentence so you don't need to diff the full text to see what moved.

Print Layout

Policy pages carry a print stylesheet. If your records require a hard copy of the terms you accepted, the printed version comes out cleanly with headings, dates and clause numbers intact.

Contact Footer

Each policy closes with the relevant contact route — privacy mailbox, compliance line or complaints address — so you never finish a clause wondering where to send a follow-up question.

Frequently Asked Policy Questions

The terms page on this legal hub always carries the live version. The footer shows the last-updated date, and the change note at the top describes what shifted in the most recent revision.

Send a request to our privacy mailbox from the email tied to your account. We log the ticket, verify identity and return the records within the window stated in our privacy clause.

Our policies apply where local law permits and the account flow validates supported regions before activation. If your region isn't supported, the eligibility clause explains what happens to a pending sign-up.

Yes. We archive previous wording rather than overwriting it. Ask the policy mailbox for the version dated to your sign-up and we'll send the archived file along with the current one.

One account per person, honest identity records, no automation against the lobby, and no sharing credentials. The acceptable-use page lists the full set with examples of what triggers a review.

Material changes are notified in-account and by email to the address on file. Minor wording fixes appear in the change note at the head of the affected page without a separate notice.

DANA, OVO, GoPay and QRIS appear as contextual references in our terms and privacy wording, describing how transaction records are handled. They aren't endorsements and the wallets retain their own separate policies.