R RedactBeforeSend Effective date: July 16, 2026

Privacy policy

RedactBeforeSend is built to review and redact sensitive browser content locally before you share it.

This policy explains how the RedactBeforeSend Chrome extension handles text, screenshots, browser storage, permissions, and privacy disclosures for the current public extension package.

Local-first processing Core text redaction and screenshot review happen in the browser extension. The current extension does not require a RedactBeforeSend backend for detection.
No analytics or accounts The current extension does not include analytics, telemetry, session replay, user accounts, billing, or a hosted customer database.
User-controlled output Copy, paste, and download actions are triggered by the user after reviewing redacted text or images.

Single Purpose

RedactBeforeSend helps users review and redact sensitive text and screenshots before sharing browser content. It detects common PII and secret-like patterns locally, supports Safe Paste warnings, selected-text redaction, local custom detectors, and screenshot review/export so users can copy, paste, or download sanitized output.

Data The Extension Handles Locally

RedactBeforeSend may process the following information inside the extension when you choose to use a redaction workflow:

The current extension does not send this content to a RedactBeforeSend server for detection, analytics, or storage.

What We Do Not Collect

Browser Storage

The extension uses browser-managed extension storage to remember preferences and support local workflows. Stored data may include redaction style, Safe Paste behavior, site-specific settings, local custom detector rules, and temporary screenshot handoff state.

Chrome may sync extension storage across signed-in Chrome profiles depending on the user's browser settings. RedactBeforeSend does not operate its own sync service in the current extension.

Chrome Permissions

activeTab Used only when the user explicitly starts screenshot review from the current tab. It lets the extension capture the visible tab for local review and redaction.
clipboardWrite Used to copy redacted text or redacted images after the user chooses a sanitized output. The extension does not use this permission to read clipboard contents in the background.
contextMenus Used to add a right-click redaction action for selected page text.
downloads Used to save a reviewed redacted screenshot as a PNG when the user chooses the download action.
storage Used to save preferences, Safe Paste settings, local custom detectors, and temporary screenshot handoff state.
Host access and content scripts Used on supported web pages so the extension can detect paste events, show the Safe Paste review guard, and support user-triggered selected-text redaction. The extension does not send page content to a RedactBeforeSend backend.

Remote Code

The current extension package does not load remote JavaScript, remote modules, remotely hosted WebAssembly, or eval-based remote code. JavaScript, WebAssembly, OCR assets, and extension code are included in the packaged extension.

Chrome Web Store Data Categories

Depending on what a user chooses to review, the extension may locally process content that contains personally identifiable information, financial or payment-like information, authentication information, personal communications, location-like text such as addresses or IP addresses, and website content. This local processing supports the extension's single purpose: helping the user redact sensitive content before sharing it.

Detection Limits

RedactBeforeSend is a review aid, not a guarantee that every sensitive value will be found. Rule-based detectors and OCR can miss unusual formats, typos, unlabeled names, small text, compressed screenshots, dense layouts, browser-restricted pages, and organization-specific identifiers. Users should inspect redacted output before sharing it.

Future Services

If RedactBeforeSend later adds accounts, billing, cloud sync, team administration, hosted policy APIs, analytics, or any backend processing of user content, this policy should be updated before those services launch or before a new Chrome Web Store version is submitted.

Contact

For privacy questions, use the developer support contact published on the Chrome Web Store listing for RedactBeforeSend. If a dedicated privacy contact is added later, this policy should be updated before the listing is resubmitted.