Privacy

Your data.
Your choices.

How your recipes, photos and cooking records are stored, connected and shared.

Effective date: November 7, 2026

At a glance

  • Your private recipes, photos and cooking records start on your device.
  • Apple connections and sharing require your choice; recipients can keep exported copies.
  • Optional cloud AI sends your question and recipe excerpts only when you choose it.
  • The website uses cookie-free traffic analytics; private Kitchen pages are excluded.
  • You control exports and recovery files. Clearing local storage can erase local copies.
Get-togethers, invitations and event photos

When you create or join a get-together, the event details, your chosen name, attendance, contributions and any recipe or photo you explicitly share are stored by Cooking Untamed on Vercel's private hosting storage. Your full Kitchen, pantry, shopping history and other recipes are not uploaded by joining. Event pages are excluded from website traffic analytics.

Your private recovery key grants your role in one event. The app keeps it in Keychain; the browser uses an HttpOnly access cookie, with temporary session storage during joining or recovery. The server stores a hash of the key. A recovery link is different from the invitation you send guests. Invitation possession is not verified email or identity. Cohost permissions require accepting an invitation, and the host can revoke links or remove participants.

Exact locations, guest details and event photos are hidden from invitation previews. Notes go only to the recipients you choose. Photos are resized and re-encoded to remove location metadata. Recipe viewing, event cookbook inclusion and saving personal copies have separate permissions. Copies someone already saved cannot be recalled.

Removing a photo or participant ends access through the event immediately. Unreferenced photo files are eligible for cleanup after 24 hours. Events expire after 365 days without a saved change; reads do not extend that period. Expired content is inaccessible and queued for daily cleanup. Deletion retains only an event ID tombstone for 365 days to reject delayed duplicate creation, without the event's content. Hosting may retain operational logs under its policies.

Updates are saved in the event. No email, text message or push delivery is implied. The app can keep a protected recent event view for up to 24 hours while disconnected. Removed access clears that managed copy when checked online. Exported calendars are independent copies and do not update automatically.

The cooking app

Cooking Untamed has no separate Cooking Untamed account, advertising or analytics SDK. We do not operate a server that stores your private recipe library. Recipes, binders, photos, notes, favorites, pantry contents, shopping lists, and cook history are stored locally in the app. A private activity summary counts actions such as saving, planning, shopping reviews, and cooking on your device. The summary is for you; the app does not send those counts to us. Your library can also sync through your own private iCloud account when iCloud is available. We do not receive that library or sell it.

Imports and images

Photo imports use your camera or selected photos with your permission. Binder covers and cooking-journal photos use the pictures you select in Apple's photo picker. Text recognition, Word document reading and supported video transcription run on your device. Word text, tables, notes and recognized picture text can be retained in the recipe’s private original source; only an embedded picture you choose becomes the recipe image. Recipe images, cook photos, and imported recipe content are kept in app storage and may be included in your private iCloud sync when available. An individual recipe-link import in the app contacts the source website directly from your device, so that site receives a normal web request and applies its own privacy policy. Social sites may block access or require you to supply the caption, a screenshot, or a saved video.

Private video imports

Shared-post imports read text only: captions you supply, supported official metadata, accessible public pages and direct public recipe links. These requests come from your device and stop at login, access checks and rate limits. Neither the app nor our servers download social-platform videos, audio, images or caption tracks. Source platforms receive those normal requests under their own policies. A saved video or screen recording you select is read locally: Apple’s on-device speech tools and image text recognition produce timestamped observations, and local parsing selects source excerpts for your review. Screenshots you add to that draft are read on-device and retain their own source labels; no video timestamp is invented. Required language assets may download from Apple. Recipe text, audio and video are not sent to a remote AI service for this import.

Source text, timestamps, draft edits and selected frame pictures remain private. The app saves a recoverable review draft before removing its temporary shared-video copy. Choosing Keep video makes a separate on-device copy, available under Kept videos for reading again or deletion; that copy is excluded from recipe sharing and library backups. Your original Photos or Files video is not moved or deleted. Saved recipes and chosen images follow your private library settings; they never enter our public catalog automatically. If you choose to share a recipe, its original link and available creator credit remain included.

