cuterie

What we collect

Your email address, to create your account and sign you in — either a one-time code we email you, or a password if you've set one up.

What you enter into the app: recipes, ingredients, instructions, ratings and notes, meal plans, shopping list items, and pantry items. This is the actual content of the app — without it, there's nothing to plan or shop for.

Links and text you choose to import: when you paste a recipe URL, share a page to cuterie from Safari, Chrome, Instagram, TikTok, Facebook, or Pinterest's share sheet, or use the Chrome extension, we fetch that one page to pull out the recipe. When the link is an Instagram, TikTok, Facebook, or Pinterest post, we instead ask ScrapeCreators — a third-party service built for this, since those platforms' own pages block a plain fetch — for that post's caption/text, images, and (for videos) a transcript of anything spoken. We only ever look at a page or post because you specifically pointed us at it.

What we don't collect

No location, no contacts, no microphone, no browsing history beyond the single page you ask us to import. No analytics, no advertising identifiers, no third-party trackers, no crash-reporting or usage-tracking SDKs. Camera and photo access is requested only when you choose to scan a recipe or add a photo of a dish — see below.

Where it goes, and who sees it

Everything you enter is stored in cuterie's database, hosted by Supabase, and is visible only to the members of your own household — the people you've invited or who share your household token. We don't sell your data, and we don't share it with advertisers or data brokers. The only outside parties involved are the infrastructure we run on (Supabase for the database, sign-in and recipe photos, Cloudflare for hosting the web app), Anthropic for one-time AI recipe extraction, and — for Instagram, TikTok, and Facebook imports specifically — ScrapeCreators to fetch the post. All service providers, not audiences for your data.

Scanning a recipe photo, pasted caption, or social link

The mobile apps can read a recipe straight out of a photo or screenshot, and both the apps and the web app can do the same with a pasted caption or an Instagram, TikTok, or Facebook post link — so you don't have to type it in by hand. Camera and photo access is only requested when you tap "Scan a photo or screenshot"; pasted text or links are sent only when you submit them in the "Import from a link" box. In every case, it's sent to cuterie's servers, then (for Instagram, TikTok, or Facebook links) to ScrapeCreators to fetch the post, and finally to Anthropic (the company behind Claude) for one-time analysis — Anthropic automatically deletes API inputs and outputs within 7 days and never uses them to train its models. cuterie itself doesn't keep the photo, text, or fetched post content after the recipe is extracted. The result lands in the same editable form as typing a recipe by hand, so nothing is saved until you review it and tap "Save recipe."

Recipe photos

A recipe can have one photo. When you import a recipe, cuterie saves a copy of the dish photo from where it came from, so it still shows after the original post or page changes; you can also take or choose your own. Photos are resized on your device and stored with Supabase at an unguessable web address that only your household's app knows. Photos saved from a recipe's source are only shown inside your household. A photo you add yourself is included when you share that recipe's public link. Changing or removing a photo, or deleting its recipe, deletes the stored file. This is separate from scanning: photos and screenshots you scan to read a recipe are still never stored.

The Chrome extension, specifically

When you click the extension's toolbar icon on a recipe page, it reads that page's content to find a recipe — its structured recipe data when the site provides it, or the visible ingredients and instructions when it doesn't. It only does this when you click the icon; it never runs in the background or reads pages you haven't opened it on. Your household's token is saved locally in the browser via chrome.storage.local so the extension knows which household to send recipes to — it stays on your device and is never sent anywhere except to identify your household when you submit a recipe. You can revoke it any time by generating a new token from the Household tab.

Cleaning up recipe formatting

The mobile apps can tidy up the wording and units in the ingredients or instructions you've already typed or pasted in, using on-device AI where your device supports it. This only runs when you tap "Clean up formatting," only rewrites the text already in that field, and happens entirely on your device — nothing is uploaded to cuterie's servers or any third party.

Deleting your data

You can permanently delete your account at any time from the Household tab — "Delete my account" removes your sign-in and, if you're the only member of your household, all of that household's data along with it. This can't be undone.

Questions

Reach out at legal@jaduino.com. Using cuterie is also covered by our Terms of Service.