A Privacy Policy Short Enough to Read

Last updated September 15, 2026. The summary: the files you build or paste never leave your browser, and this site sets no cookies for the product.

What Happens When You Use the Tools

The Compose generator, the Dockerfile generator and the validator are JavaScript that runs on your machine. The service names, passwords, ports and files you type or paste are held in the page's memory, used to draw the output, and gone when you close the tab. There is no server endpoint they could send anything to, no account, and no history. Copy and download both happen locally.

Cookies and storage on this site

This site sets no cookies for the product and keeps nothing in localStorage or sessionStorage. There is no login and no preference to remember.

Page views are measured with Google Analytics, which sets its own first-party cookies (_ga and _ga_*) and sends the page address, a random client identifier and technical details about your browser to Google. The data is used only to see which pages get read. Google's handling of it is described in the Google privacy policy. Browsers with an ad blocker or scripts disabled are not measured.

Third parties this site touches

Fonts load from Google Fonts, which means your browser requests font files from Google's servers as described in the Google privacy policy. No ad networks or tracking pixels load here. The server does what any web server does: it delivers the page files and may write standard, short-lived access logs handled by the hosting provider.

How to clear local data

The one thing you might want to clear is the browser's own memory of the page: a reload does it. Downloaded files are ordinary files on your disk and stay until you delete them.

There is nothing else to clear. If you emailed a file to the contact address for debugging, say the word and that email gets deleted too.

If this policy ever changes, the date above changes with it, and the substance will stay consistent with the terms of use.