Short-lived by design
Buckets are temporary. Automatic cleanup and per-bucket limits reduce long-term storage, while manual clear and delete actions let you remove active test data sooner.
Updated August 3, 2026
The production default deletes a bucket after 15 days without activity. A captured request updates the bucket’s last-activity time. Cleanup runs periodically, so deletion occurs after the threshold rather than at an exact second.
Deleting a bucket removes its captures from the active database. Once deleted, the capability URL stops working and the application cannot restore it.
A bucket is limited to 10,000 stored captures or approximately 50 MiB of stored request data under the production defaults. When a limit check finds either threshold reached, the oldest captures are removed in batches so newer evidence remains available.
These are safety ceilings, not storage guarantees. High-volume testing should use infrastructure you control with a retention policy designed for that workload.
Incoming request bodies larger than 1 MiB are rejected. In the dashboard, Clear requests removes every capture while preserving the endpoint and its response settings. Delete bucket removes the endpoint and all of its active captures.
Capability holders can perform those deletion actions, which is another reason to keep the bucket URL private. Deletion is not reversible from the product UI.
This notice does not promise an immediate erasure time for infrastructure backups or disaster-recovery media. Do not submit data whose handling depends on a guaranteed backup-erasure deadline.
The recent-bucket list is stored separately in your browser. Server-side deletion does not edit every browser that saved the URL; clear local site data if you also want to remove that history.