Oui Chef sends information to the AI service providers identified below. Review what each receives and how it is used before allowing AI processing.
Google — Gemini API
Google receives cooking messages and conversation history, ingredients, dietary preferences, Custom instructions, selected Dish Ideas, and recipe links and their recipe content through its Gemini API to suggest meals, create guided recipes, and generate Dish Idea images. Google also processes saved recipe content for legacy search attributes. On the web, submitted dinner voice recordings are sent for transcription and ingredient photos for interpretation.
Oui Chef uses the paid Gemini API. Google's paid-service terms exclude prompts and responses from model training and product improvement. They permit temporary logging for abuse prevention and legal disclosures. Processing is governed by Google's Data Processing Addendum, which includes security, confidentiality, restricted access, and subprocessor obligations. Processing may occur wherever Google or its agents maintain facilities.
OpenRouter — Inception and Qwen models
OpenRouter receives the search text you submit and routes it to Inception Mercury 3 for interpretation, with one Qwen3.8 Flash fallback if needed. Interpreted requirements and preferences and compact indexed recipe facts are sent through OpenRouter to Inception Mercury Decide to judge relevance. Preparation steps are excluded from those judgments. OpenRouter and its Qwen embedding providers also receive search text and saved recipe content to create semantic representations for search.
OpenRouter's Privacy Policy states that OpenRouter does not train models on inputs or outputs. Downstream model providers have separate data-use and retention terms; Google's paid-service commitments do not apply to these requests. See OpenRouter's provider information for provider-specific policies.
OpenRouter's Data Processing Agreement includes confidentiality, security, and subprocessor obligations. Section 5.1 requires written subprocessor agreements with data-protection obligations no less protective than OpenRouter's agreement, as applicable to the services they provide.
Background indexing and public discovery
Saved-recipe indexing runs automatically on the server, independently of whether the app is open or native AI permission is enabled. Private recipe ratings, notes, conversations, and Custom instructions are excluded from recipe indexes and public recipes. Saved Custom instructions are not added to OpenRouter search requests; they are used for cooking requests to Google’s Gemini API. Generated Recipes are public by default; imported third-party recipes and saved shared copies remain outside the public catalogue.
iPhone/iPad permission and device features
Before sending AI requests from the iPhone/iPad app, we identify the recipients and information shared and ask for your explicit permission. Hands Free camera frames stay on your device. Native dictation uses Apple speech recognition, preferring on-device processing when supported; otherwise Apple may process the audio. Dictated text is included when you submit it in an AI request, and dictated Custom instructions you save may be included in later cooking requests to Google’s Gemini API.
We will keep this list current when our providers change. A change to the disclosed AI recipients or data uses requires the native app to request permission again before sending further AI requests.
Read the Privacy Policy and Terms of Use. You can decline permission or withdraw it in Settings → Privacy → Withdraw AI permission to stop future AI requests from that device; requests already sent cannot be recalled. Existing recipes remain available. Automatic saved-recipe indexing continues as platform maintenance.
← Back to Oui Chef