SnapRedact privacy policy
Publisher: Matheus da Silveira Mello
Contact: matheus.mello.developer@gmail.com
Effective date: 8 November 2026 (2026-11-08)
SnapRedact 0.1.1 processes screenshots on your device. No account, servers, uploads, analytics, advertising or tracking are used. Nothing is transmitted to us.
Consent and local processing
Before capture or scanning, choose Agree and continue in the popup. Not now leaves capture disabled. Settings shows live consent status. Withdraw consent blocks new captures, pending capture handoffs, and Copy/Download from existing editors. Agreeing again does not reauthorize an earlier capture.
Capture reads the current tab's pixels and page geometry: viewport dimensions, device pixel ratio, scroll dimensions and offsets, and element positions and styles needed to select a scrolling panel and hide repeated headers. Full-page capture scrolls temporarily, then attempts to restore scroll position and changed styles. Selection uses pointer or keyboard coordinates locally.
With Auto-blur enabled, the helper scans DOM text nodes (excluding SCRIPT, STYLE, NOSCRIPT and TEMPLATE parents) and input/textarea values (excluding password and hidden inputs) for email addresses, phone numbers and card-like numbers. Only matching rectangle positions reach the editor; extracted text is not sent or stored. This scan can miss sensitive content or mark harmless text and does not recognise text inside images. Excluding password fields from text scanning does not prevent visible credentials from appearing in screenshots. Review redactions before sharing. Blur and pixelation may leave information recognisable; prefer solid Cover or Crop for sensitive details and inspect the exported result. Quick copy bypasses manual review.
Session data and stored data
New capture frames, pixels, geometry, auto-blur rectangles and editing history stay only in session memory. The worker hands a capture once to its assigned editor tab. Original pixels and undo history can remain in the open editor even after redaction or export. Withdrawing consent blocks exports but does not erase those pixels; close the editor too. Closing or reloading the editor discards it; a worker restart before handoff can also lose a pending capture. No new capture database, capture store or Cache entry is created. Only an explicit Copy, Download, or the explicitly selected quick-copy capture action exports pixels.
Only these new persistent records are kept: default export format and Auto-blur/quick-copy preferences in extension localStorage; and consent version, agreement timestamp and random consent epoch in the separate snapredact-consent IndexedDB database. Settings and consent are not encrypted by SnapRedact, are not synced and are not transmitted. The obsolete boolean preference database is removed.
On an update from 0.1.0, old captures are preserved until you choose deletion. The popup flags old captures and Settings reports “N captures saved by an earlier version are still stored in this browser”. Delete old captures asks for confirmation and then deletes the entire snapredact database. Cancel preserves it. This version never writes new captures there and does not read old image/title/time fields; it only counts records. This version can't open or export these captures. Delete them when you no longer need them. 0.1.0 stored export-format, Auto-blur and quick-copy preferences in extension localStorage, which 0.1.1 also uses. The 0.1.0 package did not use chrome.storage.local or store a dailyUsage record. Old captures are not encrypted by SnapRedact. Removing the extension normally removes its local data, but does not erase downloaded files, clipboard data or browser/system backups.
Page titles, URLs, times and exports
Neither tab.title nor the captured page's document.title is read. The editor always has the generic title “SnapRedact editor”; its address contains a random capture identifier and optional quick-copy flag, never a source title, URL or capture time. SnapRedact does not call browser history APIs. Chrome may independently retain extension-page visits, random identifiers and visit times in history/session records.
The popup and worker read tab.url transiently only to check allowed schemes (HTTP, HTTPS or file) and file-access eligibility. The address is never stored, logged, put into messages or displayed. Runtime sender extension URLs are checked to authorize extension pages; these are not source-page addresses. Errors omit address strings. Page pixels and locally scanned text can themselves contain titles, URLs or times visible on the page.
There is no capture timestamp. The clock is used for capture throttling, consent agreement time, UI timers and export filenames. Download names are generic snapredact-YYYYMMDD-HHMMSS using local export time, with a format extension. PNG and JPG are fresh canvas encodings: no source EXIF, page title, URL or visit-time metadata is copied. The local PDF writer embeds fresh JPEG pixels and writes no Title, CreationDate, ModDate or other document information dictionary. The filename export time and any information visible in image pixels remain in exports. Copy places a PNG on the system clipboard; Download creates the file you request. Other apps or your operating system may retain these exports and file times.
Permissions and questions
activeTab authorizes capture after your toolbar action; scripting injects the bundled local helper after consent. The manifest requests only activeTab and scripting, with no host permissions, storage permission, automatic content scripts, remote code or external fonts. Its extension-page policy sets connect-src 'none'. Normal website activity, including activity triggered by scrolling, and browser installation and updates are handled separately by the website or browser. Opening the privacy-policy link visits this public website in your browser. Chrome's own pages and the Chrome Web Store cannot be captured. Local files require Chrome's “Allow access to file URLs” setting.
We hold no server copy to retrieve or delete. Contact the publisher with questions. Policy changes will be published with an updated effective date.