Deletion
Deleting something removes it from your account straight away — it stops being captured, stops being compared, and stops appearing anywhere in the dashboard.
Deleting cannot be undone. There is no restore, so treat every deletion as final. What we retain internally afterwards, and for how long, is covered in the privacy policy.
What you can delete
| Item | Deleting it also removes |
|---|---|
| Project | its environments, pages, capture batches, diff batches and notifications |
| Environment | its capture batches, diff batches and notifications |
| Page | the page and its per-environment settings |
| Capture batch | every page screenshot in that batch |
| Diff batch | every page result and diff image in that batch |
Deleting a container deletes what is inside it. The container disappears from view immediately; clearing out its contents happens in the background, so shortly after a large deletion you may still see some of its items in a list that isn't scoped to it.
Batches are deleted whole. A capture batch visits every enabled page in an environment, and a diff batch reports on every page it compared — so you delete the batch and its individual page results go with it. You cannot remove one page from a batch: the batch would claim to cover ten pages while showing nine, with nothing to explain the gap. To stop capturing a particular page, disable it for that environment instead, or archive the page to stop capturing it everywhere.
Organizations follow different rules — see Deleting an organization.
Capture batches and diff batches are independent
This is the one rule worth knowing, because it is how you control storage cost.
Deleting a capture batch does not delete the diff batches made from it. A diff batch is the result — the verdict, the per-page outcome, the diff images — and it is kept. It still tells you which environments were compared and when each side was captured. What it can no longer do is open the original screenshots, which are shown as Capture deleted.
So if you are keeping storage down, delete old capture batches and keep the diff batches. You lose the "before and after" screenshots, not the finding.
The reverse also holds: deleting a diff batch never touches the capture batches it was made from.
What deletion does not change
Work already done is still billed. Deleting a project does not un-run the captures it performed. Usage recorded before you deleted it stays on your invoice for that period.
Storage stops counting at the moment you delete. Screenshots and diff images are billed for the time they are stored, so deletion ends the charge — you are not billed for storage after the moment you deleted.
Your usage history stays available. Invoices, usage totals and the usage charts outlive the data they describe, so you can always review what you were charged for.
Retention — what gets deleted for you
Two limits apply automatically, independently of anything you delete yourself.
Capture and diff batches are kept for a limited time. Once a batch passes your plan's retention period it is deleted automatically, exactly as if you had deleted it yourself.
| Plan | Batches kept for |
|---|---|
| Discovery | 45 days |
| Team | 365 days |
| Business | 730 days |
Usage history has its own retention and is not affected by deleting the data it describes. Usage and storage charts go back 2 years, with hour-by-hour detail for the last 90 days and daily figures before that.
If you need data removed sooner than these limits — for example under a data protection request — contact us.
Archiving is not deleting
Archiving keeps everything and simply takes it out of active use. Nothing is removed by archiving.
| Archiving | Deleting | |
|---|---|---|
| Data kept | yes | no |
| Still counted for storage | yes | no — billing stops at deletion |
| Can be undone | yes | no |
Two things can be archived:
- A page, when it is no longer used but its history is worth keeping. It stops being captured in every environment, and its captures and diff results still link to it. See The life of a page.
- A notification, when you have dealt with it.
Both keep their archive date even if they are later deleted.
Deleting an organization
An Owner deletes an organization from its Settings page. Deleting it removes all its projects with everything inside them, ends access for every member, and removes the payment methods saved for it. It cannot be undone, and every Owner receives an email confirming it.
An organization cannot be deleted while it owes anything. Before you can delete one, it must be:
- on the Discovery plan — downgrade first if you are on a paid plan, and
- settled — no unpaid invoice, and none still being prepared.
The reason is practical: deleting an organization removes the interface you would use to pay. We will not put you in a position of owing an invoice you can no longer see or settle.
If the organization is not there yet, the delete button tells you what remains to be done. From a paid plan the way out is short: on the Billing page, downgrade to Discovery and choose Now. That closes the paid period at once — the rest of the period you paid for is not refunded — and invoices any usage above your allowance right away, unless it comes to less than $0.50. The invoice is charged to your card automatically, usually within the hour; as soon as it is paid, the organization can be deleted. If there is nothing to invoice, it can be deleted a few minutes after the downgrade.
Organization records are retained after deletion regardless of plan, because billing and tax records must be kept. Invoices already issued remain valid, but the Billing page goes with the organization: download the invoices you need before deleting, or write to us for a copy afterwards.