Reference
Know what is kept about your traffic
See what is stored about your tunnels' traffic, how long it is kept and how to remove it sooner.
- Applies to
- All plans
- Time
- About 3 minutes to read
- What it changes
- None. This page explains; it changes nothing.
- Last reviewed
- , by Product documentation
Tunnel data
| What | How long | Notes |
|---|---|---|
| Request records in the inspector | 24 hours, and the newest 500 per tunnel | Durable tunnels only. Sensitive header values and query values are removed before storage. |
| Request and response bodies | 24 hours | Only if you turn on Keep bodies for the tunnel, and only the first 64 KiB of each. Bodies can contain secrets. |
| Held webhook requests | Until delivered, or 24 hours (Starter and Pro) or 72 hours (Team and Business) | Only if you turn on the webhook inbox. Stored with headers and body, unencrypted. Content is deleted when the request is delivered, fails or expires. |
| Record of a held webhook that finished | 24 hours | Time, method, path without the query string, status and attempts. No content. |
| Webhook signing secrets | Until you remove them | Stored encrypted and never shown again. |
| Authorized computers | Until you revoke them or the connector signs out | Listed under Connectors and devices. |
Everything else
The Privacy Policy lists everything we collect, why, and how long we keep it, including account data, abuse-prevention records and the providers that help us run the service. This page covers only what you control for your tunnels.
How to remove it sooner
Deleting a request in the inspector removes it. Deleting a tunnel removes its request records and any held requests. Turning off body capture or the webhook inbox stops new content from being kept.
What to do next
Related
This page is part of Security, privacy and reliability. Still stuck? Contact support.