Image Host Transfer Lint - EU docs IP leak

It reads your Markdown, MDX and HTML docs line by line and flags every asset URL a reader's browser would fetch from a third party: webfonts, avatars, image hosts, script CDNs, embeds, live badges and analytics. Each finding names the host, the country the request lands in, and the concrete fix that keeps the asset on your own origin.

Developers and technical writers in Germany, Austria and the Netherlands who publish a docs site out of a Markdown or HTML repository. If your handbook, changelog or product docs are public and your readers are in the EU, every hotlinked asset on those pages is a transfer you are answerable for.

Online privacy scanners load a rendered URL. They cannot see the Markdown in your repository, the pages you have not deployed yet, or the branch under review. This runs where the text lives, so a leaking image is caught in the pull request instead of after publication, and code blocks holding examples are not counted as leaks.

The free scan is complete on its own: open a file or folder and every leaking asset is named with host, country and fix. The paid layer is a different job - owning the evidence. It exports a workspace-wide Art. 30 transfer register as CSV and Markdown plus a self-host rewrite map, and covers a team seat.

A court has already priced the failure: LG Munchen I, case 20 O 14144/19, awarded one visitor EUR 100 in damages on 20 January 2022 for a single Google Fonts call on a single page. A manual review of a docs repository is billed as privacy counsel time, page by page, and has to be repeated after every merge.