Chef Engine

Chef Engine · Help & legal

App privacy policy

Updated 20 October 2026

This policy covers the rebuilt Chef Engine app, including weekly planning, shopping, recipes and guided cooking. The website and waitlist have a separate website privacy notice.

Who is responsible

Chef Engine is operated by Maksim Sigov, Zittelstraße 3, 80796 München-Schwabing-West, Germany. Contact slinex.company@gmail.com for privacy questions and requests.

Information used to provide the app

Privacy choices

You can change meal preferences, language, measurements and reminders in My setup or Your account. In permission-based app versions, open Your account → Privacy and data → Privacy choices to allow or stop analytics and manage allergy personalization and AI sharing. Earlier versions call the analytics setting Usage sharing. This does not affect access to your subscription. For access, correction, deletion, restriction or portability requests, email slinex.company@gmail.com. You can also use our account and specific-data deletion instructions.

Usage analytics and your choice

In current testing builds, optional usage analytics is on by default unless you previously turned it off. A disclosure in onboarding links to Learn more, where you can disable it. Account → Privacy and data → Usage sharing or Privacy choices also provides a turn-off control. All app features remain available when analytics is off. Older permission-based builds waited for Allow analytics; later default-on builds do not treat the default as an affirmative consent receipt. Existing refusals are preserved after upgrading. PostHog receives a random app analytics identifier, screen and feature events, onboarding progress, purchase and restoration outcomes, generation outcomes, bounded operation timings, platform, app version, build number and language. These events support installation-level funnels and reliability analysis, not cross-device account tracking. We do not collect birth dates or send age answers to PostHog.

We do not send your name, email, account identifier, food preferences, allergy selections, ingredient names, search terms, recipe text, photos, authentication tokens or payment details to PostHog. Automatic tap capture, session replay, person profiles and IP-based location enrichment are disabled. Events use the EU PostHog ingestion endpoint. Turning sharing off stops new tracking and discards queued analytics on the device. Signing out resets the random analytics identity.

AI processing

The permission-based app separately asks for permission before sending content for AI processing. Chef Engine identifies OpenAI as the recipient and explains that requests may include your recipe brief, selected photos, notes, reviewed ingredients and relevant food and kitchen preferences. Relevant allergen restrictions are shared only if you also permit allergy personalization. The account-scoped choice is remembered for future recipe ideas, dish recreation, recipe scans and AI planning; it can be withdrawn in Privacy choices. Without AI sharing you can still use saved recipes, manual recipe entry and cooking. A selected photo or draft is retained when you decline; camera or photo-library permission alone is not AI-sharing permission. Withdrawal stops new provider submissions; requests already submitted cannot be recalled.

App account identifiers, email addresses and authentication credentials are excluded from recipe-generation prompts. Anything voluntarily written in a brief or note, or included in a selected image, can be part of the request; avoid unrelated personal information and photos of people or documents that are not needed. API data is not used for OpenAI training by default, and recipe requests disable API response storage. This does not disable all retention: default abuse-monitoring logs may be kept for up to 30 days, subject to legal and safety exceptions. We do not claim zero-retention AI processing. See OpenAI’s API data controls. Saved cooking photos are not sent for recipe generation. Scan recipe and Recreate dish send the selected image for the requested interpretation; a dish photo cannot establish hidden ingredients or allergens, so ingredient review remains necessary. Human-reviewed catalog recipes are prepared separately from private user recipes.

Why and where information is processed

