Diffmint is designed for local-first code review. This policy explains what data stays on your machine, what data can sync to the control plane, and which third-party services support authentication and billing.
Diffmint does not require full repository upload by default. The CLI and VS Code extension analyze local diffs and files on your machine first. Workspaces can choose to sync selected artifacts such as summaries, severities, trace IDs, provider metadata, and markdown reports to the control plane.
Our application uses Clerk to handle user authentication securely. All authentication processes, including sign-up, sign-in, and password management, are managed by Clerk. For detailed information about how Clerk processes and protects your data, please review their Privacy Policy.
Diffmint uses Polar for checkout, subscriptions, invoices, and customer portal sessions. Workspace billing metadata such as plan selection, seat usage, and subscription state may be synchronized with Polar to manage paid access. Do not store raw payment information in Diffmint itself.
Workspaces can control whether cloud sync is enabled and whether redaction is required before sync. We recommend redacting secrets, tokens, and customer data before storing synced review artifacts. Retention policies should be configured per workspace.
If your team needs custom retention, data processing details, or billing/privacy controls, document them in your workspace security runbook and internal support channels.
Last updated: April 2026