Kitchen Wizz App Privacy Policy
Last updated: 24 October 2026
Kitchen Wizz helps you import and organise recipes, convert measurements, plan meals and manage shopping lists and your cupboard. This policy explains how the mobile app handles information.
Information on your device
Recipes and their photos, shopping lists, meal plans, cupboard items and settings are stored on your device. You can use the core local features without creating an account. Recipe photos are not uploaded by the app's recipe-sync service. Signing out keeps your local library; deleting your account from Settings also clears the app's local account data on that iPhone. Uninstalling the app can remove local data.
Accounts and optional sync
If you create an account, Google Firebase Authentication manages your email address, authentication credentials, user ID and any name supplied through account creation or Apple/Google sign-in. Kitchen Wizz does not receive a readable copy of your password.
When you sign in and link your library, recipes, including their titles, ingredients, instructions, notes, tags and source links, are backed up to our Railway-hosted API and Postgres database. Grocery category overrides and category order are stored in Firebase Firestore. Shopping lists, meal plans, cupboard items, recipe photos and other device settings do not currently sync between devices.
Importing recipes
When you import a website link, the app contacts the recipe website. If the direct request fails, our backend may fetch that page. The website and our hosting provider process network information needed to fulfil these requests. The backend's recipe-import logs record the site's hostname, rather than the full recipe URL.
Measurement conversion and ordinary text parsing run on your device. On supported iPhones, Apple Foundation Models may help structure a recipe on-device. The iOS app does not use our optional Google Gemini recipe-conversion fallback. On Android or web, that fallback can send recipe text through our backend to Google only when explicitly enabled on the server.
Voice input
On iOS, voice input uses Apple's speech-recognition service. Depending on device, language and system availability, recognition may run on your device or be processed by Apple remotely. On Android, voice input uses the device's configured speech-recognition service, which may process audio remotely under that provider's privacy terms. Kitchen Wizz does not upload audio recordings to its own backend or store those recordings. The recognised words become the shopping-list or cupboard text you choose to add. Apple's processing is subject to Apple's privacy terms.
Subscriptions and diagnostics
Apple processes App Store payments; Google processes Google Play payments on Android. RevenueCat manages purchase history and subscription entitlements using a customer identifier; this may be anonymous or linked to your account when you sign in. Kitchen Wizz does not receive your payment-card details.
Firebase Crashlytics receives crash reports and recorded errors, including diagnostic messages, stack traces, device/OS/app information and a Crashlytics installation identifier. We use these reports to diagnose faults. We do not set your account user ID on Crashlytics or deliberately include recipe content in diagnostic context. We do not use advertising trackers or behavioural analytics, and we do not sell personal information.
Reports and support
If you report a recipe issue, our backend stores the reason, recipe title, parsing method and your account user ID if signed in. If you contact support, we receive the information you send. Please do not send passwords, payment-card details or information you do not want included in your support request.
Providers, retention and deletion
Our providers include Google Firebase (Authentication, Firestore and Crashlytics), Railway (API hosting and Postgres), RevenueCat (subscriptions), and Apple (payments, sign-in and speech recognition). Google sign-in is used when configured. Google Gemini applies only to the optional Android/web fallback described above. Information is shared with providers to operate these features, or when required by law. Provider processing and retention also follow their applicable terms.
Saved account data is retained until you remove it or delete your account. You can initiate account deletion in Settings. The deletion process removes synced recipes, linked recipe reports and category preferences, requests removal of the RevenueCat customer record, and closes the Firebase account. If cleanup fails, the account remains available for retry; contact support if you cannot finish. Separately retained diagnostic reports, support correspondence and provider backups may remain for their applicable retention periods or where required by law.
For accounts linked to Sign in with Apple, account deletion first asks you to confirm your Apple identity and requests revocation of Apple's authorization through Firebase. If revocation fails, account deletion stops so you can retry.
Deleting an account does not cancel an Apple or Google Play subscription. Billing continues until you cancel in the store where you subscribed. Manage or cancel it in that store's subscription settings; you can still choose immediate account deletion. Apple and Google may retain transaction records independently.
Your choices and contact
You can decline optional microphone, speech-recognition and photo permissions, use the app without an account, and contact us about access, correction, export or deletion of your information. Some requests require verification of your identity. We will respond according to applicable data-protection requirements.
Kitchen Wizz is not intended for children under 13. If you believe a child has supplied personal information, contact us so we can investigate and remove it where appropriate.
For privacy or support requests, email support@kitchenwizz.com. Material policy changes will be reflected in the date above and, where appropriate, communicated in the app.