Recily turns things into recipes in three ways, and each one sends what you give it to our server, which passes it straight on to Anthropic's API to do the actual extraction. Our server holds the API key and forwards the request — it doesn't store what you send.
During onboarding we also ask a few short questions (e.g. your cooking experience and what brings you to the app) to personalize your experience — these answers stay on your device and are never sent anywhere.
Recipes you save, your cookbooks, grocery list, meal plan, onboarding quiz answers, and preferences like your metric/imperial unit choice are all stored locally on your device using on-device storage. There is no account and no cloud sync. If you uninstall the app, this data is deleted along with it.
When the app crashes or hits an unexpected error, it sends a diagnostic report to Sentry, our crash-reporting provider, so we can find and fix the problem. A report contains the error itself, the app version, your device model and OS version, and a short trail of the screens and requests leading up to it. It does not contain your saved recipes, your dish photos, or the text you paste. We use these reports only to fix problems — never for advertising or tracking — and because the app has no account, they aren't linked to your identity. Sentry stores them on our behalf; email us if you'd like a report deleted. Read Sentry's Privacy Policy.
We do not sell your data to third parties.
Subscription purchases are processed by the App Store or Google Play, using RevenueCat to manage subscription status. We never see or store your payment details.
Since dish photos, imported page text, and pasted recipe text are all processed by Anthropic's API, their privacy policy also applies to that processing. Read Anthropic's Privacy Policy.
Questions about this policy? Reach us at andreas.duca@gmail.com.