Skip to content
midgeDocs
PrivacyRedaction
Privacy

Redaction

How Midge removes passwords, tokens, cookies and keys in your browser before a report is uploaded.

Redaction happens in your browser, before upload. There is no setting to turn it off.

WhatWhat happens
Passwords and secret fields in request and response bodiesReplaced with [REDACTED]
Cookies and authorization headersReplaced
Tokens in addresses (?token=, ?access_token=, …) and passwords in addressesReplaced
API keys (Stripe, AWS, GitHub, Slack, Google, LLM keys), bearer tokens, JWTs, private keysReplaced
Card numbersReplaced
Email addresses and phone numbersHalf masked, like j***@example.com
Text typed into fieldsNever recorded

In screenshots and tab recordings, password fields, card fields (autocomplete="cc-…") and anything marked data-midge-blur are blurred while Midge captures. Screen recordings are not blurred.

The review shows how many values were removed and of what kind, so you can check before you create the report.

Hide more of your app

Add data-midge-blur to any element to blur it in screenshots and tab recordings and to leave it out of instant replays:

html
<div data-midge-blur>Account balance: $12,480.00</div>