When a support engineer at a big provider asks for a .har file, they are asking for a recording of your browser's network traffic, and a raw one carries live session cookies, Authorization headers, API keys and whatever was in your form posts. Sending it unredacted is a common way accounts get taken over. INTERCEPT strips the secrets and gives you a clean .har, in this tab. Included in the Sovereign Pass.
Paste a curl command or a block of request headers to put in a bug report or documentation. Cookies, Authorization, keys and tokens are replaced with placeholders.
Credential headers (Authorization, Cookie, Set-Cookie, X-Api-Key, X-Auth-Token, CSRF and the like), secret query and form fields (password, token, api_key, client_secret, session, otp and similar names), JSON bodies (any field whose name looks like a secret), and known key shapes anywhere in the file: JWTs, Stripe, GitHub, AWS, Google and AI keys, Slack tokens and PEM private-key blocks. Cookies keep their names so the log still reads sensibly; only the values go.
It is pattern-based redaction of the fields that carry credentials. It handles the standard places secrets live in a .har, and reports how many of each it replaced.
It is not a guarantee. A secret can hide in a URL path segment, a custom header this tool has not been told about, or the body of a response. The summary tells you what it found; skim the result before you send it, especially if your app uses unusual header names.
Nothing leaves this tab. The file is parsed and rewritten in browser memory.