The browser video reader accepts only a file you choose. Its optional download includes pinned, hash-checked recognition software and a speech model; downloading contacts this website and Hugging Face, which receive normal request metadata. The selected video, audio, frames and transcript are processed in the browser, without uploading them for import. Captured text, timestamps and small frame pictures stay in the private import inbox. Keeping the original video there is an explicit choice; that copy is included in an inbox recovery download until you remove it. Removing the reader download leaves your captured drafts intact.

Private nutrition estimates

For a recipe you save, confirmed USDA food matches, optional gram weights and chosen servings can stay in your private Kitchen and recovery files. They use the bundled historical USDA reference, with no nutrition-service request. These choices can travel in your optional private Apple connection; on the website, return to your connected Kitchen to process updates. Shared recipe, binder and meal-plan exports leave these private confirmations out. Changes to ingredients, source or original servings require a new review. Unconfirmed or unweighed foods stay out of the estimate.

Recipe blog feeds

When you choose Read feed or Refresh in the app or browser, the selected RSS or Atom URL is sent to cookinguntamed.com’s feed reader. Our website fetches that public feed from its publisher and returns the post titles and links for your review. Hosting and publisher services process those requests under their own policies, including normal request metadata. This does not upload your recipe library or sign in to the publisher on your behalf. Subscriptions and review decisions stay on the device or browser where you keep them, with a separate .cufeeds recovery file; they are not part of automatic Apple continuity.

Pantry photos, receipts and barcodes

Selected pantry and receipt photos are read on your device. You review suggested items before adding stock; photo review drafts stay local. Barcode reading uses device support where available, with a typed-code fallback. Remembered barcode/name pairs come from names you verify and remain in your local pantry product registry, with your workspace or library recovery copy. No online product database receives those codes, and the registry is not synchronized through the private Apple connection.

Voice and AI choices

Cook Mode requests microphone and speech permission when you enable voice commands. The app requires on-device speech recognition; it does not switch to server-based recognition when that is unavailable. Cook Mode audio is not saved. On supported devices, enhanced import parsing and plain-language method drafts use Apple's on-device Foundation Models and keep recipe text on the device. Recipe questions can use saved recipe facts, the available on-device model, or your optional OpenAI connection as described below.

An optional AI key is off by default. It is stored in the iPhone Keychain on that phone and is not part of iCloud backup. When you choose OpenAI for a recipe question, the app sends your question and shortened recipe excerpts with your key. Private cook notes are included only when you turn on Include my private cook notes in Recipe reference. You can choose This device for a question even while a key is enabled. No feature in the app requires the key. Removing the key or leaving the switch off keeps answers on the device. The connection test sends only the key, not a recipe.

Recipe translation

The app uses Apple Translation to prepare recipe-text drafts on your device. Apple may ask you to download the required language packs; those downloads use Apple’s services and settings. Method rewrites and translations require comparison with the original before opening a separate recipe copy in the editor. Saving is a separate action. Written quantities, yield, timing and source credit remain as originally supplied.

Optional downloaded voice

Kokoro offers optional local English reading voices. You start its download in voice setup in Cook Mode. The browser downloads about 138 MB of runtime and model files from this site, huggingface.co and its file-delivery hosts; the iPhone app downloads about 221 MB from Hugging Face. Those services receive a normal download request, including your IP address. We do not send recipe text, pantry information, microphone audio or generated speech with the download.

After installation, Kokoro speech is generated on your device. Generated audio stays in a small in-memory playback cache; it is not saved or uploaded. You can remove the download without deleting recipes. Missing files are not downloaded automatically. Natural voice is the default reading choice. If its download is missing or playback fails, reading pauses and offers setup or retry; it does not switch to another voice. The app can also use an Enhanced or Premium installed voice that you explicitly select. An installed browser voice is a separate, explicit choice, limited to voices the browser reports as local to the device. Listening for commands is a separate setting. Stop reading ends playback and prevents late audio from starting. A preparation already running in the app may finish locally. The microphone stays off while the app is speaking, so a step read aloud cannot be heard as a command. Stop reading stays on screen. Browser reading uses its visible Stop control. Recognition availability, audio routes and background behavior depend on the device.

Sharing and devices

