ChatData privacy policy

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

Last updated May 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, and hashed single-use password reset tokens when a reset is requested. Raw passwords and raw reset tokens are not stored.

When backend-managed sync is enabled, the plugin sends selected company-context files to getchatdata.com so the shared private repo can be updated. Those files can include metrics, answer paths, corrections, proof receipts, decisions, sources, playbooks, evals, and trusted query specs that you or the plugin choose to sync.

Company context repos

For launch customers, ChatData provisions a managed private repo named like ChatData-acme-com under a ChatData-controlled GitHub account. It is used as the shared source of truth for reusable analytics context. Customer-owned GitHub deployment is an enterprise setup option and is not included in the launch plan.

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, and repo-sync flows.

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 does not use Paras’s personal inboxes as a business sender, reply path, support inbox, or fallback contact.
ChatData does not require local GitHub credentials for ChatData-managed repo sync.
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 a managed company context repo, email support@getchatdata.com.