Summary
Recipe Extractor is built to respect your privacy. Everything happens in your browser. The extension reads a recipe page only at the moment you click it, pulls the recipe out on your device, and keeps your recipe box on your device. It cannot see your browsing and has no standing access to any site you visit. Its only site access is the payment provider's own page (extensionpay.com), where ExtensionPay's bundled script handles the anonymous plan check and the optional Pro upgrade through Stripe. If you never buy Pro, no payment information is ever collected.
How it works
Open a recipe page and click the extension. It reads that page's recipe markup (the standard schema.org data that recipe sites publish) and turns it into a card of ingredients and steps. This happens through Chrome's activeTab grant: access exists only for that one tab, only after your click, and does not persist. The extension has no content scripts on the sites you browse and cannot read any page in the background. (The one content script it carries runs only on extensionpay.com, the payment provider's own page, as ExtensionPay requires.)
What data the Extension stores
Everything the extension itself stores lives in your browser through chrome.storage.local:
- Your saved recipes, meaning the contents of the recipe card: title, ingredients, steps, servings/yield, times, the recipe's image address, the author name the site published, and the page address it came from. Each entry stays until you remove it.
- Your plan record: whether you are on Free or Pro, so the extension knows which features to turn on.
The bundled ExtensionPay library additionally keeps its own small plan record (an anonymous identifier and an install date). Unlike the extension's own data above (which stays strictly on your device), ExtensionPay keeps its record in Chrome's synced extension storage, so if you are signed in to Chrome, that record may sync across your browsers through your Google account.
What it does NOT do
- It does not transmit your recipes, the pages you read, or any personal information to us or to anyone else.
- It does not read your browsing history, your other tabs, or your keystrokes.
- It runs no tracking, no analytics, and no advertising.
- Extraction runs on your machine: there is no recipe server and no AI service involved.
Payments (optional Pro)
Pro is optional and currently a one-time purchase. It is handled by ExtensionPay (extensionpay.com), which uses Stripe for secure payment processing. If you buy Pro, ExtensionPay and Stripe handle your email address and payment details to complete and remember that purchase, under their own privacy policies. We never see or store your card information. If you do not buy Pro, no payment data is collected.
- ExtensionPay: https://extensionpay.com/privacy
- Stripe: https://stripe.com/privacy
Permissions, explained
- storage: to keep your recipe box and plan record on your device.
- activeTab: to read the recipe markup of the page you clicked on, at that moment only.
- scripting: to run the reader once in that page when you click. It gathers the page's recipe markup and nothing else.
- Host access to
https://extensionpay.com/*: used by ExtensionPay to run the anonymous plan check and to handle the optional Pro purchase. The extension has no host access to any recipe site or to any other site you visit.
Data retention
Your recipes and plan record stay in your browser until you remove them. You can clear everything at any time by deleting your saved recipes, clearing the extension's storage, or removing the extension. Removing the extension deletes its local data.
Children
Recipe Extractor is a general audience cooking tool and is not directed to children. It does not knowingly collect any personal information from anyone, including children.
Changes
If this policy ever changes, the updated version will be posted here with a new "Last updated" date.
Contact
Questions are welcome at: extensions@edenapps.app