DEKREL

Support draft

Contact and Support

Preview draft, May 2026

This preview page defines the support surface that must exist before broad public launch. The final public contact address is still pending.

What support covers

  • Account access, sign-in trouble, workspace ownership, privacy requests, billing questions, and safety review questions need a clear support path.
  • Support views must stay metadata-only by default and must not expose raw private project contents without the locked consent, incident, reason, TTL, and audit boundaries.
  • Internal model routing, hidden prompts, secret keys, and private troubleshooting records are not support-facing user content.

Preview limitation

  • A final support email or helpdesk URL is not locked because the final service name and domain are not yet chosen.
  • Until then, this page is a readiness placeholder so the product has a canonical support route without pretending the final support operation is live.

Before launch

  • Choose the final support address or helpdesk, connect it from this route, and confirm the privacy, account, billing, safety, and abuse-report workflows.
  • Keep support, policy, and account links available from the platform profile menu and public/legal surfaces.

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.