Chefcito Privacy Policy

Last updated: 27 July 2026

Chefcito is made and maintained by Aether Xtudios. This policy explains what Chefcito does and does not do with your data. It's written in plain language on purpose.

If you have questions, email aetherxtudio@outlook.com.

The short version: Chefcito has no accounts, no login, and no server database of its own. Everything you type — your ingredients, pantry, saved recipes, shopping list, and preferences — stays on your phone. The app only talks to the network for three things: generating a recipe the offline recipe library can't cover, loading a recipe photo, and showing an ad or checking your subscription. Details below.

What's stored on your device only

Chefcito stores the following locally, using standard on-device app storage (AsyncStorage). None of it is sent to us, because we don't have a server to send it to:

This data is erased when you clear the app's storage in your phone's settings, or when you uninstall Chefcito. There is no "delete my account" option because there is no account to delete — clearing app data or uninstalling removes everything.

What leaves your device, and why

1. Recipe generation (Google Gemini, via Firebase AI Logic)

Chefcito ships with about 2,382 recipes built into the app, so most requests never touch the network. When your request can't be matched from that offline library, the app sends the ingredient words you typed and the filters you picked (meal type, time limit, diet tags) to Google's Gemini AI model through Firebase AI Logic to generate a recipe.

We do not send your name, email address, contacts, photos, files, or location as part of this request — the app doesn't collect that information in the first place.

2. App integrity check (Firebase App Check + Play Integrity)

To stop bots and tampered copies of the app from abusing our AI usage, Chefcito asks Google Play Integrity to vouch that the request is coming from a genuine, unmodified install of the app. This sends a device-integrity token to Google. It does not send your recipe data or personal information.

3. Recipe photos (Cloudflare)

Recipe photos are downloaded from a Cloudflare R2 storage bucket. Like any image download, Cloudflare's servers see your device's IP address while serving the image. We don't attach any personal or recipe data to these image requests.

4. Ads (Google AdMob)

Chefcito shows interstitial (full-screen) ads through Google AdMob — no banner, rewarded, or app-open ads. Ads appear at most every 30 seconds and only after your first few recipe generations.

AdMob may collect your advertising ID, IP address, and general device information to show and measure ads. Chefcito itself does not build advertising or interest profiles about you — that's Google's ad system, not our code.

If you're in the EEA, the UK, or a US state with similar rules, Chefcito shows a consent prompt (Google's User Messaging Platform) so you can choose personalized or non-personalized ads. You can reopen and change that choice any time from the app's Settings screen.

Subscribing (see below) removes ads.

5. Subscriptions (Google Play Billing)

Chefcito offers two auto-renewing subscriptions — monthly and yearly — that remove ads. Purchases go entirely through Google Play Billing. Chefcito never sees or stores your card number or other payment details; that's handled by Google Play. The app reads your current subscription status from Google Play on your device.

What Chefcito does not do

Children

Chefcito is not directed at children and is not designed to appeal primarily to children.

Security

Network requests the app makes (to Firebase AI Logic, Play Integrity, Cloudflare, AdMob, and Google Play Billing) go over encrypted (HTTPS) connections. Because there's no Chefcito account or server database, there's no Chefcito-hosted account data to be breached.

Changes to this policy

If what Chefcito collects or sends changes, we'll update this page and the "Last updated" date at the top.

Contact

Aether Xtudios — aetherxtudio@outlook.com