Terms of Service
This legal hub mirrors the structure of our terms of service page — same clause numbering, same definitions list, so cross-referencing between documents stays consistent for every reader.
This is where we put the legal side of dewajudi in plain language. We cover the terms that govern your account, how we handle disputes, what jurisdiction rules...
Our legal posture is straightforward: dewajudi operates where local law permits and we serve supported regions only. Account holders accept our terms of service, privacy policy and cookie notice when they register, and those documents govern the contractual relationship between you and us. We retain the right to refuse or close accounts that fall outside supported jurisdictions, and we follow data-handling rules
that align with regional expectations. Disputes are first handled by our policy desk; escalation paths are written into the terms themselves. If a clause changes, we notify account holders before the new version takes effect, so you always know which policy version applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every policy document carries a version number and effective date. You can see exactly which terms applied when you signed...
Alongside the formal clauses we publish plain-language summaries so you understand what each section means in practice, without needing a...
Material policy changes trigger account-level notifications before they take effect, giving you time to read, ask questions or close your...
Our privacy policy documents what data we hold, how long we keep it and which third parties touch it. Nothing...
Supported regions are listed explicitly and we update the list when local law shifts. You always know whether dewajudi serves...
Policy decisions on your account — verifications, restrictions, closures — are logged with timestamps so any review request can reconstruct...
This legal hub mirrors the structure of our terms of service page — same clause numbering, same definitions list, so cross-referencing between documents stays consistent for every reader.
Privacy clauses referenced here use identical wording to the standalone privacy page. No surprise reinterpretations between documents that would leave you guessing which version controls.
Cookie categories named in this hub match the cookie notice exactly, including the optional-versus-required split and the vendor list maintained on the dedicated cookie page.
Conduct expectations summarised in our acceptable-use page are echoed here in shorter form, with the full enforcement ladder kept on the dedicated page for clarity.
The escalation steps described here are the same ones spelled out in the dispute resolution page, including timelines for first response and the formal review window.
Identity verification rules in this hub align with the KYC policy page word-for-word on document types accepted, retention windows and re-verification triggers for account holders.
Account closure language repeats our standalone closure policy, so whether you read it here or there, the steps to wind down an account stay identical.