AIFredo

Privacy Policy

Last updated: [DATE]

1. Who is responsible

The controller for the AIFredo app ("the app") is [OPERATOR NAME], [STREET], [POSTCODE CITY], [COUNTRY]. Email: [PRIVACY EMAIL].

2. No account, no analytics

You do not need an account. The app has no analytics or tracking SDK and does not ask for permission to track you across apps. Your scan history, chats and saved recipes stay on your device.

3. Ingredient photos, text and AI processing

When you scan ingredients or chat with Chef AIFredo, the app sends the photos and text you choose to our backend on Google Firebase Cloud Functions (region europe-west1, Belgium). The backend sends them to OpenRouter, Inc. (USA), which routes them to OpenAI (USA) to create ingredient lists, recipes and answers. We tell OpenRouter not to allow providers that store or train on the data. We do not store your photos or messages on our servers. Error logs contain technical details only, for example the model name and the error code.

We do this only after you agree on the first launch (Art. 6(1)(a) GDPR). You can withdraw your agreement at any time in Settings → Withdraw AI data consent. Without it, AI features do not work.

Do not photograph people, documents or other personal content. The app needs only food.

4. Recipe and ingredient images

The app shows illustrations of ingredients and meals. The backend creates them from the ingredient or meal name only (for example "tomato"), not from your photos. They go into a shared, private image library in Google Cloud Storage and all users can get them. They contain no personal data.

5. Free scan count

To count the free scans per month, the app sends a random install identifier. The backend stores only a one-way hash of it with the monthly count in Google Cloud Storage (Art. 6(1)(b) and (f) GDPR: providing the free plan and preventing abuse). Counts are not linked to your name or store account. When you reinstall the app, it gets a new identifier.

6. App integrity (Firebase App Check)

To block abuse of our backend, Google Firebase App Check confirms that requests come from the real app on a real device. It uses Google Play Integrity (Android) or Apple App Attest (iOS). This can process device and app integrity signals (Art. 6(1)(f) GDPR: securing our service).

7. Subscriptions (RevenueCat)

Apple or Google processes all payments. We never see your payment details. We use RevenueCat, Inc. (USA) to check if your subscription is active. RevenueCat gets a random app user ID, purchase receipts and basic device data (for example the app version, OS and country) (Art. 6(1)(b) GDPR). See the RevenueCat privacy policy.

8. Ads on the free plan (Google AdMob)

The free plan shows ads from Google AdMob (Google Ireland Ltd.). The app requests only non-personalized ads. Google can still process your IP address and device identifiers to deliver ads, limit how often you see them and prevent fraud. In the EEA, the UK and some US states, the app first asks for your consent with Google's consent form (Art. 6(1)(a) GDPR). You can change your choice in Settings → Ad privacy choices. Pro users see no ads. See how Google uses data for ads.

9. Transfers outside the EU

OpenRouter, OpenAI, RevenueCat and Google can process data in the USA. We rely on the EU-US Data Privacy Framework where the recipient is certified, and otherwise on the EU Standard Contractual Clauses (Art. 45 and 46 GDPR).

10. How long we keep data

11. Your rights

You have the right to access, correct, delete, restrict and move your data. You can also object to processing and withdraw consent at any time (Art. 15–21 GDPR). Email us at [PRIVACY EMAIL]. You can also complain to a data protection authority, for example the one where you live.

12. Children

The app is not meant for children under 16.

13. Changes

If we change this policy, we publish the new version on this page with a new date.