# What this app sends, and how to check

CyberChef's hosted workbench runs in your browser at cyberchef.tools. Its
operations process your input locally. The optional analytics collector does
not receive the material you are working on.

| | Hosted workbench |
|---|---|
| Processing | in your browser |
| Product analytics | optional first-party collection on this domain, after consent |
| Analytics storage | Cloudflare D1, behind a Cloudflare Pages Function |
| Service worker | same-origin assets only |
| Endpoint tier | optional, off by default |
| Offline use | workbench functions after its assets have loaded |

The private offline workbench is a separate build with no analytics runtime.
The public extension frames the hosted site and uses its analytics choice.

## What the hosted site sends

**Its own files.** HTML, scripts, styles, fonts, operation modules and WebAssembly
come from this site. Cloudflare receives the ordinary request metadata needed
to serve them.

**Optional analytics.** After you select **Allow analytics**, the browser sends
small JSON batches to `/api/analytics` on this domain. They contain random
browser/session/page/event identifiers, fixed product event labels, permitted
counts and timing buckets, authored page paths, coarse acquisition source and
bounded browser/device context. The server may add country from Cloudflare
metadata. The complete event inventory is in [the privacy policy](privacy.html#analytics).

There are no input/output contents, searches, filenames, clipboard contents,
keys, indicators, recipe names/contents/arguments, tool results, raw errors,
query strings, URL fragments or raw referring URLs in analytics. The collector
rejects fields and labels outside its schema. The analytics database does not
store IP addresses or full user-agent strings. Cloudflare still sees network
metadata as the host.

The **Analytics settings** control allows withdrawal. Declining, Global Privacy
Control and Do Not Track stop collection. Withdrawal clears local analytics
identifiers and unsent events; previously received records expire under the
published retention policy. A blocker can block the collection route without
breaking the workbench. Analytics has no role in completing an operation.

**Optional Endpoint lookups.** These require enabling the Endpoint tier and
pressing a labelled control. The selected vendor receives the indicator and
credentials necessary for that lookup. The local Network ledger records the
provider and outcome, not the indicator or key.

**Explicit network operations.** Upstream operations such as Show on map,
DNS over HTTPS and HTTP request perform their documented network requests when
used in a recipe. Those requests are separate from product analytics.

## Verify the behaviour

1. Open browser developer tools, choose **Network**, enable **Preserve log**,
   and reload. Decline analytics: there should be no analytics POSTs.
2. Open **Analytics settings** and allow analytics. Inspect the request body
   of `/api/analytics` while using the workbench. It should contain only the
   documented identifiers, fixed events and context. No user content should
   appear in its body or referrer header.
3. Put a distinctive test string in the input and use a URL containing a
   different test string in its query or fragment. Search the analytics
   payloads for both. Neither should appear. Use synthetic text for this test.
4. Withdraw consent and use the app again. No further events should be sent;
   an already in-flight request cannot be recalled.
5. Block `/api/analytics`, or disconnect the network after the workbench has
   loaded. Local operations should continue to work. Endpoint lookups and
   network operations still need connectivity.

An intercepting proxy such as Burp Suite, Fiddler or mitmproxy can independently
inspect traffic. The app's **Tools → Network** screen shows fetched resources
and its Endpoint lookup ledger, but inspecting network traffic is the stronger
check: first-party analytics appears under this site's own origin.

## Storage

Workbench material stays in localStorage (recipes, preferences and keys) or
IndexedDB (imported IOC lists). Consented analytics identifiers and the analytics
choice also use localStorage, but are stored separately from that material.

First-party analytics event/session records are kept for 90 days, visitor
metadata for at most 365 days, and daily aggregates for 730 days, with daily
scheduled expiry. Existing Google aggregate archives are separate and have no
automatic expiry. Clearing local site data does not erase records the analytics
collector has already received.
