DEKREL

Policy draft

Cookie and Analytics Notice

Preview draft, May 2026

This preview notice explains how DEKREL uses cookies and analytics before broad public launch. Final consent wording still needs review.

What is used

  • Authentication cookies keep a signed-in user connected to the right workspace.
  • Basic analytics events help us see whether the page loaded, whether the intake flow started, and where the interface becomes confusing.
  • Preview analytics should not include raw prompts, secret keys, hidden instructions, or private project contents.

What is not decided yet

  • A final cookie banner or consent manager is not locked until the final domain, launch regions, legal basis, and analytics stack are confirmed.
  • Marketing pixels, retargeting, and third-party ad tracking are not part of the preview baseline.

Before launch

  • The final public site must explain essential cookies, analytics use, opt-out or consent behavior where required, and the support path for privacy questions.
  • Analytics implementation should be checked against the analytics provider disclosure guidance and the product's privacy policy before broad launch.

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.