This Privacy Policy explains how RecipeCompiler (“we”, “us”) handles information when you use our browser extension and web application (the “Service”). By installing the extension or using the Service, you agree to the practices described here.

1. Information We Collect
   Account information: When you create an account, we collect your email address to authenticate you. Your password is never stored in plaintext — authentication is handled by our platform provider.

Recipe page content: When you actively click “compile” on a recipe page, the extension reads the visible text of that page and the page’s URL, and sends them to our servers to be compiled into a specification. We do not read, collect, or transmit page content unless you initiate this action.

Generated specs & saved recipes: Specs you compile and choose to save are stored under your account, along with the source URL you compiled from.

Authentication tokens: After you sign in, an access token is stored locally in your browser’s extension storage to authenticate future requests. This token never leaves your browser except to authenticate against our own servers.

Anonymous usage identifiers: If you use the Service without an account, a random, non-identifying identifier is generated and stored locally in your browser to enforce the free compile limit. This identifier is not linked to your name or email and is used solely to count free compiles.

1. How We Use Information
   We use the information above solely to provide the Service:

· to compile recipe pages into engineer-grade specifications

· to save and display your compiled recipes across sessions

· to generate downloadable PDFs of your specs

· to authenticate you and keep your saved data private to your account

We do not use your data to build advertising profiles, and we do not sell your data to third parties.

1. How Information Is Shared
   To compile specifications, the recipe text you submit is processed by a large language model provider under our control. Only the text needed to compile a spec is sent, and it is used solely to generate your spec.

Other than this processing, your data is stored within our application’s database and is not shared with any third party except as required by law.

1. Data Governance & Privacy
   This Service is hosted publicly. Even where we do not retain data, we disclose that below so you can assess your own compliance posture. User-generated recipes often contain personal notes (for example, “my grandmother’s recipe” or “my child’s allergy-safe version”) — that counts as personal data, and we treat it accordingly.

Whether we store recipes: We do not store the original recipe text you submit for compilation. Raw recipe text is processed in memory to generate a spec and is then discarded; only a compiled spec you explicitly choose to save is persisted.

Whether we store generated specs: Yes — but only when you actively click “save”. Compiled specs you save are stored under your account in our hosted database. Specs you do not save are not retained.

Whether we log user inputs: We do not log the recipe text or page content you submit. Operational logs may record request metadata (time, status) for reliability, but they never include the recipe text or source page body.

Whether we use inputs to improve the model: No. We do not use your submitted recipe text or compiled specs to train, fine-tune, or otherwise improve the language model. Inputs are used solely to produce your spec.

Whether we share data with third parties: The recipe text you submit is sent to our language-model provider solely to generate your spec. Saved specs and account data are not shared with any other third party, except where required by law.

Whether we track anonymous usage: Yes — a random, non-identifying identifier stored in your browser limits free compiles to 10 per month before an account is required. It is not personal data and is not linked to your identity. Clearing your browser storage resets it.

Security practices:

· HTTPS enforced: All traffic between your browser, our servers, and our hosting platform is encrypted over HTTPS.

· No recipe text stored in logs: Recipe text and page content are never written to application logs, error logs, or analytics.

· No PII stored without consent: We store only the email address you provide at sign-up for authentication. We do not collect additional personal data, and any personal notes embedded in recipe text are processed only to compile your spec and are not extracted, profiled, or retained separately.

1. Data Storage & Security
   Saved recipes and account data are stored in our platform’s hosted database. Access tokens are stored locally in your browser and are never written to our servers. We use reasonable technical and organizational measures to protect your data, but no method of transmission or storage is completely secure.
2. Extension Permissions
   The extension requests the following permissions, each limited to what the Service requires:

· activeTab & scripting — to read the text of the recipe page you are viewing only when you click “compile”, and to display the compiled spec grid on that page.

· storage — to store your access token locally so you stay signed in.

· tabs — to open the sign-in page and the PDF download view in new tabs.

· host permissions — because recipes can live on any website, the extension may read page content on any site, but only when you explicitly trigger a compile on that site.

The extension does not run silently in the background, does not monitor browsing activity, and does not transmit page content unless you initiate a compile.

1. Your Controls
   You can disconnect your account at any time from the extension popup, which removes the stored token from your browser. You can delete individual saved recipes from the Saved Recipes page, which permanently removes them from our database.
2. Children’s Privacy
   The Service is not directed to children under 13, and we do not knowingly collect information from children. If you believe a child has provided us with information, please contact us so it can be removed.
3. Changes to This Policy
   We may update this Privacy Policy from time to time. When we do, we will revise the “last updated” date above. Material changes will be reflected on this page.
4. Content You Submit & Copyright
   RecipeCompiler transforms recipe text you submit into structured engineering specifications. You are solely responsible for the content you compile. You may only compile recipes you own or have explicit permission to use.

While lists of ingredients are not protected by copyright, recipe instructions, formatting, descriptions and photographs are. Compiling a copyrighted recipe into a spec creates a derivative work. By using the Service, you confirm that you have the rights to any content you compile, and you agree that you will not paste or submit entire copyrighted recipes from third-party publishers (for example, paywalled or premium recipe sites).

To support this, the Service requires you to confirm you have rights before each compile, blocks known premium publishers that enforce copyright on recipe instructions, and rejects full-page scrapes or oversized copyrighted text blocks. We do not store the original raw recipe text you submit — only the compiled spec you choose to save.

1. Contact
   If you have questions about this Privacy Policy or your data, please contact us at support@recipe-compiler.com.