Coriander Privacy Policy

Effective date: June 1, 2026
Publisher: Summer Storms
Contact: hello@summerstorms.org

Summary

Coriander has two parts: the Coriander browser extension for Chrome, and the Coriander app for the Panic Playdate. Together they let you save recipes from the web, organize them, and carry them into the kitchen on your Playdate. This policy covers both.

The short version: your recipes and settings stay on your own computer and your own Playdate. Coriander has no user accounts, shows no ads, and includes no analytics or tracking. We do not collect, sell, or share your personal information. Coriander reaches the internet only to talk to our own website (summerstorms.org) in two cases you can see: the browser extension checks whether a newer version of itself is available, and the Playdate app downloads community recipes when you ask it to. Both connect to our site over a normal encrypted web request, which reveals your device’s IP address as any web request does, but neither sends your recipes, your settings, or your browsing activity. Aside from those, Coriander does not send your information anywhere.

Who we are

Coriander is made by Summer Storms. If you have any questions about this policy or your privacy, contact us at hello@summerstorms.org.

Information we do not collect

We want to be clear about what does not happen, in either the extension or the Playdate app:

No accounts. You do not sign in, and we never ask for your name, email, or any other identity.
No data collection. Coriander does not send your recipes, your browsing activity, or your settings to us or to any third party. (Coriander does contact our website in two cases, the extension’s update check and the Playdate app’s community-recipe download, both described below, but those requests carry none of your data; they only ask our site for information.)
No analytics or tracking. We do not use cookies, trackers, advertising, fingerprinting, or usage measurement of any kind.
No selling or sharing. We have nothing to sell or share, because we never receive your data in the first place.

Information stored on your devices

Coriander saves data locally so it can do its job. This data stays on your own devices and is never transmitted to us.

In your browser, the extension stores:

Your recipe library: the recipes you save, write, or edit, including names, ingredients, steps, prep and cook times, categories, descriptions, and which recipes you have favorited.
Recipe source pages: the web address of a page you scraped a recipe from, saved alongside that recipe for your own reference.
Sync bookkeeping: small technical values that keep your browser and Playdate in step, such as per-recipe identifiers, last-modified timestamps, and your last-sync status.
Your preferences: your chosen theme and your display settings.

On your Playdate, the app stores:

Your recipe library and favorites, saved on the device.
Your in-app settings, such as measurement units and serving sizes.

You can view and delete this information at any time, as described in “Your control and choices” below.

How the extension reads web pages

This applies to the browser extension only. The Playdate app does not read or browse web pages at all (it only downloads community recipes you reques, see “Fetching community recipes on the Playdate” below).

When you ask. When you open the Coriander popup on a recipe page, the extension reads that one page to look for structured recipe data and offers to save it to your local library. This happens only on the tab you are actively viewing, and only when you choose to do it.
Optional automatic highlighting (off by default). If you turn this on in
Settings, you grant the extension permission to check the pages you browse so it can light up its toolbar icon when a recipe is present. This check runs entirely on your computer. No page content, web address, or browsing history is recorded, kept as history, or transmitted. You can turn it off at any time, which removes
that access.

In every case, page reading happens locally and is used only to detect and import recipes. The extension does not log your browsing history.

How Coriander syncs

When you connect your Playdate to your computer with a USB cable and sync, recipe data is exchanged directly between the browser extension and the Playdate app over that cable. This communication is local to the USB link. No sync data passes through any server, and nothing is sent to us.

Checking for updates

This applies to the browser extension only.

So that direct-download copies can tell when they have fallen behind, the extension periodically asks the Summer Storms website (summerstorms.org) whether a newer version has been published. It does this when you install or update it, when your browser starts, about every twelve hours, and when you open the extension.

What this reveals. Like any request to a website, this contact lets our web server see your device’s IP address and standard request information, which may appear in routine server logs. We do not use it to identify you, build a profile, or track you, and we do not combine it with anything else.
What it does not send. The check does not transmit your recipes, your settings, or your browsing activity. It does not even send your current version number; the extension downloads a small public version file and compares it on your own computer.
If you installed from the Chrome Web Store, your browser already keeps the extension up to date, so this check mainly matters for sideloaded or direct-download copies.

Fetching community recipes on the Playdate

This applies to the Playdate app only.

The Playdate app can download a shared set of “community” recipes that we publish on the Summer Storms website (summerstorms.org). This happens only when you ask for it, for example, by choosing “Fetch Community Recipes” in the app’s settings. The app never fetches on its own in the background, and it makes no network connection at all unless you start a fetch.

You are in control. The first time the app needs network access, the Playdate system asks your permission and names the site it wants to reach. You can allow or deny it, and the app uses your Wi-Fi only while a fetch you started is running.
What this reveals. Like any request to a website, downloading the recipes lets our web server see your Playdate’s IP address and standard request information, which may appear in routine server logs. We do not use it to identify you, build a profile, or track you, and we do not combine it with anything else.
What it does not send. The fetch only downloads recipes from us; it does not send your own recipes, your settings, or anything else from your Playdate. Community recipes you download become ordinary recipes on your device, which you can edit or delete like any other.

Permissions and access

The browser extension asks Chrome for:

storage, to keep your recipe library and sync state in your browser.
active tab and scripting, to read the page you are currently viewing, only when you click the extension, so it can detect and import a recipe.
optional access to all sites, requested only if you turn on automatic
recipe-page highlighting, and used solely to detect recipes locally. It is not requested or used otherwise, and you can revoke it at any time.
USB device access, used only when you connect a Playdate, to sync recipes over the cable. Your browser asks you to choose the device.

The extension does not request access to your browsing history, bookmarks, saved passwords, downloads, location, camera, microphone, or any other sensitive data.

The Playdate app stores your recipes on the device. It uses the USB connection only when you choose to sync, and it uses your Playdate’s Wi-Fi only when you choose to fetch community recipes, with the system asking your permission first, as described in “Fetching community recipes on the Playdate” above.

Links to other sites

Coriander may show a link to its page on the Playdate Catalog. If you choose to follow it, you leave Coriander and visit a website operated by others, which has its own privacy practices. This policy covers only Coriander.

Your control and choices

Because your data stays on your devices, you remain in control of it:

You can edit or delete any recipe in the extension or on the Playdate at any time, including community recipes you have downloaded.
You decide if and when the Playdate app fetches community recipes; it never does so on its own, and the Playdate system asks your permission before its first network connection.
You can turn the optional page-highlighting permission on or off in the extension’s Settings.
Uninstalling the extension from Chrome deletes the data it stored in your browser. Removing the app from your Playdate deletes the data stored there.

We hold no copy of your information, so there is nothing for us to access,
correct, or delete on your behalf.

Data security

Your recipes and settings stay within your browser’s protected storage and on your Playdate, and are never transmitted, so there is no transfer of your content for an outside party to intercept. Syncing between the extension and the Playdate happens over a physical USB cable that you connect. The only network requests Coriander makes are to our own website, the extension’s version check and the Playdate app’s
community-recipe download, both described above, and both use an encrypted HTTPS connection.

Children’s privacy

Coriander is a general-audience cooking tool. It does not knowingly collect personal information from anyone, including children, because it does not collect personal information at all.

Changes to this policy

If we update this policy, we will post the new version on this page with an updated effective date. Any material change will be reflected here.

Contact

Questions or concerns? Contact Summer Storms at hello@summerstorms.org.