Privacy Policy

Summary

MyRecipe is designed with privacy in mind. Your recipes are stored locally on your device by default. If you enable cloud sync, your data is stored securely in Google Firebase and is never sold to third parties. We use third-party services to provide features like recipe import and AI generation — this policy explains exactly what data is processed and by whom.

Legal basis for processing

We process your data on the following legal grounds under GDPR:

• Contract performance: Processing necessary to provide the App's core features (recipe storage, import, cloud sync).
• Legitimate interest: Rate limiting and aggregate usage data to maintain service quality and prevent abuse.
• Consent: Optional features such as voice dictation and AI recipe generation, which you actively choose to use.

Authentication

When you first open the app, a Firebase anonymous account is created automatically. This generates a unique user ID but does not collect any personal information.

You may optionally sign in with Apple to enable cloud sync and backup. When you do, we store your Apple-provided identifier to link your account. We do not receive your name or email address unless you choose to share them through Apple's sign-in flow.

Data stored on your device

The following data is stored locally on your device:

• Your saved recipes (title, ingredients, instructions, images)
• Categories, favorites, and meal plans
• AI chat history (up to 50 conversations)
• User profile and preferences (name, theme, appearance)
• Authentication token for the Share Extension

Data stored in the cloud

If you enable cloud sync (requires Sign in with Apple and a premium subscription), the following is stored in Google Firebase:

• Your user profile (name, preferences)
• Your recipes and categories
• Recipe images and thumbnails

We also store limited usage data in Firebase to operate the service:

• Aggregate recipe save counts (which recipes are popular — no personal data attached)
• Daily voice dictation usage per device (for rate limiting only)

Recipe import

When you import a recipe, the URL or content you share is sent to our cloud services for processing. Depending on the source, the following third-party services may be used:

• Instagram, TikTok, Pinterest: Post URLs are sent to a third-party service to retrieve publicly available post content such as captions and thumbnails. We do not access your social media accounts.
• Websites: The recipe URL is fetched by our servers to extract recipe content.
• AI processing: Extracted content (text, captions, or page HTML) is sent to AI services provided by Google to parse it into a structured recipe. This may include estimating nutritional values.

Imported content is processed in real-time and is not permanently stored on our servers beyond what is saved to your recipe collection.

OCR and photo scanning

When you photograph a recipe, the text is extracted on your device using Apple's built-in Vision framework. The extracted text may then be sent to AI services provided by Google via our cloud functions to parse it into a structured recipe. The original photo is not uploaded — only the recognized text.

Voice dictation

If you use voice input to dictate a recipe, the audio recording (up to 60 seconds) is sent to a speech-to-text service provided by OpenAI for transcription. A device identifier and the audio duration are also sent for rate limiting purposes. Audio is processed in real-time and is not stored by us. OpenAI's data handling is governed by their privacy policy.

AI recipe generation

When you ask the AI to create a recipe, your message is sent to AI services provided by Google to generate the recipe. The AI may also suggest image search keywords, which are then used to find photos via a stock photo service. Only the search keywords are sent — no personal data.

Your AI chat conversations are stored locally on your device and are not sent to our servers (only individual messages are sent for AI processing when you send them).

Subscriptions

Subscription payments are processed by Apple. We use RevenueCat to manage subscription status and entitlements. RevenueCat receives your Firebase user ID to track your subscription. We do not have access to your payment details. RevenueCat's data handling is governed by their privacy policy.

Recipe sharing

If you choose to share a recipe, it is uploaded to our servers and made accessible via a unique link. Anyone with the link can view the shared recipe. Shared recipes may include the recipe title, ingredients, instructions, and image. No personal information about you is attached to the shared recipe.

International data transfers

Some of the third-party services we use (Google, OpenAI) may process data on servers located outside the European Economic Area (EEA), including the United States. These providers maintain appropriate data protection safeguards in accordance with applicable regulations. By using features that rely on these services (recipe import, AI generation, voice dictation), your data may be transferred to and processed in these countries.

Data retention

Local data remains on your device until you delete the app or the data within it. Cloud-synced data is retained as long as your account is active. If you delete your account, all associated cloud data is deleted. Aggregate usage data (recipe popularity, voice quotas) is retained indefinitely but contains no personal information. Shared recipes remain accessible via their link until you request removal.

Analytics and tracking

We do not use any user analytics or tracking SDKs (such as Google Analytics, Mixpanel, or similar). We do not track which screens you visit, how often you use the app, or your behavior within the app. The only usage data we collect is aggregate recipe popularity (save counts with no user association) and voice dictation quotas (per device, not per user).

Your rights and data deletion

Local data: Deleting the app removes all locally stored recipes, chat history, and preferences from your device.

Cloud data: If you have enabled cloud sync, you can request deletion of your cloud data by contacting us. We will delete your Firebase account, stored recipes, and all associated data.

To request data deletion, contact us at henrik@myrecipeai.net.

Children's privacy

MyRecipe is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us so we can delete it.

Who we are

MyRecipe is developed and operated by Henrik Wirak Onsrud, an independent developer based in Norway ("we", "us", "our"). We are responsible for the processing of personal data through the App.

Changes to this policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated date.

Contact

Have questions about privacy? Contact us at henrik@myrecipeai.net