reciWe is a home for the recipes that matter to you — a place to keep them, cook from them, and see them in new ways. It's built on a simple idea: your collection should be yours.
What reciWe is for
✦Keeping— a personal collection of recipes and kitchen memories, gathered from anywhere you find them.
✦Cooking— making your recipes genuinely easy to follow — scaling, substitutions, and a step-by-step cook mode.
✦Curating— organizing your collection in ways that resurface things you'd forgotten you had.
✦Exploring— finding the connections running through your entries — ingredients, people, places, seasons.
✦Sharing, deliberately— passing a recipe to the few people who matter, not broadcasting to a feed.
✦Staying yours— you control your data and your AI usage — including turning it off.
What reciWe isn't
—A scraper. We don't trawl the internet for content. The discovering is yours; reciWe is where what you find becomes yours to keep.
— No followers, no trending page, no audience to perform for. Sharing here is small and intentional.
A viral network.
—A data business. We don't sell your data, share it with advertisers, or use your collection to train models. It's stored so we can show it back to you — that's all.
How we think about AI
The cooking is yours — AI doesn't make your food better. What it can do, used honestly, is take the friction out of everything around it: capturing a recipe from a photo, a video, or a shared page in seconds, and reshaping long instructions into steps that are easy to follow at the stove. We'd like reciWe to demonstrate that rather than argue it. So its use here is transparent: you can see what it does, run it on your own model and key if you prefer, dial it down, or turn it off. The goal is to show the benefits and dispel the misconceptions — never to force it on you.
Keeping it safe
A place that holds personal entries still needs guardrails. Anything promoting violence, harm to people, or hazardous creations has no home here — that's in the terms, and we'll remove it and close accounts over it. To be straight with you about the mechanism: today that's enforced when something is reported, not by an automated filter. We're exploring modern ML methods to do it proactively, and if we add them we'll say so here — they'd run automatically, never as people browsing your collection.