Privacy Policy

Overview

DOMShot captures individual webpage elements as PNG images. It includes a Chrome extension, local agent tooling, and a hosted MCP service for public webpages. The extension runs in your browser, the local agent package runs where you install it, and the hosted MCP service runs each request in an isolated automation browser.

Hosted MCP Service

When you use the hosted MCP service, DOMShot receives the public HTTPS URL, element selector or short visual intent, styling choices, and other capture settings supplied in the tool request. It fetches that public page, inspects or renders the requested elements, and returns PNG image content with limited metadata such as selectors, dimensions, confidence, warnings, and fallback status.

The hosted service does not accept passwords, cookies, tokens, Chrome profiles, local files, private-network addresses, or pages that require a signed-in browser session. It does not submit forms or provide general-purpose browser automation.

Generated images and working files are held only in temporary storage and are deleted when the request finishes. DOMShot does not place hosted captures in an application database or use them to train models. Hosting and security infrastructure may process standard network metadata, such as an IP address, request time, response status, and error category, to operate and protect the service.

Data DOMShot Handles

When you start a capture, DOMShot can access the visible website content needed to highlight elements, capture the selected DOM node, and render the preview/export UI. Website content may include text, images, links, and visual styling from the selected page element.

DOMShot also stores your theme preference and may temporarily store the most recent capture in Chrome local extension storage so the preview can be reopened in the same browser.

When the agent package is used, it can access pages through Playwright, Chrome DevTools Protocol, or an explicit browser profile chosen by the user. Any page content, screenshots, paths, browser profiles, cookies, or login state involved in that workflow remain in the local automation environment unless the user or host application stores or shares them separately.

How Data Is Used

DOMShot uses website content only to provide its single purpose: capturing a user-selected page element and exporting it as a PNG image. The generated PNG is saved to your computer only when you click the download button.

The local agent package uses page content to inspect candidates, choose targets, render captures, and write requested output files. The hosted MCP service uses public page content only to complete the requested inspection or element capture and return the result.

The public agent documentation explains the npm, CLI, MCP, browser mode, and troubleshooting workflows at domshot.app/docs/agent.

Data Sharing

DOMShot does not sell user data or use extension, local-agent, or hosted-MCP capture data for advertising, behavioral profiling, creditworthiness, or lending purposes. The hosted MCP service has no user accounts and does not accept user-uploaded screenshot files.

Website Analytics

The public website uses Vercel Web Analytics to measure anonymous, aggregated information such as page views and referrers. Vercel Web Analytics does not use cookies and does not collect personal identifiers that track visitors across websites. Website analytics do not receive page content, screenshots, or other data handled by the DOMShot extension or agent package.

Remote Code

DOMShot does not load or execute remotely hosted code in the Chrome extension. All JavaScript used by the extension is packaged with the extension. The agent package depends on standard npm dependencies installed in the local project environment.

Your Choices

Use the Chrome extension or local agent package when a page must remain on your device or requires an authorized private browser session. Use the hosted MCP service only for public pages you are authorized to access and capture. You can contact the developer to ask a privacy question or report a concern.

Contact

For privacy questions about DOMShot, contact the developer at me@rubenruiz.dev.