Browser extension

A faster handoff from the page you are reviewing.

The Jacobi extension is a development prototype, not a published browser product. This page explains its intended workflow and the safeguards required before anyone should install it.

Prototype statusNo public install or store listing
[ 01 ]The extensionroadmap, not a download
Current status

There is no Jacobi extension for customers to install today.

The repository includes a Chrome extension prototype with a popup, a context-menu action, local recent-item storage, and a lightweight on-page price cue. It is unfinished, uses development configuration, and is not published through the Chrome Web Store.

That distinction matters. This is a roadmap page, not a download page. The web app remains the supported way to submit an audit URL today.

Open the supported audit workflow
Intended workflow

Keep the decision in the web app, remove the copy-and-paste.

01

Identify a page

From a product or offer page, the extension would let a user choose the URL they are already reviewing.

02

Hand off the URL

The URL would open in Jacobi's audit workflow. The extension would not make an evidence claim on the page itself.

03

Run an explicit audit

The user would still review the target and deliberately start the audit in Jacobi. No background live scan begins from passive browsing.

04

Review the evidence

Results, coverage, exports, and any share controls remain in the authenticated Jacobi workspace.

Release bar

What must be true before this can be a product.

RequirementWhat it means 
Production handoffThe prototype must point to the supported production app rather than a local development address.
Least privilegeEvery browser permission and host pattern must be reduced to the minimum needed for a specific user-facing feature.
Clear disclosureThe store listing, permissions explanation, privacy notice, and in-product controls must describe the same behavior.
Independent reviewThe extension needs functional, privacy, security, and Chrome Web Store policy review before release.
Data and permissions

Nothing should be implicit.

A released extension would explain each requested browser permission in plain language: what it enables, when it runs, what data it can reach, whether data leaves the browser, and how the user can remove access. That disclosure does not exist for a released Jacobi extension because there is no released Jacobi extension.

For now: use the web application for audits and see the Privacy Policy for the current service data-handling overview.