Privacy Policy for SavedPixel HTML CSS JS Extractor

SavedPixel HTML CSS JS Extractor ("SavedPixel" or "the extension") is a local-first Chrome extension that lets users inspect webpages they choose and create local HTML, image, Markdown, MHTML-derived, and ZIP exports. This policy explains what data the extension accesses, how it is used, what remains local, and what we do not collect.

What the extension does

The extension runs on webpages chosen by the user and provides tools to:

• Inspect page structure and categorize sections
• Select included and excluded elements via a visual picker
• Preview extracted HTML with inlined or separate CSS
• Inline fonts and images as data URLs when requested
• Download standalone single-file HTML exports
• Download bundled ZIP exports containing HTML, CSS, fonts, images, and scripts
• Export selected elements as PNG or JPEG images, including a ZIP containing multiple selected images
• Create Markdown Content, Markdown SEO Basic, Markdown SEO, and responsive Markdown Layout files
• Attach notes to page elements and download or locally save annotation Markdown
• Import user-selected bookmark HTML or grouped CSV URL lists and run explicit sequential batch exports
• Create Native MHTML and clean static ZIP captures
• Extract the element currently selected in Chrome DevTools

Data we access

To perform its core functionality, the extension may access:

• The HTML structure of the current webpage
• Computed CSS styles of selected elements
• Page-linked stylesheets, fonts, images, and scripts needed for export generation
• The current tab context required to run extraction on the page the user selected
• Visible text, headings, links, form labels, metadata, structured data, element positions, dimensions, and responsive layout evidence used by the selected output
• Enabled page URLs and labels that the user explicitly imports or enters for grouped batch exports

When generating bundled exports, the extension fetches remote assets (stylesheets, fonts, images, scripts) directly from their original hosting servers to include them in the local export. These fetches are made from the browser and the content is not sent to any server we operate.

Data we store

The extension stores limited local data in the browser using chrome.storage.local, such as:

• Sidebar, picker, overlay, filename, Markdown, responsive viewport/output, and annotation preferences
• Per-tab or recoverable extension UI state
• Imported or manually entered batch groups, target URLs, labels, import metadata, and the latest recoverable batch-run state

This data is stored locally in the user's browser and is not synchronized to SavedPixel. If the user chooses an annotation folder and the File System Access API is available, the directory handle is stored in extension-owned IndexedDB so the browser can request permission to reuse it. The user can forget that folder association.

Web history disclosure

SavedPixel does not passively read Chrome browsing history and does not create advertising or analytics profiles. Grouped batch functionality does let users import, enter, and locally store lists of page URLs, then navigates only the enabled URLs after the user explicitly starts the batch. For Chrome Web Store disclosure purposes, SavedPixel therefore conservatively declares Web history use for this user-authorized core function.

Annotations and speech recognition

Annotation notes remain in the extension UI until the user downloads or saves them. Optional folder writes occur only after an explicit user action. Where Chrome provides SpeechRecognition or webkitSpeechRecognition, the extension can place recognized speech into the focused note. SavedPixel does not receive audio or transcripts; browser or vendor handling is governed by the browser's policies.

Data we do not collect

• We do not collect, sell, or use personal data for advertising, analytics, profiling, or unrelated tracking.
• We do not collect authentication information, payment data, health data, personal communications, or precise location for a SavedPixel service.
• We do not use any third-party analytics, telemetry, or tracking services.
• We do not transmit extracted page content to our own servers or any third-party service.

Remote code

The extension does not load or execute remote JavaScript or WebAssembly as extension code. All extension JavaScript is bundled locally. Remote CSS, fonts, images, and optional source-page script files may be fetched from their original hosts solely to link, inline, or write them into a user-requested local export. Copied source-page scripts are static export assets and are not executed as remote extension logic.

Permissions used

Downloads

When the user explicitly requests an export, the extension creates files in the user's Downloads folder using the browser downloads API. Exports may include:

• A single .html file with inlined styles, fonts, and images
• A .zip bundle containing separate HTML, CSS, font, image, and script files
• PNG or JPEG selected-element images
• Markdown Content, Markdown SEO Basic, Markdown SEO, responsive Markdown Layout, or annotation files
• Native MHTML or an MHTML-derived local package

Export generation happens entirely within the browser. No exported content is uploaded or transmitted to any external service.

Data sharing

We do not sell user data. We do not share user data with third parties. The only external network requests the extension makes are direct fetches to the original hosting servers of page-linked assets (CSS, fonts, images, scripts) when the user requests a bundled export.

User control

Users control which pages or grouped URLs to process, which elements to select, which assets to package, and when to download. Downloads begin only after a direct action or one explicit batch Start. A local watchdog may reconcile an already user-started batch after normal service-worker suspension, but it does not schedule unattended runs.

Users can clear selections, edit or delete local groups, cancel a batch, forget annotation folders, clear extension storage through Chrome, or uninstall the extension. Uninstalling removes Chrome-managed extension storage; files already downloaded to the user's filesystem remain under the user's control.

Changes to this policy

If we update this privacy policy, we will revise the "Last updated" date at the top. Continued use of the extension after changes constitutes acceptance of the updated policy.

Contact

Support email: savedpixel@byronjacobs.com