Recipie AI — Privacy Policy
Last updated: 17 September 2026
Recipie AI turns a photo of your ingredients or a meal into recipes and calorie estimates. This policy describes exactly what the app does with your data. It reflects the app's actual behaviour at version 1.0.0.
The short version
- There are no accounts. We never ask for your name, email or phone number.
- Your recipes, meal plans, calorie log, shopping list and the photos of the meals you log stay on your device.
- Photos you take or choose are sent for analysis and not stored by us. The copy of a logged meal's photo is kept on your device, not on our servers.
- If you subscribe, Apple takes the payment. We never see your card.
- We do not use analytics, advertising, or tracking of any kind.
What leaves your device
Photos. When you snap ingredients or a meal, the app downscales the image on your device (longest edge 1024 pixels, JPEG) and sends it to our server function, which forwards it to Google's Gemini API for analysis. Our function passes the request straight through: it does not write the photo to a database, a file store, or an application log. Google processes the image under its own API terms; see "Third parties" below.
Dish names. To show a photo alongside a recipe, the app sends the dish name (for example "shrimp scampi") to Unsplash, falling back to Pixabay, then Pexels, then Spoonacular. These are plain search terms. No photo of yours and nothing identifying you is included.
Subscription status. If you subscribe, our subscription provider receives the purchase and returns whether it is still active. See "Subscriptions" below.
Nothing else. Ingredient lists you type, servings, budgets, ratings and logged meals are never transmitted.
What stays on your device
Everything the app remembers lives in your device's local storage and is removed when you delete the app:
| Stored | What it is |
|---|---|
ra_recipes, ra_session | Generated recipes and where you were in one |
ra_rating_* | Star ratings you gave |
ra_plan_setup, ra_week, ra_plan_id | Store, household size, budget, moods, appliances, the generated week |
ra_meals | Meals you logged, with calories and macros |
ra_shopping_* | Which shopping-list items you ticked off |
ra_profile, ra_images | Display preferences and a cache of dish photo URLs |
Meal photos. When you log a meal from a photo, the app keeps that photo as a JPEG file inside its own folder on your device, named after the meal. It is not uploaded anywhere: the copy sent to Google for analysis is the one described above, and this one never leaves the phone. Because it sits in the app's Documents folder, it is included in your iPhone's normal iCloud device backup, under your own Apple account — we have no access to that backup. Deleting a logged meal deletes its photo, and the app removes any photo left without a meal behind it the next time it starts. Deleting the app removes all of them.
The profile screen shows placeholder details in this version. It is not your data and is not sent anywhere.
Subscriptions
Some features need a paid subscription. It is sold as an auto-renewing in-app purchase — a yearly plan with a free trial, or a weekly plan — and the following is true of it:
- Apple takes the payment. The purchase happens inside Apple's in-app purchase flow. We never receive, see or store your card number, billing address or Apple ID.
- RevenueCat processes the purchase on our behalf. RevenueCat is the service that talks to the App Store for us and tells the app whether your subscription is active. It receives your purchase history for this app — which plan you bought, when it started, when it renews or lapsed — and it creates a random anonymous identifier for your installation so it can keep that record straight. We never set that identifier, and because the app has no accounts there is nothing for it to be joined to: no name, no email, no phone number.
- What is not sent. None of your recipes, meal plans, calorie log, shopping list or photos are sent to RevenueCat or to Apple.
- Cancelling is done in Apple's subscription settings on your device, not by us. The app has a button that opens that page for you, and a Restore button that re-reads a subscription you already own on the same Apple ID.
Third parties
- Apple processes payment for subscriptions and holds the receipt.
- RevenueCat receives subscription purchase records and an anonymous installation identifier, as described above.
- Google (Gemini API) receives your photo to identify ingredients or a meal. Google's handling is governed by its API terms. Depending on the API tier in use, Google may retain content for a limited period for abuse monitoring, and on some tiers may use it to improve its services.
- Supabase hosts the server function that relays these requests. As a hosting provider it may record standard request metadata such as IP address and timestamp in its platform logs. Our function adds no logging of its own.
- Pixabay, Pexels, Unsplash and Spoonacular receive dish-name search terms only.
We have no other processors. We do not sell or share data with data brokers, and we run no advertising.
Children
Recipie AI is not directed at children under 13 and we do not knowingly collect information from them.
Your choices
Because there are no accounts, there is no profile to export or delete. Removing the app erases everything it stored. To stop sending photos entirely, do not use the camera or Calorie Snap features; the rest of the app works without them.
Changes
Material changes will be reflected here with a new "last updated" date.
Contact
Questions about this policy: darrenislivinghisbestlife@gmail.com