Questions

Not yet, and we're not going to invent a date. The recipe library, the ingredient and unit engine, and the data model underneath are built and tested. Meal planning, shopping lists, and sending your list to a store are being built now.

Join the beta list and you'll get one email when there's something real to try. Not a countdown, not a newsletter.

Free during the beta, with no card required. After that there'll be a paid plan with a 30-day free trial, so you can plan a full month before deciding anything.

We haven't set the price yet, and we'd rather say that than put up a number we might change.

You keep them. Every recipe you added stays readable, and you can export the whole library whenever you want — while you're subscribed, after you cancel, or five minutes after you sign up because you want to check that export works.

Your own content is never the thing behind the paywall. That's a deliberate line, and it's written into our terms rather than just promised here.

There are no "our recipes." We don't have a catalog. Every recipe in your library is one you typed, pasted, photographed, or imported.

This is the thing that makes Dog-Eared Kitchen different from most of the category, which starts by handing you a curated collection and hoping your family eats it.

Kroger first — and its banners — with more retailers as we get access to them. Grocery ordering integrations are gated behind each retailer's approval, which is not something we control or can promise a date for.

What we can promise: there is always a plain text and CSV export that works everywhere, including a paper list. That fallback isn't a stopgap, it's a permanent feature, because we've watched competitors lose functionality overnight when a platform switched off an API.

No, and this one matters. Dog-Eared Kitchen does not check, verify, or filter recipes for allergens or dietary suitability.

You can tag your own recipes however is useful to you, but those tags are your notes. We don't verify them and we never infer an ingredient you didn't write down. If someone in your household has a food allergy, read the actual product labels every time.

Because you're entering your own recipes, and your recipes don't come with reliable nutrition data attached. Producing a calorie count would mean guessing at portion sizes and ingredient specifics and then presenting the guess as a number, which looks authoritative and isn't.

We cut nutrition, cuisine, and diet classification early and on purpose. If you want nutrition tracking, a dedicated tool will do it far better than we would.

It's a web app, built to work properly on a phone — which is where you'll use it, standing in an aisle. No install, no app store, and it works the same on your phone, tablet, and laptop.

That's the plan. A household shares one recipe library, one calendar, and one shopping list, so two people can shop from the same list without stepping on each other. It's on the roadmap rather than built today.

Subscriptions. That's the business.

We may also earn a small commission when you choose to send your list to a partner retailer and order from them. It costs you nothing and it changes nothing about what we show you — we don't rank stores by what pays us, and we won't, because a meal planner that steers your groceries for a kickback is a worse meal planner.

We don't sell your data and we don't run ads. Both are in the privacy policy as commitments, not marketing.

We store your email address and the recipes, plans and lists you create. Essentially nothing else. We never sell personal information, we don't run advertising, and we don't store passwords — sign-in is a one-time link or Google.

Delete your account and it becomes inaccessible immediately and is permanently deleted after 30 days. The privacy policy has the full detail.

One person in Colorado, in the open. The about page has the rest, including why this exists at all.