Chive - Recipe Nutrition

Automatically see a Chive nutrition card on recipe pages.

Bring Chive beside recipe pages. After you enable automatic cards, Chive checks each HTTP or HTTPS page locally for standard Recipe structured data. If the page identifies itself as a recipe, Chive sends that page's address and a bounded copy of the visible recipe details to the Chive service. This works without an account. Chive reuses a finished card when the same normalized canonical page has already been processed, and simultaneously tries the exact URL through its normal public crawler. A compact status tab appears while the card is prepared. Open it for nutrition, ingredients, serving controls, save, and grocery-list actions. The automatic detector does not read Chrome browsing-history records or send a list of pages you visit. Its bounded copy contains selected Recipe structured data, page metadata, candidate image URLs, and visible text from likely recipe sections. Forms, inputs, buttons, hidden content, navigation, footers, scripts, styles, and the rest of the DOM are excluded. You can keep automatic cards off during the first- run disclosure, or change the setting later from the extension's Options page. A recipe built from a browser snapshot is a source-page card: it can be reused by the extension when someone visits that same recipe page, but it is not shown in public search. It can become searchable only after Chive independently verifies the recipe through a successful public crawl. A source-page card does not enter a user's library unless they explicitly save it or add it to groceries. The card shows nutrition per serving, ingredients, publisher attribution, and whether nutrition was published or estimated. Connecting a Chive account is optional. Connected users can save or unsave a recipe and add its ingredients to their Chive grocery list. Sign-in starts from the recipe popover, which waits and refreshes automatically after the secure Chive tab finishes connecting, then resumes the save or grocery action that started sign-in. Google and email authentication happen on Chive; the extension never receives a Google password, email password, or one-time sign-in code.