Privacy Policy Changelog

All material changes to the Clarus Privacy Policy are documented here.


April 19, 2026 — Per-provider AI retention language and sub-processors page

Version: 1.2

Honesty pass on §3 (AI Features and Third-Party AI Providers) and a new dedicated Sub-processors page.

  • §3 now cites each provider's specific retention terms on the tier we actually use. Clarus is on the default commercial API tier for both Anthropic and Google — not Zero Data Retention or an equivalent enterprise tier. The policy now states this explicitly and points to the specific terms documents at anthropic.com/legal/commercial-terms and ai.google.dev/gemini-api/terms.
  • Upgrade path named. §3 now documents the intent to upgrade to Anthropic ZDR and Google's enterprise terms when funded, with a commitment to update the policy before the upgrade takes effect.
  • OpenAI and Fireworks AI explicitly called out as unused. They had been listed in earlier drafts as potential providers; the current policy confirms no user content is routed to either today and sets a 30-day-notice commitment before that changes.
  • New /sub-processors page. Every third party that receives user content or PII now has a dedicated page with purpose, data processed, hosting region, and a DPA link. The page explicitly lists what is not in use (Google Analytics, Sentry, advertising/retargeting pixels, session replay, OpenAI, Fireworks).
  • §4 now points to the sub-processors page for the full list.

No change to the no-training commitment or the 90-day AI-log retention.


April 19, 2026 — Service-level coverage and single source of truth

Version: 1.1

The Privacy Policy was expanded from marketing-site-only coverage to cover the entire Service (marketing site and signed-in application) as a single document. Key additions and clarifications:

  • Account and Service coverage added. Sections now describe account information, user content, AI-feature processing, third-party AI providers (Anthropic and Google), our no-training commitment, 90-day AI-interaction-log retention, GDPR / CCPA / Oregon rights, international transfer safeguards (Standard Contractual Clauses), and a 72-hour breach notification commitment.
  • Accurate tracking language. The "What We Do Not Use Today" section was retained and extended to the whole Service: no Google Analytics, no advertising or retargeting pixels, no session replay or heatmap tools, no attribution cookies, no localStorage-based campaign tracking. We use Plausible Analytics (cookieless) for both the marketing site and the signed-in application.
  • Sharing table clarified. The sub-processor recipients list now reflects actual vendors: AI providers (Anthropic, Google), Polar.sh (billing), Plausible (analytics), Resend (transactional email), and cloud infrastructure providers.
  • Encryption disclosure added. Section 9 now names application-layer AES-256-GCM envelope encryption for user content in addition to TLS for data in transit.
  • Consolidated source of truth. Editorial-stage duplicates previously held in apps/marketing/design/ have been retired. The only source of truth is apps/marketing/src/content/legal/, enforced by a CI check.

No change to the core commitment that we do not sell your data, do not serve targeted advertising, and do not use your content to train AI models.


April 5, 2026 — Initial Release

Version: 1.0

This is the first published version of the Clarus Privacy Policy. No prior version exists. Key provisions include:

  • Privacy-first attribution: Campaign attribution uses URL parameters and server-side conversion logging rather than analytics cookies or browser storage.
  • Cookieless Plausible analytics: The site uses Plausible Analytics for pageviews and CTA conversion measurement without analytics cookies or localStorage-based attribution.
  • Tracked CTA disclosures: The policy explains how landing paths, UTM parameters, referrer information, CTA IDs, and conversion timestamps are used when someone clicks a tracked signup CTA.
  • Operational contact details: The policy now includes a working email and mailing address for privacy requests.