The paired Apple Watch receives the active recipe step, matching ingredient text, and timers from your iPhone, and sends controls back to the phone. Cooking Untamed uses Apple CloudKit for private library sync between your devices and separate household sharing with people you invite. Apple processes that data under your iCloud account and its privacy terms. Household participants receive the recipe and grocery information you share.

Recipe and binder exports go to the person or app you select in the system share sheet. You choose whether an app file or PDF includes recipe photos, a binder cover, and cook photos with their captions and dates. Personal ratings, journal notes without photos, shopping lists, and pantry contents stay out of those exports. Sharing an individual cook photo sends that photo, its caption, and a recipe file. These files are independent copies; recipients can keep or forward them.

Copy to Apple Reminders asks for permission when you choose a destination list. It reads available list names and checks the chosen list for earlier copy markers, then writes the selected grocery text, notes and source-list name with a marker used to avoid duplicate retries. The destination account’s synchronization and sharing settings apply to that copy; later edits do not synchronize with Cooking Untamed. Recipe titles, categories and listed times are also indexed locally for Spotlight search, with updates and removals following the local library.

A shared recipe link carries recipe text in its URL fragment, which the recipient's browser reads locally; it is not uploaded to a recipe server. Anyone with the complete link can read it. Shared links leave photos out. The receiving messaging app or other destination applies its own privacy policy. Your device backup settings may also govern app data backups.

Family cookbooks

When sharing a family cookbook, the owner publishes a selected binder’s recipe text, notes and variations, with optional recipe cover images and binder cover. Original captured source, cooking-journal entries, ratings, pantry contents, groceries, meal plans, step pictures and cook photos stay out of that published version. Invited people view it through their own iCloud account with read-only access, separately from their own library.

Owners choose when to publish updates and manage access for each cookbook. A cached view is the last version received and may remain when a fresh iCloud access check is unavailable. Stopping access does not recall copies saved or forwarded separately. When you explicitly open Apple sharing in the Cookbooks workspace, this website reads only recipe or binder publications that Apple grants the signed-in account access to. Selected-person access uses private invitations; anyone-with-link access still requires an active iCloud account. Browser publishing shares reviewed text-only snapshots; app publications may contain chosen cover images. Publication assets and invitation codes stay out of website analytics. See the family cookbook guide for availability and requirements.

This website

The website is hosted by Vercel and uses Vercel Web Analytics in production to understand aggregate visits. It uses no analytics cookies. Traffic statistics can include page URL, referrer, approximate location, browser, operating system, and device type. Vercel uses a request-derived hash for anonymous visitor measurement and discards visitor sessions after 24 hours. See Vercel's analytics privacy documentation for details.

Website analytics are separate from the cooking app. The website does not automatically access your app's library, microphone or pantry. It reads only recipe and plan content you choose to open in a shared link or import file. The shared-recipe page reads only the text included in a link you open and is excluded from traffic analytics. The browser clipper, custom menu creation, shared-menu pages, your browser Kitchen, Family, Learn, Cuts and the Cookbooks sharing workspace are also excluded. Typed website recipe searches stay in the page and are not added to its URL. Catalog filters and page numbers can appear in browsing URLs. A custom menu link carries its title and selected public recipe IDs in its URL fragment; anyone with the complete link can read them. Copy a menu link or save the menu to your browser Kitchen; neither is stored in a developer-operated database. Vercel also processes requests needed to deliver and protect the site.

Your browser Kitchen

When you save recipes or menus to Kitchen, the website stores your recipe text, menus, dated meals, personal meal notes and Made history, pantry names, known stock amounts and reminder dates, cooked-batch records and explicit stock adjustments, shopping selections, checked purchases, manual package-price estimates and budgets, saved filters/tags/preferences, calendar templates, cooking-journal notes/photos, and cooking steps, ingredient checklists and timer deadlines in this browser's IndexedDB storage. No Cooking Untamed account is required. The workspace remains local unless you explicitly connect the optional private Apple connection in Devices & backup; that connection is shown only when configured and needs your own Apple account. Workspace searches stay in this browser; saved search/filter sets are included in your recovery file. We do not receive this personal content through website analytics.

