RecipeTune

Privacy Policy — RecipeTune

Last updated: 28 July 2026

RecipeTune ("the app") turns recipe photos into structured recipes you can scale and cook from. It is developed by Koczan Craft ("we", "us"). This policy explains what data the app handles, why, and the choices you have. By using the app you agree to it.

The short version. Your recipes live on your device and are visible only to you — nothing in RecipeTune is shared with other users or made public. We do not use any analytics or crash-reporting service, so we do not track which screens you visit or what you cook. Ads are always non-personalised. The one time your data leaves your device by design is recipe import: the photo you choose is sent to OpenAI to be read (see §3).

1. Data we handle

DataWhyStored / processed by
Your recipes — title, servings, ingredients, steps, categoryThe core of the app. Stored on your device; synced to your private cloud copy when you are signed in and onlineOn device (SQLite) · Cloud Firestore
Recipe photos — the imported source screenshot and an optional dish photoKept with the recipe so you can re-check the originalOn device · Firebase Storage
A recipe photo you importSent once to be read into ingredients and steps (see §3)OpenAI
Account identifier, and email address if you sign inSign-in, recovery, and linking your recipes to youFirebase Authentication
Preferences — language, default servings, theme, display name, avatarYour settings, applied across your devicesCloud Firestore · Firebase Storage
Import usage counter — a per-day count of importsRate limiting, to control cost and abuseCloud Firestore
Advertising data — advertising identifier and ad-interaction dataShow and measure ads (see §6)Google AdMob

What we do not collect: we use no analytics and no crash-reporting service — no Google Analytics, no Firebase Analytics, no Crashlytics. We do not collect your location or your contacts, we do not scan your photo library (you pick the individual images yourself), and we do not sell your data.

2. Accounts & sign-in

RecipeTune is anonymous-first. On first launch the app creates an anonymous account for you automatically — you can import, save, scale and cook recipes without ever giving us an email address or any other personal detail.

Signing in is optional, and only adds recovery and multi-device sync. You can sign in with an email and password, or with your Google or Apple account. That provider authenticates you and shares your email address (and, for Apple, optionally a name); we never receive your Google or Apple password. Signing in links your existing anonymous account in place, so the recipes you already made come with you.

3. Recipe photos & how import works

This is the one place your content is sent to a third party, so it is worth being precise.

When you import a recipe, the app sends that image to our server (a Firebase Cloud Function), which forwards it to OpenAI to be read into structured ingredients and steps. The result comes back to your device, where you review and correct it before anything is saved.

If you would rather no image ever left your device, you can add a recipe by typing it in manually instead — import is optional.

4. Who can see your data

Your recipes, photos and settings are yours alone. RecipeTune has no sharing, no groups, no public profiles and no feed. Server-side security rules restrict every recipe, image and settings record to the account that owns it — this is enforced on the server, not just hidden in the app. Nothing you create is visible to other users or to the public.

5. Service providers

6. Advertising

The app is free and supported by advertising through Google AdMob. AdMob may collect a device advertising identifier and limited device and ad-interaction information to deliver, cap and measure ads.

Google's handling of ad data is described at policies.google.com/technologies/ads. We do not sell your personal data.

7. On-device data & offline use

RecipeTune is local-first: your recipes are stored in a database on your device and the app works fully offline. When you are signed in and online, changes sync to your private cloud copy so you can use another device; if two devices change the same recipe, the most recent change wins.

Downloaded photos are cached on your device for speed and offline use. Cooking timers use local notifications only — scheduled by your device, not sent from our servers. RecipeTune does not use push notifications and has no notification token.

Deleting the app removes its on-device data. Signing out clears the local copy on that device.

8. Data retention & deletion

9. Children

The app is not directed at children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us data, contact us and we will delete it.

10. International users

The app and its developer are based in Japan. Your data is processed and stored on Google Cloud / Firebase infrastructure, and imported recipe images are processed by OpenAI; both involve servers in the United States and, depending on the service, other countries. By using the app you consent to your data being transferred and processed as described here.

11. Contact

Questions or deletion requests: privacy@koczancraft.com

12. Changes

We'll update this page when the policy changes; the "last updated" date above always reflects the latest revision.