Skip to content

Where your data goes.

It runs on a machine you control. Here’s exactly what leaves it, and what stays.

What runs where.

A machine you control
  • TestPilot appNext.js, behind each user’s own sign-in
  • SchedulerRuns inside the app; checks every minute
  • ChromiumThe browser every web test runs in, driven by Playwright
  • SQLite databasedata/testpilot.db: projects, tests, results, saved logins
  • Files on diskdata/projects/<id>/: screenshots, videos, reports
  • Claude CodeSigned in with your Claude account
What leaves it
Your websiteEvery crawl and every test.
Anthropic, through Claude CodePage HTML and element lists, screenshots for vision, test text, failure details, and documents you upload for context.
Your SMTP serverReport emails, scheduled runs only, when you set it up.
Google and CloudflareOnly when your site doesn’t answer: a check that TestPilot itself is online.

Nothing goes to the TestPilot team.

What the AI sees.

Through Claude Code on your machine. No TestPilot server in between.

Page HTML

To write tests and find a moved element again.

Learn more

Page HTML and the lists of elements the crawl found, to write tests and to find a moved element again.

Screenshots

Only for checks that need vision.

Learn more

Screenshots, for checks that need vision (a produced result, a visual check, an assistant’s reply).

Tests and failures

To explain why a test failed.

Learn more

Test titles, descriptions and steps, and the details of a failure, to explain why it failed.

Your documents

Uploads you add for extra context.

Learn more

Documents you upload for extra context, and the words around an upload field when a sample file has to be written for it.

How it reaches Anthropic

AI runs through the Claude Code command-line tool on the machine running TestPilot, signed in with that machine's Claude account. There is no TestPilot server in between: what Claude needs goes from your machine to Anthropic, and Anthropic's terms for that account apply.

Screenshots and page HTML contain whatever the page shows. Point TestPilot at a test account with test data wherever you can.

What stays local.

All in its data folder (DATA_DIR, ./data by default).

SQLite database

Projects, tests, runs, results, saved logins.

Learn more

data/testpilot.db: projects, tests and their step history, runs and results, what the crawl learned, cached AI answers, saved logins and the email log.

Files on disk

Screenshots, videos, reports, your data files.

Learn more

data/projects/<project id>/: screenshots, videos, reports and the data files you upload.

Cached AI answers

Reused instead of asking twice; expire in 30 days.

Learn more

Claude’s answers are reused when the same question comes up again (the same page crawled again, the same failure, the same document), so it isn’t asked twice. They expire after 30 days; AI_CACHE=off turns this off.

Passwords and 2FA secrets.

Stored locally

In the local database, not encrypted at rest yet.

Never sent back out

Settings only show which ones are set.

Only to your site

Tokens and Basic Auth go to your site’s host only.

Behind one password

Signed session, checked on every request.

Tip: use a dedicated test account, so a leak of this machine never reaches a real person's account.
Every detail
  • Passwords, bearer tokens, saved sessions and authenticator secrets are stored in the local SQLite database.
  • They are not encrypted at rest today. Protect that machine’s disk (full-disk encryption, for example) and who can sign in to it.
  • The app never sends them back out through its API: a project’s settings only say which ones are set, and leaving one empty on save keeps it.
  • A bearer token and Basic Auth are only sent to your site’s host, never to other sites a page loads.
  • Everyone signs in with their own email and password and sees only their own websites. The session cookie is signed, and checked on every request.

Every outgoing connection.

All that TestPilot’s own code connects to.

  • Your websiteEvery crawl and test
  • AnthropicWhat the AI needs
  • Your SMTP serverOnly if you set up email
  • Google & CloudflareOnly when your site doesn’t answer
  • The TestPilot teamNothing
When and what, in full
Outgoing connections TestPilot makes
ToWhen and what
Your websiteEvery crawl and every test, from a Chromium browser that never hides that it’s automated.
Anthropic, through Claude CodeWhat the AI needs (the list above), under the Claude account signed in on that machine.
Your SMTP serverOnly when you set up email: the PDF report after a scheduled run, or a short “Site down” alert.
Google and Cloudflare (by default)Only when your site doesn’t answer: a request to a well-known address to tell an outage from TestPilot’s own connection. The addresses can be changed (CONNECTIVITY_CHECK_URLS).
The TestPilot teamNothing. TestPilot doesn’t report back to us.

Deleting data.

Delete a project

Tests, runs, files, crawl data and cached answers go.

Learn more

Deleting a project removes its tests, runs and results, data files, crawl knowledge, cached AI answers, and its folder of screenshots, videos and reports.

Delete a run

Its results, screenshots, videos and report go.

Learn more

Deleting a run removes its results, screenshots, videos and report.

Already sent to Anthropic

Handled under your Claude account’s terms.

Learn more

What was already sent to Anthropic is handled under your Claude account’s terms, not by TestPilot.

Questions from your security review?

Bring them to a demo. We'll show where each of these lives in the running product.