Privacy policy

ForkChop is a recipe-matching tool. You tell it what’s in your kitchen and it suggests things you can cook. Everything below describes what happens with the information you give it.

Without an account, your pantry, allergies, dislikes and saved recipes all live in your browser’s localStorage. They are never sent to us. Clearing your site data clears everything ForkChop has ever known about you on this device.

Signing in creates an account backed by Supabase. Your account stores:

• Your email address, so we can send you a magic link.
• Your pantry (raw text, resolved ingredient id, and whether each was typed, scanned or spoken).
• Recipes you’ve saved.
• For recipes sourced from a third party, a snapshot of the recipe so it still renders if that source is offline.

Every row is protected by row-level security keyed on your user id — no other signed-in user can read or modify your data.

We do not use analytics or advertising trackers. We do not sell or share your data. Signing out and deleting your account removes everything the account holds.

Sign-in is passwordless. We never see or store your password, because there is no password. The only cookies we set are Supabase’s authentication cookies, which keep you signed in and are cleared when you sign out. There are no advertising cookies, no third-party analytics, no session replay.

ForkChop hands off to a few services. What each one receives:

Supabase (authentication and database)

Hosts your account and the database above. Sees your email and everything stored against your account. Governed by Supabase’s privacy policy.

Spoonacular (recipe search)

When your pantry is thin on cookable local recipes, ForkChop asks Spoonacular for more. We send the ingredient names and any filters you’ve set (diet, cuisine, meal, allergens, time). We do not send your identity, email or any other stored data. Governed by Spoonacular’s terms.

Open Food Facts (barcode lookups)

When you scan a barcode, ForkChop sends the barcode number — and nothing else — to Open Food Facts to look up the product. No user identifier, no cookies, no other pantry data. Open Food Facts is a free public database.

Your browser’s speech recognition

The microphone button uses the browser’s built-in Web Speech API. On Chrome that means audio is streamed to Google’s servers for recognition; on Safari, Apple’s. That is your browser’s behaviour, not something ForkChop routes. We only receive the transcribed text, and only what you commit from the review tray.

Your device’s camera

The scan button uses your camera locally. Video frames are decoded in-browser and never sent anywhere. Only the resulting barcode number leaves the device.

Grocery checkout providers

When you check out, ForkChop hands off to the store’s own website with your items pre-populated. ForkChop never sees your payment details.You complete the purchase on the store’s domain, under their terms.

Vercel (hosting)

The app is served from Vercel. Vercel receives standard request metadata (IP address, user agent, requested paths) for the same reasons any web host does. Governed by Vercel’s privacy policy.

ForkChop is not directed at children under 13 and we do not knowingly collect data from them.

You can sign out at any time from the account menu, and delete your account by emailing us. Deleting the account removes every row keyed to your user id — pantry, saved recipes, everything.

We’ll update this page when the app’s data handling changes. The date at the top always reflects the last real change.