ChatData privacy policy

ChatData is built for trusted analytics work in Claude Code, Cursor, and Codex. The product is local-first by default, with explicit portal and managed-sync features when you choose to use them.

Last updated June 27, 2026

What ChatData stores locally

The ChatData plugin stores local trial, profile, settings, proof, metric, correction, and company-repo state on your machine.

~/.chatdata/license.json
~/.chatdata/profile.json
~/.chatdata/settings.json
project-level .chatdata/ files such as metrics, proof receipts, corrections, and company repo manifests

What is sent to getchatdata.com

When you start a trial or log into the portal, ChatData stores your email, name if provided, role if provided, company domain, trial start time, portal session, ChatData token, salted password hash after email verification, verified-email timestamp, and hashed single-use email verification or password reset tokens when those links are requested. Raw passwords and raw single-use tokens are not stored.

When MCP or plugin sync is enabled, ChatData stores the selected context you approve for the workspace. That can include metric definitions, answer paths, corrections, proof receipts, sources, caveats, review decisions, and trusted query references. ChatData stores workspace memory in the MCP context layer and portal review state.

MCP context layer

ChatData uses the MCP context layer and portal review state as the shared workspace memory. If you provide a GitHub SQL or dbt link, ChatData treats it as a customer-owned source-of-truth reference for proof receipts and dashboard tie-outs.

Telemetry and tracking

Plugin telemetry is off by default. ChatData does not add third-party tracking pixels to lifecycle emails. The website uses Cloudflare infrastructure logs and D1 database records needed to operate the portal, trial, email, MCP, review, and context-sync flows. Founder admin views are aggregate product operations views and do not show raw context content, raw event metadata, passwords, or single-use tokens.

For support troubleshooting, a verified platform admin can start a short-lived support view for an active verified user. Support view requires a reason, is logged, shows a visible banner, and blocks workspace writes such as API-key creation, consent changes, teammate invites, billing actions, and context edits.

Email

ChatData sends trial access and lifecycle emails from support@getchatdata.com using Cloudflare Email Service. Emails are used to help you start the trial, learn the core workflows, and decide whether ChatData is useful enough to keep.

What ChatData does not do

ChatData does not sell personal data.
ChatData uses ChatData-owned support and lifecycle email routes for customer communication.
ChatData does not ask you to host workspace memory in source control.
ChatData does not claim data is trusted merely because an AI produced it. Trust artifacts, validation, and proof receipts are the product.

Data deletion and questions

To request deletion of portal records, lifecycle email enrollment, or workspace context, email support@getchatdata.com.