Privacy Policy
Last updated: 12 October 2026 · Versión en español (prevails in case of conflict)
FrigoChef is an app to manage your fridge, make the most of your food and decide what to cook, available on Android (Google Play) and iOS (App Store). This policy explains what data we process, why, who we share it with and your rights under the GDPR and Spanish data-protection law.
1. Data controller
The data controller is José Manuel Fernández Ruiz, an independent developer based in Spain, who publishes FrigoChef on Google Play under the developer name "Jferrui".
Privacy and support contact: quecomemosinfo@gmail.com.
2. Using the app without an account
You can use FrigoChef without creating an account ("Continue without an account"). Your inventory, recipes, weekly plan, shopping list, receipts, diet profile, dish photos and settings are then stored only on your device and never sent to our servers. Receipt and label text recognition (OCR) and the dish score run on the phone itself. Uninstalling the app deletes that data.
3. Data we process when you have an account
| Data | Purpose | Legal basis |
|---|---|---|
| Account: email and password (hashed by Firebase), or the identifier and name of your Google or Apple account if you sign in with them (Apple may give us a relay email). Internal user id, sign-up and last-sync dates. | Create your account, identify you and sync your data across devices. | Contract (Art. 6(1)(b) GDPR). |
| Synced app data: inventory, own recipes (with photos if you add them), cooked recipes and scores, weekly plan, shopping list, favourites, reviews, scanned receipts and spending (store, products, amounts), display name and profile photo, settings, roulette spins, notification preferences and inbox. | Keep your cloud copy and have it on all your devices. | Contract (Art. 6(1)(b)). |
| Diet profile: country, budget, likes and, if you enter them, allergies and intolerances (health data). | Personalise recommendations and never suggest recipes with your allergens. | Your explicit consent (Art. 9(2)(a)) when filling in or editing the survey; you can delete them in Settings → Food preferences. |
| Community: recipes you publish (text, photo, caption, language), your name and avatar next to them, likes, who you follow, your blocked-users list and the reports you submit (post, reason, comment). | Let other users see your recipes, follow chefs, moderate content and protect you from abusive users. | Contract (Art. 6(1)(b)) and legitimate interest in a safe community (Art. 6(1)(f)). |
| Chef Pro subscription: user id, purchase and renewal history, platform and app version (handled by RevenueCat; Apple or Google process the payment and we never see your card). | Activate and keep your subscription and restore it on other devices. | Contract (Art. 6(1)(b)). |
| Ads (free plan only): device advertising identifier (AAID on Android; IDFA on iOS only if you allow it), IP address and approximate location, interactions with ads, device diagnostics. | Show and measure ads and prevent fraud; personalise them only if you accept. | Consent (Art. 6(1)(a)) for personalised ads, collected with Google's consent form; legitimate interest (Art. 6(1)(f)) for non-personalised ads and security. |
Public in the Community: your posts (recipe, photo, caption), your username, your avatar, the Chef Pro badge and who you follow. Everything else is private and only you can access it.
We do not use third-party analytics or crash-reporting tools. The app is not directed at children under 13 and we do not knowingly process their data.
4. Processors and third parties
- Google LLC / Google Ireland Ltd. — Firebase (Authentication, Cloud Firestore, Cloud Storage, Hosting): accounts, database, photos and this website. Database servers in the European Union ("eur3"); Google may process data in the US under the EU-US Data Privacy Framework and standard contractual clauses. Firebase privacy.
- Google Sign-In and Sign in with Apple: only if you choose to sign in with those accounts; their own policies apply.
- RevenueCat, Inc. (US): validation and management of the Chef Pro subscription. RevenueCat privacy policy.
- Apple Inc. and Google as app stores: subscription billing under their terms.
- Google AdMob, its User Messaging Platform (Google Ireland Ltd.) and its advertising partners: ads in the free plan. How Google uses data. The partner list is shown in the in-app consent form.
Transfers outside the EU to Google and RevenueCat rely on the EU-US Data Privacy Framework and the European Commission's standard contractual clauses. We do not sell your data.
5. Ads and your consent
The free plan may show Google AdMob ads (in the recipe list, after finishing a recipe or a scan and, optionally, videos in exchange for an extra use). In the EEA, UK and Switzerland we first ask, with Google's consent form, whether you accept personalised ads; declining is as easy as accepting and the app works the same. On iOS, Apple's tracking prompt (ATT) is only shown if you accepted the consent form first.
You can change your choice at any time in the app: Profile → Settings → Privacy → Ad privacy. Also on iOS: Settings → Privacy & Security → Tracking; and on Android: Settings → Google → Ads (reset or delete the advertising ID). Chef Pro subscribers see no ads and are never asked for ad consent.
6. Retention
- Account and synced data: while the account exists. When you delete it, data is removed immediately; backups are purged within 30 days.
- Community posts: until you delete them or your account.
- Content reports: moderation log with an internal id, kept on the basis of legitimate interest (community safety) and no longer identifying you once your account is deleted.
- Subscription data: as required by tax law and the stores.
- Advertising data: according to Google AdMob's policies.
7. Deleting your account
You can delete your account and all your data in the app at Profile → Settings → Account → Delete account, or by emailing quecomemosinfo@gmail.com. Details at delete account.
8. Your rights
You can exercise your rights of access, rectification, erasure, restriction, portability and objection, and withdraw consent at any time, by writing to quecomemosinfo@gmail.com from your account email. We answer within one month. You may also lodge a complaint with the Spanish Data Protection Agency (www.aepd.es) or your local authority.
9. Security
Data travels encrypted (TLS) and is stored on Google's infrastructure with access rules that prevent any other user from reading your private data. Passwords are handled by Firebase Authentication and never stored in clear text.
10. Changes
If this policy changes materially we will say so in the app and on this page with a new update date.