Frequently asked questions

You do not have to. Start with one recipe that matches your evening — bookmark it, cook it once, and see if the timings feel honest. kitchenholy is built to be read on a phone at the stove, not studied like software.

Because trust comes from your pan, not our headline. Read the ingredient list and the order of steps. If the voice matches how you actually cook — clear prep, realistic heat notes — you will know after one meal.

Reading the blog does not require an account. Your browser remembers what you opened; we do not lock recipes behind a login for normal reading. If you subscribe to the newsletter, you can revisit links from your inbox.

No. Skim to the ingredients and steps if you are in a hurry. The longer text is there for technique and context when something goes wrong — you can come back to it later.

You should not have to. The recipe archive and tools are free to use in the browser. If we ever offer a paid extra, it will be clearly labelled — never a surprise paywall on reading.

Reasonable. Open a short post first — check font size, step order, and whether prep and cook time are split. If it feels readable at arm length from the hob, the site is doing its job.

No. Small kitchens are normal. We write for one cutting board, one sink, and the smoke alarm that actually works. Complexity is in the technique sometimes — not in needing a pro kitchen.

Because memory slips when you are tired. A written recipe gives you a shared baseline when you cook with someone else, when you scale portions, or when you need a reminder for baking ratios.

Tell us via the contact form with the page URL. We fix unclear steps and broken links when we can. You are not bothering us — bad instructions waste food.

Reading recipes is not a trial that flips into a trap. If we ever sell a product, the price and terms will be shown before you pay. For day-to-day reading, assume zero surprise charges.

Only if you want email: new posts, seasonal roundups, or reminders when we publish something that fits a busy week. The newsletter is optional — unsubscribe in one click.

Judge it the same way you judge a cookbook: clarity, honesty, and whether it solves a problem you actually have. We will describe scope and price before you pay — no vague “unlock premium” without detail.

Some readers feel the same about apps. Our core recipes stay on the open web. If we ever offer a subscription, it will be for a defined bundle — not the only way to read the blog.

Then the problem is fit, not greed. Our refund policy explains how to ask for help or a refund for paid goods. For free reading, there is nothing to claw back — use what helps you.

If we sell newsletter tiers or digital packs, pick the rhythm that matches how often you cook from links we send. Shorter plans reduce commitment; longer plans sometimes save money — your call.

So do we. Sponsored posts are labelled at the top. Tools list where numbers are approximate. If a partner offer costs money, we will say so plainly.

Sometimes. Email us with scope, audience, and timeline. We do not negotiate in the dark — if there is a fit, we reply with something concrete.

It sets expectations for digital goods or paid newsletters — timelines, how to ask, and cases where the law or payment rules apply. Read it alongside the checkout text before you buy.

You can — and you should compare. We aim for consistent structure: prep vs cook time, honest substitutions, and tools that stay free. If another source fits your week better, use it.

Fair. We use it for replies and — if you opt in — the newsletter. Read the privacy policy for how long we keep messages and who processes mail for us. You can ask to delete contact submissions where the law allows.

No publisher stays forever. We host content like any small site: backups and a domain. If you rely on one recipe, consider saving a copy for yourself — we cannot promise decades of uptime.

We do not sell our mailing list. Sponsored posts are editorial deals — they do not mean we hand your inbox to strangers. If that ever changed, we would ask for consent in plain language.

People who operate the site and any email provider we use to deliver mail. We do not run a public forum — your message is not posted on the homepage.

Privacy ideas travel: minimise data, secure it, explain why you have it. Our policy is written for a general audience; your local law may give you extra rights — ask if you are unsure.

We rarely need accounts for reading. If we add them later, we will use HTTPS and sensible password rules. Never share codes or passwords by email — we will not ask for them that way.

For newsletter subscribers, unsubscribe first — then contact us if you need historical deletion where possible. Contact-form email may sit in backups for a while; we explain that in the policy.

Enough to recover from mistakes — not a guarantee against every disaster. Do not treat the site as your only archive for family recipes.

Neither do we, blindly. Security is process: updates, hosting choices, and limited access. If you report a vulnerability, we try to fix it responsibly — see the security page.

You only need to scroll and read. The recipe card is plain text and numbers. If you can set a timer on your phone, you can use this site — no dashboards or jargon required.

