Effective June 29, 2026
Savor Privacy Policy
Savor uses the minimum data needed to provide dinner recommendations, account sync, recipe import, subscriptions, and product improvement.
Data you provide
Your cooking profile may include dietary preferences, allergies, foods to avoid, equipment, and dinner preferences. Cooking history can include ratings, completion details, and notes. If you sign in with Apple, Savor receives Apple’s account identifier and any name or relay email you choose to share.
How Savor uses data
Profile and cooking data power safety filtering, recommendations, progress, sync, and recipe import. Purchase information is verified with Apple to unlock subscription features.
Product analytics
Savor may send pseudonymous, first-party events such as onboarding progress, paywall interaction, recommendation use, and completed dinners. These events use a random installation identifier and never include allergy text, avoided-food text, notes, email, Apple user ID, or advertising identifiers. Savor does not use third-party advertising or analytics SDKs.
You can turn Product Analytics off or request deletion and identifier reset from Profile. Events remain queued on-device during network failures until accepted or deleted.
Storage and deletion
App data is stored on your device. Account and import data may be stored in Savor’s Cloudflare-hosted service when cloud features are used. Product analytics are retained only as long as needed for aggregate product measurement. Use the in-app controls to delete analytics data. Account deletion support is available through the support page.
Sharing
Savor uses Apple for sign-in, subscriptions, and app distribution; Cloudflare for backend hosting; and Google Gemini for eligible live recipe-import processing. Savor does not sell personal data.
Security and changes
Savor uses encrypted transport, signed account sessions, strict data validation, and separated staging and production services. Material policy changes will be posted on this page with a new effective date.