Privacy

Privacy Policy

The short version: there's no account, nothing about your recipes is sent to us, and you can turn off the only thing we measure. Here's the long version.

Last updated 24 May 2026

In one breath: Pantry has no accounts and no backend for your data. Your saved recipes and notes live in your own browser and sync through Chrome Sync — Google's infrastructure, not ours. We never receive them.

What Pantry stores

Everything Pantry saves is kept in chrome.storage.sync, which is synchronized across the Chrome browsers you're signed into. None of it is transmitted to Pantry or any third party.

WhatWhyWhere it lives
Your "Recipes" bookmark folder IDSo saved recipes always land in the same folderYour browser (Chrome Sync)
Feature toggles (e.g. ingredient hints)To remember your settingsYour browser (Chrome Sync)
Your per-recipe notesThe notes you write in the side panelYour browser (Chrome Sync), compressed
Bookmarks themselvesThe recipes you saveYour normal Chrome bookmarks

Because your recipes are saved as ordinary Chrome bookmarks, they sync to mobile Chrome, are searchable from the address bar, and remain in your browser even if you uninstall Pantry.

What we measure

To understand whether Pantry is useful, we collect a small amount of anonymous usage data — for example, how often the popup is opened and how many recipes get bookmarked. This data is not linked to your identity and never includes the contents of pages you visit, the recipes you save, or the notes you write.

You can turn this off. Open Pantry's options page and toggle off analytics. When opted out, no usage events are sent at all.

What we never do

  • No account, login, or email is ever required.
  • We never send your bookmarks, notes, or browsing history to our servers — we don't have a server that receives them.
  • No tracking pixels and no advertising networks.
  • We never sell or share your data.
  • We don't strip ads, block trackers, or alter the recipe blogs you visit — those pages load exactly as their creators built them.

Permissions, and why Pantry asks for them

Chrome requires extensions to declare the capabilities they use. Here's each one Pantry requests and the single reason it needs it.

PermissionWhy Pantry needs it
bookmarksCreate and maintain a sorted "Recipes" folder of the recipes you save.
storageRemember your Recipes folder, feature toggles, and per-recipe notes (synced via Chrome Sync).
sidePanelOpen the side-panel UI for the recipe notes editor.
tabsRead the active tab's URL and title to attach notes to the right page and refresh on navigation.
Host access (http/https)Detect recipe content and run auto-scroll, ingredient tooltips, and bookmarking on the recipe blogs you visit. Pantry only adds scroll position, tooltips, and its own toolbar UI — it does not modify the page's content.

Third parties

Two third parties are involved, and only in limited ways:

  • Google Chrome Sync stores and syncs your settings and notes across your devices, under Google's own privacy terms. Pantry never sees this data flow.
  • Anonymous analytics (used only when you haven't opted out) processes the non-identifying usage events described above.

Children

Pantry is a general-audience tool and is not directed at children under 13. It collects no personal information from anyone.

Changes

If this policy changes, we'll update the date at the top of this page. Material changes will also be noted in the extension's release notes.

Contact

Questions about privacy? Email hello@pantry.cool — replies usually come within a day.