Redax Privacy Policy
Last updated: October 29, 2026
Redax is a Chrome extension that redacts sensitive information (IDs, GUIDs, secrets, and personal information) on web pages you choose. This policy explains what Redax does with data.
The Short Version
Redax processes page content only on your device, in your browser. It does not collect, store, transmit, sell, or share any of the content it reads, and it has no analytics or tracking.
What Redax Reads
On sites you have enabled, Redax reads the visible text of the page and the values of text fields so it can find patterns such as GUIDs, API keys, email addresses, and card numbers. This happens locally, in memory, while the page is open. Redax does not keep a copy of page content and never sends it anywhere.
What Redax Stores
Redax saves your settings with Chrome's storage API: which detectors are on, your paused sites, and your display style. If Chrome Sync is turned on, Chrome syncs these settings across your signed-in browsers. Redax stores nothing else.
Network Requests
Redax makes no network requests. It never sends page content, browsing history, or URLs anywhere.
Permissions
- storage: saves your settings.
- scripting: runs the redaction script on sites you have enabled.
- activeTab: when you open the popup, lets it see which site you are on and which other sites that page loads frames from, so it can offer to enable Redax there.
- Site access (optional): Redax asks for access only when you enable it on a site or on all sites. You can remove access at any time in Redax settings or on Chrome's extensions page.
Changes
If this policy changes, the updated version will be posted at this URL with a new date.
Contact
Questions: support@redax.pro