Change one dish at a time. Keep a side or sauce they already like. New recipes fail less often when you do not change five variables on the same Tuesday.

Filter for shorter posts or weeknight tags when we have them. “Simple” here means honest steps — not that every dish is three ingredients.

Use the numbers as guardrails, not handcuffs. When we give a range or a substitution, it is because stoves and flour bags differ. Note what you changed so you can repeat wins.

Print or scribble the ingredient list if that helps. The site is there so you can search again next month — paper still wins for greasy fingers sometimes.

Give them one job with a clear endpoint — stir until thickened, set the timer, wash one tool. Long lectures over boiling water rarely stick.

It happens. Finish safely — adjust heat, add liquid if something scorches — then write us if the wording was unclear. We would rather fix the post than blame your eyes.

Then do not. Pick one recipe with a short ingredient list when you have one calm hour. Cooking systems grow from one repeated win, not from a perfect plan.

Because future-you is still you — tired, rushed, forgetful. Written steps are a kindness to that person.

Algorithms bury posts. Email is a direct line when we publish something worth your Sunday prep — if you want it. You can keep social only; nothing breaks.

Neither do we. Messages should sound like a note from a cook, not a clearance aisle. If we ever sound off-brand, hit reply and tell us.

When we have something useful — not a fixed daily blast. Expect quieter weeks and busier seasons; food publishing is not factory output.

Skim the subject line and save the link for later — or unsubscribe. Inbox peace beats guilt-reading.

So you see new tools and long posts without remembering to check the site. The archive stays public either way.

Forward it. If they want their own copy, they can subscribe — we do not police households.

Only in coarse ways if we ever tailor sends — for example language or region. We do not sell segments to data brokers.

We are not a clinic. Posts may discuss ingredients generally — not your personal history. For allergies, verify packaging every time.

Because a confusing step costs real money in wasted food. Short notes after a fail help us edit posts for the next reader.

They will be labelled at the top — money or free product involved. The recipe still has to work in a home kitchen; we do not publish fiction for a fee.

We turn down partners that want scripted praise. If a product is mediocre, we say so or we do not run the piece. Readers notice when trust breaks.

If we use affiliate links where allowed, we will say so near the link. They do not change our testing notes — they may help fund hosting.

Because good ingredients and tools exist — and independent publishing has bills. Transparency keeps the exchange honest.

Yes. Use the contact form with “Partnership” in the subject. Include audience fit and what a successful project looks like.

Maybe — never guaranteed. Free samples do not buy a positive review; they buy consideration and honest testing time.

If we add them, we will aim for formats that do not wreck reading. Blockers exist — we get it.

We may collaborate on stories when the food fits our voice. Conflicts will be disclosed like any other sponsor.

Because knowing who paid for what lets you judge the angle — same as any magazine.

You still benefit from ratios and technique. When a post lists substitutes, it is so you can pivot without starting over.

Write quantities on paper once — or use our serving scaler on the tools page. Half the stress is deciding; the list removes that layer.

Use stems and peels where it makes sense, freeze stock in small portions, and label dates. Small habits beat a perfect zero-waste week.

Keep a “top twenty” list: oil, salt, onions, eggs — whatever you actually burn through. Everything else can be bought for specific recipes.

Look at what ran out first this week — not what looked pretty in the shop. Rotation beats novelty for weekday cooking.

One notebook row per trip: butcher Saturday, market Sunday — whatever fits your city. Consistency beats optimising every route.

Label jars with initials or dates. Shared fridges need boring rules — boring saves arguments.

Because forgotten bags of flour turn into duplicates and waste. A shallow, honest shelf beats a deep mystery cupboard.

Yes. We write for grocery bags and reusable totes — not Sysco trucks.

Because scaling a cake by guess is how you get a sunken middle. The tools give a first pass — you still taste and adjust.

Ours knows cups-to-ml and serving ratios in one place — fewer taps, fewer unit mistakes. Use what feels faster for you.

Add prep and cook minutes in the time tool on the tools page. If the total shocks you, start earlier or pick a shorter recipe.

We sometimes give rough numbers for curiosity — not for treating conditions. A dietitian beats a blog for medical nutrition.

