Supperbook Private kitchen companion

Privacy policy

Your kitchen saves locally first and can stay current through private iCloud.

Supperbook does not require a Supperbook account. The developer does not collect, sell, or use your recipes or personal information.

Effective August 4, 2026

The short version: Everyday recipe, planning, cooking, pantry, and shopping features use a local copy on your device. On a new iPhone or iPad install, synchronization starts automatically through your private Apple CloudKit database when iCloud is available, and you can turn it off at any time. Importing a web link contacts the website you chose. Sharing or backing up data happens only when you initiate it.

Information stored on your device

Supperbook stores the information you enter or import inside the app on the device where you use it. This can include:

  • Recipes, ingredients, instructions, photos, source links, and archived import originals
  • Cooking notes, history, timers, favorites, folders, and tags
  • Meal plans, pantry items, store names, and shopping lists
  • Accessibility, display, and other app preferences

This local copy remains the app's working copy whether iCloud sync is on or off. Supperbook does not operate its own account system, recipe database, synchronization server, or GPT service.

Private iCloud synchronization

In the installed iPhone or iPad app, Supperbook synchronizes supported data through the Apple account already signed in on the device. This starts automatically on a new install and can be turned off in Settings. Supported recipes, folders, plans, pantry and shopping data, cooking progress, timers, history, app colors, accessibility choices, collapsed sections, welcome-guide progress, and bounded recipe covers or original-source files are copied to your private CloudKit database and can be exchanged with your other enabled devices using the same Apple account.

Apple operates iCloud and CloudKit under Apple's terms and privacy practices. Supperbook does not create a Supperbook login or send this data to a developer-operated server. Small app preferences use Apple's iCloud key-value storage; kitchen records and supported files use private CloudKit. Native alert permissions and transient screen state remain device-local.

Turning iCloud sync off stops cloud exchange but keeps the local kitchen and any pending local changes. It does not erase either the local copy or records already stored in your private CloudKit database.

When Supperbook uses a network connection

Core library, planning, cooking, pantry, shopping, backup, and restore features do not require a Supperbook account or server. A network connection is used when you choose a link import or while iCloud sync is enabled. On a new native install, iCloud sync is enabled automatically when iCloud is available and can be turned off under More → Local data.

When you choose to import a recipe from a link, your device requests the page at the address you entered so Supperbook can read its public recipe information. Opening an original source link also takes you to that website. The destination website and any resources it serves may receive ordinary connection details such as your IP address, device or browser information, and the time of the request. Those websites handle that information under their own privacy policies.

Supperbook does not include your saved recipes, plans, pantry, or shopping-list data in those requests. Photo text recognition on supported Apple devices uses Apple’s on-device Vision technology rather than a Supperbook or AI web service.

Analytics, advertising, and tracking

Supperbook does not include advertising, third-party analytics, cross-app tracking, behavioral profiling, or an AI service. The app does not send usage analytics or personal data to the developer.

Backups, exports, and sharing

Supperbook can create portable .supperbook.zip backups and recipe-collection files. A complete backup can contain your app data, recipe cover images, and archived original imports.

These files leave the app only when you intentionally use a save, download, export, or Apple share control. You choose the destination and recipients. After you send a file to Files, iCloud Drive, email, or another service or person, that recipient handles the file under its own terms and privacy practices.

Retention and deletion

Your local information remains on the device until you delete individual records, restore a different backup, clear the app’s local storage, or delete Supperbook. Deleting the app removes its local app data, subject to any device or computer backups you control, but does not by itself erase records already synchronized to your private CloudKit database.

When iCloud sync is enabled, deleting a supported item in Supperbook can synchronize that deletion to your other enabled devices. The developer cannot retrieve or delete private CloudKit records on your behalf. Create a complete backup before deleting the app, clearing storage, or making destructive changes.

Changes to this policy

If Supperbook’s data practices change, this policy and the App Store privacy information will be updated before the changed version is released. The effective date at the top identifies the current version.

Contact

The current contact path and privacy-safe reporting guidance are on the Supperbook support page. The support page does not collect a message by itself. Never include private recipes, shopping data, photos, backup files, or other personal information.