← Back to RecipeCatalog

RecipeCatalog Privacy Policy

Effective date: October 10, 2026

This policy describes the RecipeCatalog Android app and app support provided by Zajabuk, a developer based in Michigan, USA ("we" or "us"). For privacy questions, contact contact@zajabuk.com. It covers the current app, including development and test releases. Website hosting and services you open outside the app may handle information separately.

Your recipe collection is stored on your device. Some features use outside services. Importing links contacts the source website; choosing Translate sends recipe text to Google; model setup may download files from Google or Hugging Face. Android backup and a cloud folder you select may store copies outside your device. RecipeCatalog does not provide a Zajabuk account or a Zajabuk-hosted recipe sync or recovery service.

1. Information kept in the app

RecipeCatalog stores recipes you enter, import, or save: titles, descriptions, ingredients, instructions, notes, source links, categories, tags, favorites, Want to Try selections, detected allergen and dietary labels, original text snapshots, and cooking history. It also stores meal plans, shopping lists, ingredient-library changes, settings, and cooking progress, including timer deadlines. Notes and food preferences may reveal personal information if you choose to include it.

These records are kept in the app’s private storage on your device. The app can temporarily handle shared text, downloaded webpage text, and images you select or capture for scanning. Original scan photos are not a permanent photo library within RecipeCatalog and are not included in its full-data JSON backup. Keep originals separately if you need them.

2. Photos and text recognition

When you choose a photo or use your camera to scan a recipe, Android’s picker or camera app supplies the selected image. RecipeCatalog processes that image on the device with Google ML Kit text recognition; its recipe-scanning code does not upload the photo to Zajabuk for recognition. The current app does not request access to your contacts, microphone, or precise device location.

Google ML Kit can send SDK operational information to Google, such as device and app information, performance measurements, and an installation identifier. Google describes this in its ML Kit data disclosure and Privacy Policy. On-device recognition does not mean that every supporting Google component is free of network activity.

3. Importing websites and social posts

When you import a URL, RecipeCatalog requests content from the source site and may follow relevant recipe links. Those services receive ordinary connection information, including your IP address, the requested URL, and browser or request details. A source URL itself may contain identifiers or other information. Share only links you are comfortable accessing this way.

Some imports use an embedded browser with JavaScript, cookies, third-party cookies, and local website storage enabled. Source sites and resources they load may use these technologies under their own policies. The capture browser is separate from your normal phone browser and does not automatically reuse its signed-in session. The current app does not provide Facebook or Instagram account sign-in. Import success depends on publicly accessible written content and the source’s access restrictions.

4. Optional on-device AI

AI assistance is optional and is off by default in the current build. When enabled and available, recipe analysis runs on your device using a supported Google on-device model or a downloaded local model. RecipeCatalog’s AI code does not send recipe prompts, text, or scan photos to a Zajabuk cloud AI service.

Setting up or updating a model can contact Google services or download a model from Hugging Face. Download providers receive connection information, such as your IP address and requested model file, and may retain service logs. Google components may process diagnostics under Google’s policies. See Google’s Privacy Policy and Hugging Face’s Privacy Policy. Model availability varies by device. You can turn AI assistance off in Settings; turning it off does not necessarily remove previously downloaded files.

5. Translation sends recipe text to Google

Translation is an online feature. When you choose to translate a recipe, the app sends its title, description, ingredient text, and instructions, together with the target language, to Google’s translation service. Google also receives normal connection information. This is separate from on-device recipe AI. Avoid translating private information you do not want sent to Google. Google handles these requests under its own policies.

The app can retain an original recipe snapshot alongside the translated text. Machine translations can be inaccurate, including quantities, ingredients, allergens, and cooking instructions. Review the result before saving or cooking.

6. Backups, exports, sharing, and Android backup

When you create a full-data JSON backup, the current app exports saved recipe records and history, meal plans, current and saved shopping lists, ingredient-library changes, settings, and cooking progress. Downloaded AI models and temporary scan or browser files are excluded. CSV is a recipe export, not a complete backup of the app. RecipeCatalog does not encrypt these exported files. Protect them and the folder you choose.

Android’s file picker lets you choose a local or supported cloud destination. A selected storage provider receives the files you save there. Sharing or printing sends the selected content to the app, person, or print service you choose. Those recipients control their copies.

The current app allows Android system backup and device transfer. Depending on your Android version, device settings, account, and provider, Android may copy eligible app data to your backup account or another device. This is separate from manual JSON exports and is not a guarantee that everything will be backed up or restored. Manage system backup in your Android settings. See Android’s backup explanation.

7. Information Zajabuk receives

The current app has no Zajabuk-operated advertising or analytics integration and does not automatically send your recipe collection to us. We do not sell your recipe data or use it for targeted advertising. Independent source websites and platform components may collect information as described above.

If you contact us, we receive your message, contact information, and any recipes, screenshots, diagnostics, or attachments you choose to provide. We use them to answer questions, investigate problems, and improve the app. Email and support providers process those communications for delivery and storage. Do not send passwords, payment-card details, or unnecessary sensitive information. If paid distribution is offered, the store or payment provider handles checkout; we may receive order references and purchase-status information needed for support.

8. Retention, deletion, and your choices

Saved app records remain until you edit or delete them, replace them through a full restore, clear app storage, or uninstall, subject to Android restoring an existing backup. Deleting an individual recipe also removes its meal-plan entries and cooking session; it does not necessarily remove items already copied into a shopping list. The Advanced option to delete every recipe clears recipes, meal plans, shopping lists, and cooking progress, but does not erase every app setting, downloaded model, or browser file.

To remove remaining local app data, use Android’s app-storage controls or uninstall. Manage Android backups, exported files, original camera photos, cloud files, and copies shared with others separately. Deletion in RecipeCatalog does not delete a recipe from its original website or erase copies already processed by another service. A full backup restore replaces current app data after confirmation; old recipe-only JSON and CSV imports merge recipe records.

We retain support correspondence only as reasonably needed to resolve requests, maintain useful support records, and meet legal obligations. You can request access, correction, or deletion of personal information we hold by emailing us. We may need to verify the request, and applicable legal exceptions may apply. We cannot directly access or erase a recipe database held only on your device. You may also have rights to object, restrict processing, obtain a portable copy, or complain to a relevant privacy authority, depending on where you live. We will honor rights required by applicable law.

9. Security, international processing, and children

We use the app’s Android private-storage facilities and take reasonable care with information sent to us. No device, network, export, or backup system is completely secure. Use a device lock, keep software current, and protect exported files. Do not treat the app as a secure vault for sensitive health or other confidential records.

Zajabuk is based in the United States. Google, Hugging Face, source websites, and storage or support providers may process information in other countries under their own policies and applicable safeguards. RecipeCatalog is not directed to children under 13. We do not knowingly collect their personal information through app support; contact us if you believe a child has sent us such information.

10. Policy changes and contact

We will revise the effective date when this policy changes and provide appropriate notice of material changes. If a future feature introduces materially different data handling, we will explain it and obtain consent where required before that processing occurs.

Contact Zajabuk at contact@zajabuk.com for privacy questions or requests.

← Return to RecipeCatalog · Terms of Service