We use account and app data to deliver the service you request, manage purchases, protect the service and answer support requests. Where you expressly allow analytics, the recorded permission relies on your consent under Article 6(1)(a) GDPR, together with permission for associated device storage/access where required. You can withdraw without losing app features. Default-on operation is not evidence of consent; any prior-permission requirement and the applicable basis for default-on operation require separate assessment before public launch. This notice does not establish an exemption from those requirements. This is separate from the processing needed to fulfil your meal-planning and purchase requests. Necessary account, saved-content and purchase processing supports performance of the service contract under Article 6(1)(b) GDPR. Fraud prevention and essential service security are assessed under Article 6(1)(f), and records required by law under Article 6(1)(c). These bases do not replace a separate condition required for health data or consent required for access to information on your device. Allergy information can be health data. The permission-based app asks for explicit consent under Articles 6(1)(a) and 9(2)(a) GDPR before saving and using allergy selections for meal filtering and recipe personalization. This permission is separate from analytics and AI sharing. You can use the app without providing allergy information. Withdrawing pauses new allergy-dependent personalization; it never silently relaxes your exclusions. Existing plans remain saved. You may remove current allergy selections in My Setup and request erasure of previous information, including historical copies, through support or account deletion. Removing selections does not make an existing recipe safe for changed requirements; review affected meals. Versioned permission receipts record the purpose, notice version, choice and time so choices can be enforced and demonstrated. Do not provide another person’s health information unless you are authorised to do so. This notice describes processing; reading or accepting it is not a substitute for any separate permission required by law.

Providers include Google/Firebase for authentication, database, storage, attestation and push delivery; RevenueCat for verifying store purchases; Apple and Google for store payments and sign-in; OpenAI for recipe generation; and PostHog for usage analytics. App database and storage resources are configured in Europe. Provider systems and support processing may involve other countries. Apple and Google also act under their own privacy terms for store accounts, payments and platform services. Transfers outside the European Economic Area require an applicable mechanism, such as an adequacy decision or standard contractual clauses with the necessary safeguards. Contact us for information about relevant recipients, processing locations and copies of applicable transfer safeguards. We do not sell your personal information or use it for advertising profiles.

Device storage and backups

Offline recipes, images, pending edits and retained photo drafts are stored in the app’s private, account-scoped storage. Signing out or deleting the account clears that account’s local content. Newer testing builds exclude this device-local content from Android cloud backup and device transfer and mark the iOS storage directory as excluded from backup. Pending work remains on this device; clearing or uninstalling the app can remove work not yet synchronized. Apple’s exclusion is guidance to the operating system, not a guarantee about every backup. These settings do not erase earlier backups; manage those through your device or backup provider.

Retention, deletion and your choices

Your account data is kept while needed to provide the service, until you request deletion or it is otherwise removed. Deletion is processed as a queued backend operation covering app account records, preferences, plans, private recipes and media. Default production service logs have a 30-day retention period. Separately required audit records and information needed for a documented security incident, purchase administration or legal obligation may have a different retention period; we explain the relevant reason when handling a request. Database backups expire after 14 days. Deleted media recovery copies expire seven days after object deletion. Account-export files have a seven-day storage lifecycle; deleted-file recovery can continue for a further seven days. These periods are separate from removal from active service and do not apply to Apple’s or Google’s purchase records. A restricted deletion marker containing the account identifier, deletion time and reason prevents deleted accounts from returning when a backup is restored.

Usage analytics is separate from app content and uses a random identity. Turning it off does not retrospectively remove events already delivered. Contact us for an analytics deletion request; Privacy choices (Usage sharing in earlier versions) shows the analytics reference for your device when available. Aggregate statistics that no longer identify a person may be retained.

Deleting the app account is not a request to cancel store billing, and does not automatically erase every record independently held by a payment provider. For a request covering provider-held records, tell us the scope so we can verify ownership and coordinate it with the relevant provider, including RevenueCat where applicable. We explain any legally justified retention rather than treating all purchase records as exempt from erasure.

You can request access, correction, erasure, restriction or portability, object where applicable, and withdraw optional consent without affecting the lawfulness of earlier processing. Contact us using the address above. We respond without undue delay, normally within one month. Where the law permits an extension for a complex or numerous request, we explain the reason within that initial month. Identity checks are proportionate; do not send passwords, authentication codes or payment-card details. You may complain to the Bavarian data-protection authority for the private sector or another competent supervisory authority.

See account deletion for the in-app and website request paths. Deleting an app account does not cancel a store subscription; cancel it separately with Apple or Google. The rebuilt service does not import older app accounts, saved recipes or preferences.

Children and changes

Accounts are available only to people aged 16 or older; users aged 16 or 17 also need a parent or guardian’s permission. The app does not collect a birth date or display an age-confirmation screen. Adults can plan meals for their household without creating a child account. If a child has supplied personal information without the required permission, contact us. We update this page when practices change and communicate material changes where required.