LARDAR.

Privacy, plainly.

Last updated: November 2026

The short version

Lardar's job is deciding dinner, not collecting you. Your kitchen lives on your phone. There's no account to create, and we don't sell or share data for advertising. Ever.

Your photos

When you photograph your kitchen, those photos are sent securely to our AI provider to work out what's in them (ingredients, and best-before dates when legible). They're used for that answer and not used to train AI models. The photos you keep — like your supper snaps — are stored on your device.

What stays on your phone

Your inventory, shopping list, cookbook, cooked history, preferences and supper photos are stored locally on your device. Delete the app and they're gone.

Ask Lardar

When you ask Lardar a question, that question, your current ingredient list and tonight's recipe are sent through our own server to an AI service to write the answer — with no account, no device identifier, nothing that says who you are. The conversation lives on your phone for that dinner and is gone when the dinner is. We don't store it, and we don't use it to train anything. If that ever changes, this page changes first.

Anonymous tallies

To see what’s working, the app sends bare counts — “a scan happened”, “a dinner was cooked” — to our own server: an event name, a date, a number. No identifiers of any kind travel with them (not even an anonymous device id), so nothing stored can be connected to you or your kitchen. There’s a switch in You → Your data; it starts on, and turning it off stops the counts and bins any that haven’t been sent. One thing we always count, switch or no switch, is our own AI calls — how long each took and what it cost us — because that’s about our server, not about you.

What’s in Britain’s kitchens

From version 1.1, when the switch is on, our server also keeps one anonymous line per scan and per dinner — the ingredient names the reader saw (and a brand name when one was printed on the pack), the dish it wrote, a date — and, when you rate a dish, the dish name and your again / maybe / no. We add them up across every kitchen using Lardar. Nothing about who owned them is recorded, because the server never knows: no name, no account, no device id. Your address is looked at only to stop abuse and, from 1.4, to tell which part of the country a request came from (a region or a city at most); the address itself is never stored. Your photos go through our server to Anthropic’s AI, which reads them for ingredients; neither of us keeps them. It’s how the reader gets better, and how we’ll be able to say, honestly, what the country has in its fridge on a Tuesday. The same switch turns all of this off — off means off. We’ll publish what we learn; we’ll never sell a list.

Voice. When you switch on read-aloud while cooking, what you say is turned into words by your phone, not by a server, and nothing is recorded. A question you ask out loud goes to Lardar as text, exactly as if you had typed it into Ask Lardar, and is not kept.

Asked first. The first time you do anything that would send something to the AI — a photo, a typed list, a question, a week's plan — Lardar shows a short card saying where it goes and asks first. "Not now" sends nothing.

New in 1.4

Payments

Lardar has a free lane: five dinners, counted on a stamp card. After that it’s Lardar Plus: £2.99 a month, with the first week free the first time you join, or £24.99 a year. Apple processes the payment; we never see your card details. Cancel any time, in one tap, inside the app.

Health data

If you choose to link Apple Health, meal logs go directly from your phone into Health. We can't read your Health data on any server, because we don't have your data on servers.

Questions

Email hello@lardar.co — a human (one of the two of us) answers.

Lardar Ltd · Company No. 17423484 · Registered in England & Wales · ICO registration ZC253207


← lardar.co