Trust center

Privacy

This page describes what actually happens to your data, precisely. When behavior and wording disagree, that is a bug — please report it.

Your files

Uploaded files are processed in memory on the server for the duration of the request and are not written to durable storage. PDF parsing uses a temporary file that is deleted immediately after extraction.
Files fetched by URL are subject to the same handling.
Nothing about a file is retained after the response is sent — unless you opt in to saving that analysis (below).

The app works without a key: parsing, statistics, quality checks, correlations and evidence are computed deterministically server-side.
If you add an Anthropic API key, it is kept in this browser — in session storage by default (cleared when the tab closes), or in local storage only if you tick "Remember this key on this device".
When you run an AI feature, the key is transmitted with that request to this app's backend, which forwards it to Anthropic. It is used for that request only. It is never stored server-side, never written to logs, and never included in saved analyses or error messages.
We do not claim the key "never leaves your browser" — it necessarily travels with each AI request. It is not retained anywhere along the way.

Only when you use AI features, and only with your key: column names, computed statistics, correlations, evidence objects, the data-quality summary, a small labelled sample of rows (or a text excerpt for documents), and your question.
With no key configured, nothing is sent to Anthropic.

By default, nothing is stored server-side. Every analysis is transient.
If you tick "Save this analysis to history and enable a share link", the result is stored in the app's database: an anonymous session identifier, the filename, file type, chosen model, your question, and the full analysis payload — statistics, evidence, AI text if any, up to 100 chart sample rows, and up to 10 source-row excerpts per evidence item containing only the columns used by that finding. Your API key is never part of it.
Saved analyses are retained until you delete them from the history list. Anyone with a share link can view that saved analysis; deletion requires the browser session that saved it.

No analytics, tracking pixels, or third-party scripts other than the charting library. That is the only request any page makes to another host — the type faces are served from this app, so this page contacts nobody else.
A random session identifier is kept in your browser's local storage to group your saved analyses; it is sent only to this app.
Requests are rate-limited by IP address in memory; addresses are not durably logged.