Privacy Policy — Kitchen Book

Kitchen Book — Privacy Policy

Effective date: 13 July 2026  ·  App by WebStacked

The short version

  • Your recipes are stored on your device. We don’t have a server that sees them.
  • There’s no account, no sign-in, and no personal profile required.
  • We don’t use analytics, trackers, or advertising of any kind.
  • Backing up your recipes (to iCloud, Dropbox, or a file) is optional and only happens when you choose it — your own iCloud or Dropbox account handles that, not us.
  • Sharing a recipe with another Kitchen Book user happens phone-to-phone over Bluetooth/Wi-Fi — nothing passes through our servers.
  • Scanning a recipe card is processed entirely on your device.

Who we are

Kitchen Book is developed by WebStacked. This policy explains what information the app handles and how, for anyone who uses it.

Information you provide

Everything in Kitchen Book is entered by you, and stays on your device unless you actively choose to back it up or share it:

  • Recipes you create or import (titles, ingredients, method, notes, ratings, dietary tags, timers)
  • Photos you attach to a recipe (a hero photo, step photos, or a photo of a recipe card you’re scanning)
  • An optional display name and profile photo, shown to people you share recipes with
  • Optional contact details you choose to include when sharing a recipe (e.g. so a recipient knows who sent it)

None of this is sent to WebStacked. We don’t operate a server that receives, stores, or has visibility into your recipes.

Information we do not collect

We don’t use analytics or crash-reporting SDKs, advertising networks, or any form of tracking. We don’t know how often you open the app, what recipes you have, or anything else about your usage — because nothing is sent anywhere for us to see.

How your data is stored

Recipes, photos, and settings are stored locally in the app’s own storage on your device (using Apple’s on-device database technology). Automatic iCloud syncing of this database is explicitly switched off — your data doesn’t leave your device unless you use one of the backup options below.

Optional backup & restore

If you choose to back up your recipes, you can save them to:

  • iCloud Drive — written to your own iCloud account via Apple’s standard iCloud Drive storage. Apple’s privacy policy covers how they handle iCloud data.
  • Dropbox — the app connects directly to your own Dropbox account. We never see or store your Dropbox login or files; Dropbox’s privacy policy applies to that connection.
  • A file you save yourself — a backup file you choose where to keep, e.g. in the Files app.

These backups are only created when you tap to create one. Restoring works the same way, in reverse, at your initiation.

Sharing a recipe

Kitchen Book can send a recipe directly to another nearby device running the app, using Bluetooth and peer-to-peer Wi-Fi (Apple’s Multipeer Connectivity). This is a direct connection between the two phones — it doesn’t use the internet and doesn’t pass through any WebStacked server.

You can also export a recipe as a PDF, an image “recipe card,” or plain text, and send it using the normal share options on your phone (Mail, Messages, saving to Photos, and so on) — those follow whichever app or service you choose to send it with.

Camera, photos, and on-device scanning

If you scan a recipe card or choose a photo, Kitchen Book uses on-device text recognition to read it. Where your device supports it, the app may also use Apple’s on-device Apple Intelligence models to tidy up the scanned text into a title, ingredients, and steps. Both of these happen entirely on your device — the image and text are never sent to WebStacked or to Apple’s servers for this purpose.

You control camera and photo library access through your device’s Settings at any time.

Notifications

Cooking timers use local notifications, scheduled directly on your device to alert you when a timer finishes. These don’t involve a push notification service or any external server.

Children’s privacy

Kitchen Book isn’t directed at children, and we don’t knowingly collect information from children. Since the app doesn’t collect personal data from any user in the first place, this is largely academic — but we wanted to say it plainly.

Your choices

  • Delete any recipe, photo, or note at any time from within the app.
  • Delete a backup from iCloud Drive, Dropbox, or wherever you saved a file, using those services directly.
  • Deleting the app removes all locally stored recipes and photos from your device.

Changes to this policy

If Kitchen Book adds a feature that changes how data is handled — for example, an optional account or an online recipe-import service — this policy will be updated first, and the “Effective date” above will change accordingly.

This policy describes the current version of Kitchen Book. It doesn’t cover future features that aren’t part of the app yet.

Contact us

Questions about this policy or how Kitchen Book handles information can be sent to:
[your contact email — e.g. [email protected]]

Kitchen Book is developed by WebStacked (webstacked.co.uk).