This extension exists to turn a recipe web page into a re7 recipe. Here's exactly what
it does with your data.


The extension only reads the page you're on when you click its toolbar icon. There is
no background content script and no scanning of other tabs or your browsing history -
browser.scripting.executeScript only ever runs once, on demand, against the active
tab, triggered by that click.

• The readable text of that page - what @mozilla/readability extracts, meaning the
  article body rather than the full HTML, truncated at 20,000 characters - is sent to
  the LLM provider you configured in the options page: OpenAI, or any
  OpenAI-compatible endpoint you chose to point the extension at. The page's title and
  URL go with it as context for the model. None of this is ever sent to re7's servers.
  Using this feature calls out to your LLM provider and may cost you tokens/API usage
  under your own account with them.
• re7's servers receive the recipe the model produced - title, ingredients,
  instructions, and servings - plus the page's URL, stored as the recipe's source. This
  happens automatically as the final step of an import you started by clicking "Import
  this page": there is no separate confirmation step, so review the result in re7
  afterwards, where you can edit or delete it. re7 never sees the raw page content,
  never sees the LLM's request or response, and is not involved in the extraction step
  at all.
• Signing in to re7 goes through the standard OAuth Authorization Code + PKCE flow
  directly between your browser and your re7 instance; re7 only issues the extension
  an access/refresh token scoped to creating recipes, and nothing else.

In the terms Firefox uses for data collection, the extension declares two required
types in its manifest: website content (the page text the recipe is built from) and
browsing activity (the URL of that one page). Both are required rather than
optional, because an import cannot happen without transmitting them.


Your re7 access/refresh tokens and your LLM API key are stored locally in
browser.storage.local on your device only. They are never written to
browser.storage.sync (which browsers can sync to your account across devices), and
they never pass through re7's servers or any third party. They leave your device only
as credentials on requests to their own respective endpoints: the tokens to your
configured re7 origin, the API key to your configured LLM endpoint.


None. This extension makes no calls to any analytics, crash-reporting, or telemetry
service. The only network calls it makes are the ones described above: to your
configured re7 origin (sign-in, token refresh, saving a recipe) and to your configured
LLM endpoint (testing the connection, extracting a recipe).


See the "Permissions" section of README.md for what each requested
permission is used for and why.


This extension is part of the re7 project. Open an
issue on the repository for any privacy questions.