Browser recipe imports can read PDF text from the pages you select, DOCX text, plain text and photos you select on your device. English photo and scanned-PDF text recognition run on your device with self-hosted recognition software and language files; image data is not uploaded to an OCR service. A source image can also remain a local reference while you review or transcribe it. PDF/DOCX source text can be retained privately with the saved recipe and in recovery files. These documents and reference photos are not sent to our recipe-link endpoint. When you explicitly choose Read public links, those public URLs are sent to this website’s import endpoint, which fetches public recipe markup without your account cookies. Hosting security and operational logs may process request metadata. Failed or incomplete sources require your review; no private or signed-in page access is provided.

The browser import inbox separately keeps source files and reviewed drafts in local IndexedDB storage. Ingredient-card screenshots added within a social draft retain their recognized text, not copies of the selected image files; your original images stay in Photos or Files. For video imports, an original-video copy is stored only when you explicitly choose to keep it. An import-inbox recovery file (.cuimports) carries those sources and may contain personal text and images. It is separate from the recovery file for saved Kitchen records. You choose whether to download or import either file.

Prepare offline Kitchen is optional. It keeps public website code, pages and opened images on this device; it does not cache Apple connections or website API responses. Removing that offline website copy leaves recipes, import drafts and cooking history in their separate storage. Clearing this site’s browser data can erase all local copies. Website updates do not force a reload or clear saved records; save unfinished forms before choosing to update.

Browser Cook Mode generates natural speech locally after its optional voice download on supported desktop browsers. If you explicitly choose an installed browser voice instead, its availability follows your browser and operating-system settings. This is separate from the app’s on-device speech recognition. Timer alerts appear in the open page, without background alarms or push notifications.

A recovery file includes the complete local workspace and may contain personal notes. A continuation link or portable .cuplan file includes full recipe text and dated meals, including meal notes; it leaves out pantry contents, shopping checkmarks, Made history and photos. Continuation links carry this text in their URL fragment, which is read locally and stays out of the web request. You choose when to copy a link, open the installed app, download or import a file. Anyone with the complete link or file can read and keep its content. Each receiving Kitchen reviews and adds independent copies; later edits are local to that Kitchen. Cook-journal photos are resized locally into metadata-free JPEGs; they are included in a full Kitchen recovery file, but not portable plan, recipe or binder files. If optional Apple continuity is configured and you connect, the supported recipes, menus, plans, pantry and shopping records, cook results, preferences, calendar templates, favorites, ratings and School progress are sent to your own CloudKit private database. Apple manages authentication and may retain a sign-in cookie. Account connection settings and synchronization baselines stay outside recovery files; a recovery file may include different versions of conflicting edits and a non-readable account marker used to keep copies separate, without Apple account names or sign-in tokens. Disconnect stops this browser connection and leaves local data and existing private iCloud items intact. This is separate from the Cookbooks publication workspace, where you can explicitly open authorized shared recipes and binders through Apple. Browser storage can be cleared or evicted, so keep recovery files somewhere you trust. Use Kitchen → Devices & backup to export a copy or erase this browser workspace.

Children and shared devices

The app does not create child profiles or check a person’s age. On a shared device, an adult should manage Apple invitations, camera and microphone permissions, optional AI connections, and any content shared outside the household. Keep private exports and API keys out of shared folders.

Contact and changes

For privacy questions, email support@cookinguntamed.com. If you contact us, we receive the information you choose to include in that message. To remove local app data, delete it in the app or delete the app from your device. Updates to this policy will include a new effective date.

School and learning practice

School progress includes read marks, dated practice logs, your self-check scores, notes, optional photos and weekly goal. It starts on your device and is included in your private app library backup or browser Kitchen recovery file. Shared recipes, binders, cookbooks and meal-plan exports leave this progress and its photos out. Existing quick-practice notes and bookmarks remain available; matching bookmarks carry into School as undated prior practice, without invented dates or scores.

If you connect optional private Apple continuity, School progress can be sent to your own CloudKit private database. In the browser, Learn’s Progress & your devices panel keeps the consent-aware connection available as you move between lessons. It does not connect to Apple before you choose to connect. In the app, saving School progress schedules the existing connection when available. This does not share your progress with household members or cookbook readers.

Learning calculator inputs stay on their page. Pairing preferences typed on a public menu page stay on that page and are left out of its shared link. Family household votes use the separate explicit Apple connection described in Family.