Policy draft

Terms of Service

Preview draft, May 2026

These preview terms define the basic service boundary while DEKREL is being prepared for release. Final legal wording still needs review.

Service scope

DEKREL helps users turn a plain project request into an AI-team workflow, draft outputs, reviews, and revisions.
Preview flows may use demo or limited provider behavior until production LLM, billing, storage, and connector integrations are fully enabled.
The service does not guarantee professional legal, medical, financial, security, tax, or compliance advice.

Users are responsible for the prompts, files, references, and instructions they provide.
Users must not request illegal, harmful, abusive, privacy-invasive, rights-infringing, or policy-evasion work.
Users must have the rights and authority needed for any connected account, file, domain, workspace, or external action.

AI-generated outputs may be incomplete, inaccurate, or unsuitable for regulated use without human review.
High-impact or regulated decisions require a human-review boundary before they are used outside the product.
The service may refuse, transform, pause, or route requests to review when safety, ownership, privacy, copyright, or platform-security boundaries apply.

Final terms must be aligned with the business entity, payment provider or merchant of record, refund policy, jurisdiction, support process, and production provider contracts.
Paid usage, rollover, refunds, dunning, checkout copy, and exact usage calibration remain subject to the billing pass.

This keeps the draft honest before public launch. It is a product/legal review checklist, not a claim that legal review is finished.

Final service name, company/legal entity, business address if required, and support contact.
Final production domain and every auth, policy, email, analytics, billing, and checkout URL that references it.
Confirmed processors and subprocessors for hosting, database, analytics, LLM providers, email, payments, and support tooling.
Model-provider data handling, prompt/output model-improvement controls, and whether user content is used to improve models.
Final data retention, deletion, export, correction, objection, appeal, and privacy request workflow.
High-risk-use boundary, human-review requirement, AI-disclosure requirement, refusal/review/appeal or rephrase path, and abuse-report workflow.
Cookie consent or analytics opt-out behavior by launch region.
Policy-change notice process and version/date history.
Payment provider, MoR/checkout flow, refund/cancellation terms, tax/invoice handling, and exact billing/support workflow once paid plans are enabled.