Privacy Policy – Recipe Collector

Overview

Recipe Collector helps you save, organize, back up, and share recipes. This policy explains what data we collect, how we use it, and the choices you have.

What data we collect

• Account identifiers: We use Firebase Authentication. We store a unique user ID (UID). If you sign in with Google/Apple, those providers may also provide basic account details depending on your settings (for example, name/email).
• Recipe content you provide: Recipe text, recipe URLs, and recipe images you upload for parsing/normalization.
• App data stored on your device: Recipes are stored locally on your device using SQLite for offline use.
• Cloud backup data (if enabled): If you enable backup, we store recipe JSON on our servers under your UID. (Images are not included in backup by design.)
• Shared link data: If you create a share link, we generate a token and store which recipe keys are included in that link, so recipients can import them.
• Subscription status: Subscriptions are managed by the app store on your device. We do not store entitlement records on our servers.
• Advertising data (if ads are shown): We use Google AdMob / Google Mobile Ads SDK. Ad providers may collect device identifiers and ad interaction data to provide and measure ads.

How we use your data

• To authenticate you and keep your recipes associated with your account (UID).
• To store and display your recipes locally on your device.
• To back up and restore recipes if you enable cloud backup.
• To create share links and allow recipients to import the shared recipes.
• To normalize recipes you import (text/URL/images) into structured recipe data.
• To display premium features based on the device’s store subscription status (if applicable).
• To show ads to non-subscribed users (if applicable).

AI processing (recipe normalization)

When you import recipes from text, URLs, or images, our backend may send the content you provide to an AI service (e.g., OpenAI) to extract structured recipe information. This processing is used to return normalized recipe JSON.

When we share your data

• With service providers: We use Firebase Authentication. We may use hosting providers to run our backend.
• With AI providers: Recipe content you submit for normalization may be sent to an AI provider to generate structured recipe data.
• With advertising partners: If ads are enabled, AdMob/Google Mobile Ads SDK may collect and process data for ad delivery and measurement.
• When you share recipes: If you create a share link, anyone with the link can view the list of recipes in the link and import them into the app.

Your choices

• Backup: You can choose whether to enable cloud backup (if the app offers a toggle).
• Delete recipes: You can delete recipes from your device. If cloud backup is enabled, deleted items may be marked deleted in backup during sync.
• Ads: Your device may allow resetting or limiting ad identifiers and ad personalization in system settings.

Data retention

We retain cloud-backed recipe data for as long as your account remains active or until you delete your content. Shared link tokens may expire.

Security

We use reasonable security measures to protect your data. No system is 100% secure.

Children

Recipe Collector is not directed to children under 13 (or the minimum age required in your region).

Contact

Email: emc2qwe@gmail.com