Dom Ship — Privacy Policy

Browser extension for Firefox and Chromium-based browsers that sends the rendered HTML of the current page to an HTTP endpoint configured by the user.

Summary

• The developer collects no data. Dom Ship has no servers, no analytics, no telemetry, no trackers.
• Page content is sent only when you explicitly click “Send page”, and only to endpoints you configured yourself.
• All settings stay locally in your browser and are never synced or transmitted anywhere else.

What the extension does

Dom Ship lets you define one or more profiles, each pointing to an HTTP endpoint of your choice. When you click the toolbar icon and press Send page, the extension performs a single POST request to the selected profile's endpoint containing the current page's URL, its title, and the rendered HTML of its DOM, plus any parameters and headers you configured in the profile.

Data collection by the developer

None. The extension never communicates with the developer or with any third party. There is no analytics, crash reporting, telemetry, or advertising of any kind.

When data leaves your browser

Data leaves your browser only when you press Send page. There are no automatic or background transmissions: the “automatic activation” feature only preselects a profile in the popup for matching domains — it never sends anything by itself.

The recipient of the data is exclusively the endpoint URL that you entered in the profile. You are responsible for choosing endpoints you trust, since the transmitted page may contain personal or sensitive content visible on that page.

What is transmitted

When you send a page, the POST request contains:

• url — the address of the page being sent;
• title — the page's title;
• html — the full rendered HTML of the page's DOM;
• any extra parameters and headers you configured in the profile (e.g. authentication tokens).

Local storage

Profiles — including endpoints, parameters, and any authentication tokens you enter in headers or parameters — are stored using the browser's storage.local API. They remain on your device, are never synced across browsers, and are never read or transmitted by anyone other than the extension itself. Uninstalling the extension removes them.

Permissions

• activeTab / scripting / tabs — used to read the rendered HTML of the current tab, only after you click the extension's icon.
• storage — used to save your profiles locally.
• Host permissions — needed solely to deliver the POST request to the arbitrary endpoint you configured. They are not used to read or monitor your browsing.

Third parties

No data is shared with or sold to third parties by the extension. Any endpoint you configure is a service of your own choosing and is governed by that service's own privacy practices.

Changes to this policy

If the extension's behavior regarding data ever changes, this page will be updated and the change noted in the extension's release notes.

Contact

For any question about this policy, visit kabirferro.com and use the Report button.

Last updated: July 24, 2026