Press one button. Find out what's for dinner. Cook it.
Last updated 14 September 2026
The short version. whok has no accounts and no sign-in. It does not track you, carries no advertising and no third-party tracking code, and nothing about how you use the app is reported anywhere. The recipes live inside the app on your phone, so browsing, randomising and cooking work with no network at all and send nothing anywhere.
Five things do leave your phone, and only when you choose them: a meal photo you send in, a meal you built and chose to share, a feedback message you write, a report you file about someone else's photo or shared meal, and, if you subscribe to Super Whok, the record of that purchase.
whok is made by Louis Whittome, an individual developer in the United Kingdom, who is the data controller for anything described here. Contact: hello@whok.app.
Your household size, your dietary and allergen filters, your favourites and your record of meals you have cooked are stored only on your device. They are never uploaded. Deleting the app deletes all of it.
whok also keeps a running count of how many meals it has suggested to you and how many of them you went on to cook, shown to you in Settings. That count is kept on your phone, is not attached to any identifier, and is not sent anywhere — there is no analytics service behind it, and nobody but you can see it.
If you choose a photo of a meal you cooked and send it, it is uploaded and stored on Cloudflare R2. Every photo is reviewed by hand before it is shown to anyone. Approved photos are then public: they appear in the app for everyone who opens that recipe, and they are served from a public address.
Only send photos of food you cooked. Do not send photos with people, faces, documents or anything else identifying in them — once a photo is approved it is public, and that cannot be undone for copies already downloaded.
Photos are stripped of location and camera metadata during upload. Rejected photos are deleted.
Meals you build yourself stay on your phone until you tap Share on one.
Doing that uploads a copy of that meal — its name, its ingredients, its method and the
calorie, cost and allergen estimates worked out from them — to a database run on
Cloudflare, and gives you back a link like whok.app/m/ followed by twelve
characters. Anyone with the link can read the meal, in the app or in a browser. There is
no account on it and no name attached to it, only the device code described below.
A shared meal is stored on our servers and can be read by us. That is how a link can be taken down and how a report can be acted on, and it is true of every share from the moment you tap the button.
What a share is not is public. It is unlisted: there is no feed, no browse, no search and nothing anywhere that turns links into a directory. The only people who can find a shared meal are the people you send the link to. Unlike a photo, a shared meal is not reviewed before it goes out — the link works immediately — which is the trade for a link you can send now rather than tomorrow.
A share is a snapshot, frozen when you tapped Share. Editing the meal afterwards does not change what the link serves, and sharing it again makes a second, separate link.
You can take a link down at any time. On any meal of yours that has links out, the menu has Links you've sent — revoke one link or all of them at once, from the phone that sent them. A revoked link stops working straight away and says so to anyone who opens it. Losing or reinstalling the app means losing the ability to revoke, because there is no account to prove the meal was yours; email hello@whok.app and it will be taken down by hand.
Meal photos and shared meals are content whok's users create, and there is a line under what may be sent through it. Objectionable content is not tolerated. Do not send or share anything abusive, hateful, harassing, sexual, violent, illegal, or anything that is not yours to send — and do not use a recipe's name, method or ingredient list as a way to carry any of it. There is no exception for content sent by a link rather than published: a shared meal reaches a real person and is covered by exactly the same rule.
Anyone can report a photo or a shared meal from inside the app, and the web page a shared link opens carries an email link for reporting it, so somebody who never installs whok still has a route. Reports are reviewed by hand, normally within 24 hours. Content that breaks this rule is removed, and the device that sent it is blocked from sending anything again — which also takes down everything else it has shared. There is no appeal queue and no second account to make, because there are no accounts.
The first time whok needs to talk to its server it generates a random code and keeps it on your device. It is not your Apple ID, not your advertising identifier, and not Apple's vendor identifier — it is a random number that means nothing outside whok, and it is not connected to your name, email or phone.
It is sent with photo uploads, shared meals and reports, for one reason: to enforce the daily limit on each, to prove that a link you are revoking is one you sent, and to block a device that repeatedly sends things it shouldn't. Reinstalling the app generates a new one — which is why a reinstall loses the ability to revoke links sent before it.
The feedback form in Settings submits to a Google Form. That means Google receives whatever you type, including the optional email address, and handles it under Google's privacy policy. The email field is optional and exists only so a reply can be sent; leave it blank and the feedback is anonymous. Nothing else about you or your phone is attached to a feedback submission.
Super Whok, the weekly meal planner and the shopping list built from it, is a subscription. Buying it, restoring it and redeeming a code all happen through Apple: you pay with your Apple Account, and Apple handles the payment, the renewals and the cancelling under Apple's privacy policy. whok never sees your card, your name or your Apple Account.
To know whether your subscription is active, whok uses RevenueCat, a company that checks App Store purchases for apps. The app asks RevenueCat whenever it needs to know, which includes when it opens. RevenueCat receives an anonymous app user ID made up on your phone, the purchase receipts Apple issues (which subscription, its price, and when it started, renews or ends), and the ordinary technical detail any request carries: the app version, your phone's system version, its country and language settings, and its IP address. It receives no name and no email, because whok has neither, and that user ID is not connected to the device code described below. RevenueCat handles it under RevenueCat's privacy policy, and it is not used to track you or to advertise to you.
Reporting a photo or a shared meal sends what is being reported — the photo's identifier, or the link's token — along with the reason you pick and your device code, so the report can be reviewed and abuse traced back to the device that caused it. Reporting a shared meal from its web page instead is an ordinary email to hello@whok.app: it carries no device code, but it does carry your email address, as any email does.
Cloudflare hosts the server, the photo storage and the database. Google receives feedback submissions, and Apple and RevenueCat receive the record of a Super Whok purchase, all as described above. That is the entire list. Nothing is sold, rented or shared with advertisers, data brokers or anyone else, and there is no analytics provider.
Approved photos are kept while the recipe uses them. Rejected photos are deleted on rejection. The upload record — the device code, the time and the recipe — is kept so the daily limit and any ban still mean something. Feedback stays in the Google Form until it is dealt with. RevenueCat keeps the record of a subscription so that Restore purchases can find it again on a new phone.
A shared meal has no expiry date: it is kept until you revoke it or we take it down, because a link you sent someone should still work when they get round to cooking it. A revoked or removed share stops being readable immediately, and its row is kept after that — it is the record of what was shared and, where something was taken down, the evidence for the decision. Ask at hello@whok.app if you want a share of yours erased outright rather than switched off.
Under UK GDPR you can ask for a copy of what is held about you, ask for it to be corrected, or ask for it to be deleted. Because there are no accounts, the practical way to do this is to email hello@whok.app describing the photo you sent, the meal you shared, the feedback you left or the subscription you bought so it can be found — for a shared meal, the link itself is the quickest way to identify it, and for a subscription, the order ID on Apple's receipt email. Photo uploads, shared meals and reports are processed on the basis of legitimate interests — running the service and keeping it free of abuse. You can complain to the Information Commissioner's Office if you are unhappy with how this is handled.
whok is a cooking app for general audiences and is not directed at children. It does not knowingly collect anything from a child under 13.
If this policy changes, the date at the top changes with it.