DEKREL

Policy draft

Billing and Refund Terms

Preview draft, May 2026

This preview page explains the billing boundary while pricing and usage calibration are still being finalized.

Current billing state

  • Public pricing may show directional Core, Pro, and Power plans, but live checkout is not active until the payment provider or merchant of record and final terms are connected.
  • Exact included usage, top-up pack shape, dunning day counts, internal weighted formula, markup, and heavy-run multipliers remain a separate billing pass.
  • Usage should be explained publicly as usage, remaining usage, additional usage, or estimated usage, not as raw tokens or hidden internal units.

Refund and payment boundary

  • Refund, cancellation, failed-payment, tax, and invoice wording must be aligned with the final merchant of record or payment provider before paid launch.
  • Auto-refill remains off unless a user explicitly opts in, and expensive steps should have approval boundaries where required.
  • This preview does not process paid checkout.

Before paid launch

  • The final billing terms must be reviewed with the exact service name, legal entity, payment provider, support contact, and pricing table.
  • Do not treat this draft as the final refund policy.

Final review checklist

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.