Nombook Privacy Policy

Last updated: 9 September 2026

Nombook is a private recipe diary that stores its working copy on your device and, when iCloud sync is enabled, in your private iCloud database. This policy explains what that means in practice.

The short version

Nombook does not collect your data or send it to us. There are no Nombook accounts, no servers of ours, no analytics, no advertising and no third-party tracking. Your cookbook stays on your device and, if you leave iCloud sync on, in your private iCloud database. A recipe is shown to somebody else only when you deliberately create and send an iCloud sharing link for it.

What Nombook stores, and where

Everything you create in Nombook is written to the app's storage on your own device. When iCloud sync is enabled, the cookbook is also synchronized through Apple CloudKit so that devices signed in to the same Apple Account see the same data:

CloudKit stores synchronized data in the private database belonging to your iCloud account. Apple says private-database data is accessible only to the user by default and is not visible in the developer portal. It counts against your iCloud storage quota. You can turn cookbook sync off in Nombook's iCloud Sync settings; that keeps the local copy and stops this device from making new sync changes after the app restarts. Data already in iCloud remains available to your other devices.

The app also synchronizes its language preference and your ordered cuisine and dish-type choices through Apple's iCloud key-value store. Nombook does not operate a server and does not receive any of this data.

Sharing a recipe

When you choose Send a link or Copy link, Nombook uploads a snapshot of that recipe to your private CloudKit database and asks Apple to create a read-only iCloud sharing link. The snapshot can include the recipe title, ingredients, steps, notes, photos, and the profile name you entered in Nombook. Anyone who has the link may be able to read that snapshot, so send it only to people you intend to share it with.

A recipient who opens the link saves an independent copy in their own cookbook and then leaves the CloudKit share. Later edits do not propagate to that copy. Sending the link again refreshes the snapshot. Deleting the original recipe asks CloudKit to remove its shared snapshot and stops the link from serving it; a copy somebody already saved is not removed.

Permissions Nombook may ask for

Camera. Optional. Used only when you choose to photograph a dish or scan a recipe from a cookbook page, a recipe card or your own handwriting. Photos you take in Nombook are saved to the app's own folder. Text recognition happens on your device using Apple's Vision framework; no image is sent anywhere. If you decline, everything else in the app continues to work.

Photo library. Optional. Used only when you pick a photo to attach to a recipe or scan. Nombook uses Apple's standard photo picker, which shows you your library without giving the app access to it — only the pictures you actually choose are copied in. Nombook never browses your library and never stores a reference to your original photos. If you choose Save to Photos on one of Nombook's own images, the app uses add-only access to write that one copy to your library; it still does not read or enumerate the library.

Notifications. Optional, and requested only the first time you start a step timer. It exists so a timer can tell you when it's up while you're in another app or your phone is locked. All notifications are created and delivered locally by your device. If you decline, timers still run while Nombook is open, and the app says so on the timer.

When Nombook uses the network

Nombook uses the network for iCloud sync, recipe-link sharing, and when you ask it to read a recipe from the web. Web access happens if you paste a link or use the in-app browser to find a page and save it.

In those cases your device contacts that website directly, the same way a web browser would. That website will see the ordinary things any website sees — your IP address, and the request for the page — and its own privacy policy governs what it does with that. Nombook sends nothing about you along with the request, keeps no record of what you visited, and the in-app browser uses a non-persistent session, so its cookies and cache are discarded when you close it.

Nombook does not phone home or report that it was opened. It contains no analytics, crash-reporting, advertising, or tracking SDK.

On-device intelligence

On devices that support Apple Intelligence, Nombook may ask Apple's on-device Foundation Models to help make sense of a recipe page or a scanned photo you imported. This runs on your device. The text is not sent to Apple, to us, or to anyone else, and the feature is never required — Nombook falls back to its own parser when no model is available.

Children

Nombook is not directed at children and collects no information from anyone, including children.

Your data is yours

We do not receive your cookbook and cannot view, correct or delete it on your behalf. You are in control through Nombook and your Apple Account:

If iCloud sync was enabled, deleting the app does not by itself delete the private iCloud copy; reinstalling with the same Apple Account can restore it. A copy may also remain in a device backup until you remove that backup through Apple's settings. Copies of recipes that other people already saved from a sharing link belong to those people and are not deleted with your original.

Changes to this policy

If Nombook gains a feature that changes any of the above, this page will be updated before that feature ships, and the date at the top will change.

Contact

Questions about privacy, or about anything else in Nombook: nombooksupport@gmail.com