Chrome extension privacy

Last updated: April 20, 2026

This page describes exactly what the iwant2eat — Save recipe Chrome extension does with data. It complements the general iwant2eat privacy policy, which covers the web service the extension talks to.

What the extension reads

When you click the extension icon and press Save this recipe, the extension reads the following from the tab you are currently on:

• The page URL and title.
• The visible text of the main article (via a one-shot script injected only at the moment you click Save — there is no persistent content script and no continuous monitoring).
• The URLs of likely recipe images (og:image, twitter:image, and large <img> elements inside the article).

The extension does not read any other tab, any browsing history, any form data, any cookies from other sites, or anything from pages you did not explicitly click Save on.

What the extension sends

The collected URL, title, text, and image URLs are sent to https://www.iwant2eat.com over HTTPS, together with your iwant2eat session cookie so the server knows which account to save the recipe to. Nothing is sent to any third party.

What the server does with it

The server creates a recipe in your personal iwant2eat vault. The recipe text is then parsed by our AI pipeline (Claude, via Anthropic) the same way a pasted or emailed recipe is — see the main privacy policy for details on that pipeline. Images referenced by the collected URLs are downloaded by the server and attached to the recipe.

What is stored locally in the browser

The extension uses chrome.storage.local only to remember your choice of API endpoint (production vs. local-dev during testing). No recipe content, no page text, and no personal data is stored by the extension itself.

Permissions and why they are requested

• activeTab + scripting — so the popup can read the currently active tab's content the moment you press Save.
• storage — to remember the endpoint toggle.
• host_permissions for https://www.iwant2eat.com/* — so the browser attaches your iwant2eat session cookie when the popup posts the captured recipe to your account.

Data retention and deletion

Recipes saved via the extension are stored in your iwant2eat account and follow the retention and deletion rules described in the main privacy policy. You can delete any recipe from inside the app, and you can delete your whole account from /data-deletion.

What the extension does not do

• No ads, no tracking pixels, no analytics beacons.
• No telemetry — the extension never "phones home" on its own.
• No background page activity — there is no service worker that runs while you browse; the extension only does anything when you click its icon.
• Your data is never sold or shared with anyone outside the processors listed in the main privacy policy.

Contact

Questions about the extension's data handling: privacy@iwant2eat.com.