A little help.
A little more privacy.

Open Veil’s popup and check that Master Protection and the relevant sensitivity category are enabled. In Settings, check that the domain is not excluded. Check Chrome’s extension site-access settings, then reload the page.

Chrome internal pages, the Chrome Web Store, and other browser-restricted pages block extension content scripts. Try a regular website. For local files, enable Allow access to file URLs in Veil’s extension details.

Automatic detection matches structured patterns and may miss some values. Use element, text, or area blur for anything else, or add a custom regex in Settings. Review your screen before sharing.

Reveal a value using the configured click or hover action, disable its category, or exclude the domain in Settings. Peek All temporarily reveals masked values; avoid using it while sharing sensitive content.

Use Clear All in the floating toolbar on that page. Saved manual element and area blurs are associated with the page’s origin and path. Removing the extension clears its local extension storage.

No. Redaction runs locally. Settings and manual blur locations are stored in Chrome’s local extension storage. See the privacy policy for details.

Record your Chrome version, Veil version, the steps that caused the issue, and any extension error message. Use synthetic example data and remove credentials and personal information from screenshots.