This Privacy Policy describes how Recipe Keeper ("we", "us", or "the App") handles information when you use the Recipe Keeper iOS application.
We are 407 Studios. We made Recipe Keeper to help you privately collect and cook recipes you love. We collect as little data as possible, never sell it, and you can delete it at any time.
1. Information we collect
1.1 Information you give us
- Recipes and content you create. Ingredients, instructions, photos, notes, ratings, meal plans, and tags you add to the App. This data is stored locally on your device and synced to your private iCloud account.
- Imported content. When you import a recipe from a URL, photo, screenshot, PDF, Instagram, TikTok, or other source, the relevant text and images are processed transiently to extract a structured recipe.
- Subscription information. If you purchase a Recipe Keeper Pro subscription, Apple processes the payment. We receive a transaction receipt that we verify with our payment partner (RevenueCat). We do not see or store payment card details.
1.2 Information collected automatically
- Device and diagnostic data. Crash reports, performance metrics, and approximate locale via Firebase Crashlytics and Firebase Analytics. These help us find bugs and prioritize improvements. You can disable analytics at any time in iOS Settings › Privacy › Tracking.
- Push tokens. If you allow notifications, Apple issues an anonymous device token that we store via Firebase Cloud Messaging so we can send cooking reminders and updates.
- Remote configuration. Firebase Remote Config delivers feature flags and limit values to the App. It does not collect personal data.
1.3 Permissions we request
- Camera. Used to scan recipes from cookbook pages, screenshots, or PDFs you choose.
- Microphone. Used to power voice search inside the App. Audio is processed by Apple's on-device speech framework and is not transmitted to our servers.
- Photo library. Only photos you explicitly select are read.
- App tracking transparency. Only used to enable optional, anonymized analytics. The App functions fully if you decline.
2. How we use information
- To run the App and deliver the features you've requested.
- To extract structured recipes from media you import (see "Third parties" below for the AI provider).
- To sync your recipes across your devices via Apple iCloud.
- To diagnose crashes and improve reliability.
- To process subscription billing.
- To respond when you contact support.
We do not use your data to train AI models, and we do not sell your personal information.
3. Third parties we work with
Recipe Keeper relies on the following processors, each governed by their own privacy practices:
- Apple iCloud / CloudKit. Stores your recipes and meal plans in your private iCloud account.
- Firebase (Google LLC). Crashlytics, Analytics, Cloud Messaging, Remote Config.
- RevenueCat, Inc. Subscription receipt validation and entitlement management.
- OpenAI, L.L.C. Text and selected images from a recipe you import are sent to extract a structured recipe. OpenAI processes the request transiently per its API terms and does not use the input to train its models when accessed via the API.
We do not allow these providers to use your data for their own marketing.
4. Data retention and deletion
- On-device data stays on your device until you delete the recipe or uninstall the App.
- iCloud data lives in your iCloud account; deleting it from the App removes it from iCloud.
- Diagnostic data (Firebase) is retained for the period set by Google's defaults, typically up to 14 months.
- Account deletion. You can request deletion of any data we hold by emailing us (see Contact below). We will respond within 30 days.
5. Children
Recipe Keeper is not directed at children under 13 (or under 16 in the EEA / UK), and we do not knowingly collect their data. If you believe a child has provided us information, contact us and we will delete it.
6. Your rights
Depending on where you live (e.g. EEA, UK, California), you may have rights to access, correct, port, or delete the personal information we hold about you, or to object to its processing. To exercise any right, email us at the address below. We will respond within applicable statutory time limits.
7. Security
We use industry-standard safeguards: HTTPS in transit, Apple's on-device sandbox, and access controls on our processors. No system is perfectly secure, so we recommend keeping iOS up to date and using a passcode.
8. Changes to this policy
If we make material changes to this policy, we will update the "Last updated" date and, where appropriate, notify you in the App. Continued use of Recipe Keeper after changes take effect means you accept the revised policy.
9. Contact
Questions, requests, or complaints? Reach out via our Support page or the in-app support form.
407 Studios, the makers of Recipe Keeper.