Updated October 14, 2026
Savor Privacy Policy
Savor uses data to provide dinner recommendations, guided cooking, subscriptions, and optional recipe imports.
Data you provide
Your cooking profile may include dietary preferences, allergies, foods to avoid, equipment, and dinner preferences. Cooking history can include completion details and optional fixed-choice reflections. Your profile, dinner plan, cooking history, Regulars, and accepted recipe copies are stored on your device. Savor does not require an account or offer cross-device sync.
How Savor uses data
Tonight selects recipes on your device. Saved allergies, avoided foods, and substitution text are not sent to an AI service for recommendations. Apple processes subscription purchases. Savor checks subscription access, and its import service verifies signed purchase and app-integrity proofs to authorize imports and enforce usage limits. These proofs and service identifiers do not give Savor your Apple password or payment-card details.
Recipe Import
When you choose to submit an import, Savor sends the recipe text or source link and your review corrections to its service. For a permitted public link, the service may retrieve source text, captions, audio, or visible recipe text. Cloudflare provides the import API and storage; Google Cloud provides retrieval and Gemini processing. The content is used to prepare the recipe you review. Your saved cooking profile is not included in the import request.
Imports use private request and device identifiers. Source processing and retained artifacts are subject to access, retention, and reuse restrictions. Source images and shared recipe caching are not enabled in the current candidate. Accepted recipes are saved locally so you can cook them offline. Provider processing may involve retention under the provider’s service terms; Savor does not promise zero provider retention.
Product analytics
Savor keeps a limited queue of product events on your device and sends them to its own service when configured and reachable. Events can include a recipe or plan identifier, a dinner count, fixed readiness or cook-again choices, your fixed answers to “Was tonight good?” and “Would you have ordered in tonight?”, timer actions, and purchase-result state. Events are associated with a pseudonymous installation identifier. They exclude free-form allergy, avoid, substitution, recipe, and note text. Savor does not use advertising identifiers or a third-party advertising or analytics SDK.
Storage and deletion
In You → Privacy, you can export local dinner data and delete your local profile, dinner history, Regulars, accepted imports, shared drafts, and analytics queue. The delete action also requests deletion of uploaded analytics. If the service cannot be reached, Savor retains the deletion credential and retries when you reopen the app. Deleting local data does not cancel your Apple subscription.
Deleting local copies does not itself erase server import records or Apple’s transaction records. Import processing checkpoints expire after 24 hours for source evidence and seven days for derived facts, or sooner when access expires; scheduled cleanup removes expired checkpoints. These checkpoint limits do not apply to all import request, review, or accepted-recipe records. Those server records remain until their applicable deletion process runs, including a verified support request. Minimal purchase, security, and usage records may be retained to enforce access and prevent abuse. Email zw@wk-llc.com for access or deletion of server data; the support page explains what to include and how we verify a request. Apple’s subscription records remain subject to Apple’s account and retention practices.
Uploaded product events are scheduled for deletion after 90 days. A limited analytics deletion record may remain for up to 90 days to reject late uploads. Retention windows describe service cleanup rules; they do not promise immediate removal from provider backups or replace provider retention terms.
Sharing
Savor uses Apple for subscriptions and app distribution, Cloudflare for its backend, and Google services for recipe processing. Savor does not sell personal data or use it for cross-company advertising tracking.
Security and changes
Material policy changes will be posted on this page with a new effective date.