Last Updated: March 14, 2026

DOM Stripper ("the Extension") is provided as a utility tool to help developers, SEO specialists, and AI operators clean and extract HTML from webpages.

Your privacy is critically important to us. This Privacy Policy outlines how we handle the information when you use our Extension.

1. Information Collection and Use

We do not collect, store, or transmit any personal information or browsing data.

The Extension operates entirely locally within your browser:

• No Data Transmission:: The Extension does not send any data, HTML content, or browsing history to external servers, APIs, or third parties.
• No Analytics or Tracking:: We do not use analytics software, tracking pixels, or any other method to monitor your usage of the Extension.
• Local Processing:: When you click "Clean & Copy DOM", the Extension clones the Document Object Model (DOM) of the webpage you are currently viewing, strips it of layout code and scripts, and copies the resulting text directly to your local computer's clipboard. This process happens entirely on your machine.

2. Permissions Required

The Extension requires the following permissions to function:

• activeTab: Allows the Extension to access the content of the tab you are currently viewing only when you explicitly click the Extension icon to activate it. It does not monitor tabs in the background.
• scripting: Required to execute the local HTML-cleaning script on the active tab so the cleaned DOM can be copied to your clipboard.

3. Data Retention

Because no data is collected or transmitted, there is no data retention policy. The Extension only holds the cloned HTML data temporarily in your computer's active memory (RAM) long enough to clean it and copy it to your clipboard.

4. Changes to This Privacy Policy

If we add features in the future that require data collection (which we currently have no plans to do), we will update this Privacy Policy and clearly outline those changes.

5. Contact Us

If you have any questions or concerns regarding this Privacy Policy, please open an issue on the project's GitHub repository or contact the developer directly.