Jump to Recipe collects nothing.

Last updated 2026-07-25. This policy covers the Jump to Recipe Chrome extension (jump-to-recipe-extension) and nothing else.

In one table

Data collected: None. No personal information, no browsing history, no page content, no file contents, no usage statistics.
Data transmitted: Nowhere. The extension makes no network requests at all. There is no server behind it; there is nothing to send data to.
Analytics / telemetry: None. No analytics SDK, no crash reporting, no beacons, no remote configuration.
Accounts: None. There is no sign-in, no licence check, and no payment of any kind.
Local storage: Your own preferences only, held in chrome.storage.local inside your browser. Uninstalling the extension removes them.
Third parties: None. Nothing is sold, shared, rented, or used to assess creditworthiness or for lending.
Remote code: None. Every line the extension runs ships inside the package. Nothing is fetched or evaluated at runtime.

You do not have to take this on faith. The complete source is at github.com/minty-modesty/jump-to-recipe-extension under the MIT licence, and you can confirm the absence of network calls yourself with a grep for fetch, XMLHttpRequest, sendBeacon and WebSocket.

Permissions

/ what each one is for

activeTab: Reads the recipe page you are on, and only after you click the toolbar icon. No background access, no other tabs.
scripting: Needed to run extract.js in the page: it looks at the page's own <script type="application/ld+json"> blocks and draws the card. Nothing leaves the page.

The rest

Children

The extension is not directed at children and collects no data from anyone, of any age.

Changes to this policy

Any change is published on this page with a new "last updated" date, and the change itself is visible in this repository's commit history.

Contact

Email jemarbury.lh@icloud.com, or open an issue on GitHub.