What Blurrrer does with your data

Every screenshot you drop into Blurrrer is decoded, OCR'd, scanned for sensitive patterns, and redacted inside your browser tab. The image, the extracted text, and the list of detected findings never touch a Blurrrer server — there is no Blurrrer server for user content.

• The initial HTML, CSS, JS, and fonts that make up the app itself, served from this domain.
• On first OCR run, the Tesseract.js worker script, WASM core, and English language data are fetched from public CDNs (unpkg.com and tessdata.projectnaptha.com) and then cached by your browser. These fetches don't include your screenshot.
• No analytics. No trackers. No error-reporting service.

The site enforces a Content Security Policy that blocks any other outbound connection, so a compromised script can't quietly exfiltrate an image.

Blurrrer sets no cookies. The extension uses chrome.storage.sync only to remember your per-site preference (Ask / Always / Never). That preference is scoped to your Chrome profile.

The extension intercepts pastes and file uploads on ChatGPT, Claude, Gemini, Copilot, Perplexity and Grok. It runs the same local detectors, shows a warning modal, and either sanitizes the text in place or opens this web app for image redaction. It never uploads intercepted content anywhere.