What we store, and why.

What we store

Account

your e-mail address and a salted hash of your password

Team

its name, settings, members and invitations

Sites

the URLs you add; a test account per site if you enter one, set by admins and never shown again

Results

verdicts, reasons, the runner's log with the test account blanked out, and the screenshots behind failures

Audit log

changes made in your team and the address they came from, visible to admins

Where the tests run

Your runner

the browser runs on your machine; we receive what it uploads and nothing else

Hosted

one of our runners receives the site's test account for the run, opens the site, uploads the results, and keeps neither the account nor the pages afterwards

Self-hosted

sends nothing to us at all

Who else sees data

Mail relay

invitations, password resets and alerts (site names, test names, reasons)

Your webhook

the same alert as JSON, to the address you set

Stripe

your e-mail and plan when you pay

The model

the sentence you type when drafting a test

Share links

a run's verdicts and screenshots, to anyone holding the link, until you revoke it

Nothing is sold or shared for advertising.

How long

Runs

the history period of your plan; 90 days after a trial ends or a subscription is cancelled; a shared run a year

Account

while it exists; the audit log keeps the e-mail on the actions it records for 730 days, also after deletion

Deleting

a run removes its results and screenshots at once; a site keeps its past results until they expire; a team removes everything it held and ends its subscription

Disk

when the data volume runs low, the oldest evidence past a week goes first, teams that never paid before paying ones

Backups

an operator's backups follow the operator's own schedule