Data handled by the service
The service is designed for short-lived synthetic integration tests. It necessarily stores the HTTP request data you send so the dashboard can display it.
Updated August 3, 2026
A bucket record includes its random ID, display name, creation and activity times, response configuration, and creator IP for abuse limits. A capture includes the HTTP method, headers, query parameters, body, sender IP, and timestamp.
Bucket IDs are not published intentionally, but possession grants access. Do not treat an unguessable URL as permission to submit someone else’s personal or confidential data.
Public pages use Google Analytics 4 to measure page views and product events such as endpoint creation, URL copying, synthetic requests, and the milliseconds from endpoint creation to the first capture. Bucket IDs, request bodies, and capture URLs are not sent as analytics event parameters.
UTM campaign values may be stored in session storage to attribute endpoint creation. Endpoint timing is also stored in session storage and consumed after the first matching capture.
The recent-bucket list and visual theme are stored in your browser. They help you reopen buckets but are not an account or server-side recovery mechanism. Clearing site data removes that local history.
A local history entry can remain after the server deletes a bucket; opening it will fail and the application removes the stale entry.
Network infrastructure and application logs may process connection metadata needed to operate and protect the service. The product does not need you to create an advertising profile or account.
Your safest privacy control is data minimization: use invented people, IDs, emails, tokens, and payload values; clear captures after testing; then delete the bucket.