Only if you treat them as grades. Use them as guardrails: one timer, one scale reading, then your senses.

Because “a pinch” that grows every time changes the dish. Writing down what worked turns luck into a repeatable dinner.

Copy-paste or screenshot — we do not store your calculations on your behalf unless we add accounts later.

Check salt at the end, taste before serving, and keep one clean spoon for tasting. Most errors are fixable if you catch them early.

Because busy weeks happen to everyone. Tools shorten the path from “I forgot to halve the recipe” to “this still tastes right”.

Turn on screen lock rotation if you like landscape, and lower brightness at night. Grease on the glass is normal — voice timers help.

One written plan visible on the fridge: main + sides + who starts what. Shared notes beat shouted instructions across rooms.

Basics: salt style, oil you trust, one sharp knife you actually enjoy. Recipes can flex; habits should not.

Pick one neutral base — rice, bread, plain yoghurt — then add bold toppings for those who want them. Battles rarely help appetite.

Delegate whole tasks with a clear “done” signal: chop these vegetables, stir until this texture. Micromanaging every stir breeds resentment.

Label leftovers with dates. Boring — and it works.

Because the week is a relay race. A short list reduces the 6 pm panic when nobody remembers what thawed.

Time vs control. Kits save shopping; scratch saves money and packaging. We write for scratch cooks — kits are fine when they help your week.

Because future-you is still tired. A note on the fridge is a conversation with that person.

Keep the notebook. Use the site when you want photos, search, or updates — they solve different jobs.

Video helps for technique; text helps for shopping lists and printouts. Mix both — nobody earns a medal for one format.

That sting is real. Next time, cross-check timings with a second source, read comments if open, and trust your thermometer more than any headline.

Some are databases, not voices. If you want context and failure notes, editorial sites and books still matter.

Cheap often means ad-heavy or untested. Compare clarity: are steps ordered for a real stove? That is worth more than a free PDF.

Rarely. One perfect tool beats five half-connected ones. Browser + calendar + maybe a shopping list app is enough for many people.

It can suggest ideas — it can also invent unsafe temperatures or missing steps. Always verify food safety and bake times with a trusted source.

Perfection is the enemy of dinner. Pick one recipe tonight, accept imperfection, and adjust next time.

Because we aim for honest timings, clear steps, and small tools in one place — built for weeknight reality, not influencer gloss.

We read contact messages. We cannot promise instant replies, but we do not ignore clear bug reports or typos that confuse cooks.

We are not a hotline. Lower the heat, add liquid if safe, and finish the meal. Email us after with what went wrong.

Include the recipe URL, what you expected, what happened, and your oven or pan type if relevant. Screenshots help.

URLs change rarely. If we move a post, we try to redirect. If something 404s, tell us.

Small teams move plans quietly. We share bigger changes on the blog or status page when they matter to readers.

Yes. Short, specific ideas beat “make it better”. We cannot build everything — we read everything.

Share links in your household chat, save PDFs of recipes you rely on, and keep a paper backup for holidays.

We do not run meal-coaching services. We can point to posts and tools that fit your question when it fits our scope.

Because trust is built when someone fixes a wrong temperature — not when marketing shouts “we care”.

Not with magic — but with shorter recipes, clearer order of operations, and realistic totals for prep and cook time. That reduces decision fatigue.

Post a visible weekly plan — even three bullets. Shared visibility beats heroic memory.

Guests care about hot food and kindness, not your Instagram aesthetic. A calm timer and a clean plate beat a perfect photo.

Cooking beans, using seasonal produce, and reducing waste are not cheap — they are smart. Shame is optional.

Measure once, taste twice, and remember most home mistakes are edible. The worst outcomes are usually dry, not dangerous — learn the fix.

Pick one technique a month — sear, emulsion, dough — and repeat until your hands know it. Breadth without depth is just stress.

Write the margin notes on paper or in a shared doc: “Grandma uses less salt.” Digital and physical both preserve story.

Automate one thing: a weekly repeating slot for grocery shopping, or a single shelf for “eat first”. Small rails reduce chaos.

Because love does not thicken a sauce faster. Tools give you back minutes for the table talk you actually want.

Cook one recipe from the site this week. If the result feels fair for the effort, come back. If not, tell us why — that is data, not failure.