Hush
Effective date: 1 January 2026 · Last updated: 1 January 2026
The short version: Hush does not collect, transmit, or share any personal data, browsing activity, or page content. Everything happens locally inside your browser. There is no Hush server.
1. Who we are
Hush is a Chrome browser extension developed and operated by Four Line ("we", "us", "our"). Our website is fourline.ai. This Privacy Policy describes how the Hush extension handles information.
2. What this policy covers
This policy applies only to the Hush browser extension distributed via the Chrome Web Store and the assets bundled inside its package. It does not cover the public website at fourline.ai, which has its own privacy notice, nor any third-party site you may interact with separately.
3. What we do not collect
We have intentionally designed Hush so that the following information never leaves your computer and is never seen by us:
The content of any web page you visit, including text, images, forms, account details, or any other DOM data Hush operates on.
Any redacted, blurred, pixelated, annotated, or otherwise modified version of a page element.
Any screenshot, PNG, SVG, or other export Hush generates on your behalf.
Any annotation, watermark, template name, or template selector you create.
Browsing history, URL list, tab list, or referrers.
Account credentials, cookies, session tokens, or autofill data.
IP address, device identifiers, advertising identifiers, telemetry, or usage analytics.
Crash reports or error reports.
The extension contains no analytics SDKs, no tracking pixels, no fingerprinting code, and no remote code execution paths. The JavaScript that runs in your browser is exactly the JavaScript shipped in the .crx package — auditable in the Chrome Web Store source listing.
4. What is stored locally on your device
Hush uses the standard Chrome chrome.storage.local API to remember a small amount of state between sessions. This data is written to your local browser profile and is never transmitted off-device. We cannot read it. The stored items are:
Floating-launcher position — the pixel coordinates you dragged the launcher to, so it stays where you put it.
Last applied redaction style, scoped per origin (per website). Used only to offer a one-click "Apply previous" banner the next time you select an element on the same site.
Saved templates, scoped per origin. When you click Save in the Templates section, Hush stores the CSS selectors of your selected elements together with their inline style strings so you can re-apply the same redactions later.
You can clear all of this at any time by removing the extension or by clearing site data in Chrome. There is no cloud copy.
5. Permissions and why we ask for them
Hush requests the minimum set of Chrome permissions needed to perform its function. Each is used solely on your local device:
activeTab — lets the extension read and modify the DOM of the currently active tab when you click the icon, the floating launcher, or use the right-click menu. Without it, redaction is impossible.
scripting — lets the extension inject its content script and the bundled html-to-image rendering library on demand. We never inject remote code.
downloads — lets the Download buttons save your generated PNG / SVG files to your local Downloads folder.
storage — used only for the local-state items listed in section 4.
contextMenus — adds the "Redact this with Hush" right-click entry on web pages.
<all_urls> content scripts — required so the floating launcher and keyboard shortcuts can appear on any site you choose to redact. The extension does not exfiltrate, log, or transmit anything from those sites.
6. Network requests
The Hush extension itself does not make any outbound network requests. It does not contact our servers, third-party servers, or any remote endpoint while running. The only network activity that may occur is initiated by you, when you click the brand badge in the toolbar, which opens fourline.ai in a new tab as a normal browser navigation. Visiting fourline.ai is governed by the privacy notice on that website.
7. Third-party services
Hush bundles one open-source library inside the extension package: html-to-image (MIT-licensed). It is shipped as a static file inside the extension and runs entirely in your browser. It does not make network requests. We do not use any third-party SDK, analytics provider, advertising network, A/B testing tool, or remote configuration service.
8. Children
Hush is a general-purpose tool not directed at children under the age of 13. We do not knowingly collect personal information from children — and given that we do not collect personal information at all, this is also literally true.
9. Changes to this policy
If we materially change how the extension handles data, we will publish an updated version of this page with a new "Last updated" date and bump the extension's version number. If a future version of Hush ever introduces a feature that requires sending data off-device, that feature will be opt-in, clearly labelled in the user interface, and described in this policy before the version is published.
10. Your rights
Because Hush does not transmit or retain any data about you, there is no remote dataset to access, correct, port, or delete. You can fully exercise control by:
Uninstalling the extension to remove its local storage.
Clearing the extension's storage from chrome://extensions → Details → Site access / Storage.
Deleting individual templates from the Templates panel inside the extension.
If you are in the European Union, the United Kingdom, California, or another jurisdiction with statutory data-subject rights, those rights apply only to data we hold about you — and we hold none. We will respond to verifiable requests under any applicable law.
11. How to reach us
Questions, feedback, or security reports: write to hello@fourline.ai. For Chrome Web Store policy concerns, you can also use the "Report abuse" link on the extension's listing.