Your analysis stays yours.

What usage reporting sends

When you run the standard email-linked dashboard setup, it sends the client name, ChatData skill, plugin version, workflow start or completion, timestamp, elapsed seconds, and random event and workflow IDs. A revocable installation credential connects these events to your account. We do not send file paths, project names, prompt hashes, or arbitrary error text.

We use these events for your personal usage dashboard, product improvement, and support. Tracked prompts count explicit ChatData workflow starts, not every prompt you send to your AI. The dashboard starts with editable estimates of 60 minutes per workflow and $125/hour. It estimates time saved from the difference between that baseline and observed workflow time, then multiplies the result by the hourly value to estimate analysis cost saved. These are estimates, not readings from an AI provider bill. Calculation helpers remain local.

Dashboard linking is part of the standard installation flow. The setup notice describes usage reporting before it creates one command tied to your verified email and chosen client. That command contains a single-use setup code, which expires after 20 minutes and is exchanged automatically over HTTPS for a revocable credential stored on your machine. It does not ask you to paste a secret or use an interactive terminal. Existing unlinked public source installations do not begin sending telemetry automatically. The official ChatData skills stop before analyzing your data until the current client is linked to your verified email; setup, status, and update commands remain available so you can repair the installation. You can disconnect locally or revoke an installation in your dashboard. Revocation stops new reporting; it does not automatically erase previously reported events.

Your account and email

We store your email, verification and sign-in records, usage events, installation credentials in hashed form, estimate settings, and consent choices. Personal emails are welcome. Sign-in links verify that the dashboard belongs to you. You do not need a password.

We send sign-in and essential account emails. The signup form explains that creating an account also subscribes you to ChatData setup help, data science workflows, and product emails. You can unsubscribe in your dashboard. Signing in again does not change an existing email preference. We do not sell personal data.

Your local context folder

Local onboarding inventories names, sizes, and modification times in one project folder you choose. It creates a report on your machine without uploading that inventory or reading conversation history. Source and evidence checks read files you explicitly reference. The semantic model, file paths, fingerprints, and review notes are not included in ChatData usage telemetry. Your AI client may read files you provide under its own data policy.

Other services

Cloudflare hosts the site, database and email delivery. The website uses Cloudflare’s analytics/performance beacon and processes ordinary request information such as IP address, browser and timing for delivery and security. Application logs record request method and path; configured PostHog reporting handles server errors. These services are separate from the plugin’s content-free usage events.

GitHub handles public source downloads and updates. At Claude Code startup, ChatData can check the latest public GitHub release at most once a day to show an update notice. The request sends no account token, prompt, dataset, path, or project information; GitHub receives normal connection information such as IP address. The result is cached locally. Set CHATDATA_UPDATE_CHECK=0 in Claude Code’s environment to disable checks. Updates install only when you request them. Your AI client and connected services have their own processing and retention policies. Claude Code, OpenAI, Cursor, Cloudflare, and GitHub describe their practices.

Your local Claude footer

On the first Claude Code session after installation, ChatData configures its own footer and saves a local backup of the previous setting. The previous footer is not run or displayed. Footer setup does not enable usage reporting. If you later choose another footer, ChatData respects that choice. Local disconnect restores the saved setting when ChatData still owns the footer.

Your controls

Your dashboard lets you export account usage, change marketing preferences, revoke installations, and delete your individual account and reported usage. We keep account usage until you delete it. We regularly remove expired sign-in links, sessions, and temporary rate-limit records. Infrastructure backups and security logs may persist under provider retention policies. Deleting the account does not delete local analyses or copies held by your AI provider.

Local files, client history and backups remain under your control. For access, correction, deletion or privacy questions, contact support@getchatdata.com. We receive the information you choose to send for support. The earlier hosted service has a separate historical policy.