Privacy Policy

This Privacy Policy explains how Cook EZ ("Cook EZ," "we," "us," or "our"), the operator of cookezapp.com and the Cook EZ mobile apps, collects, uses, shares, and protects personal information when you use our website, iOS app, Android app, and related services (together, the "Service").

By creating an account or using the Service, you acknowledge this Policy. If you do not agree, please do not use Cook EZ.

Questions: admin@umratech.com.

We collect information you provide, information created when you use Cook EZ, and limited technical data needed to run the Service.

• Account data: name, email address, profile image URL, and sign-in identifiers from Clerk (Apple, Google, or email one-time code).
• Taste and diet: eating patterns, allergies, dislikes, cuisines, skill, equipment, and optional custom cooking instructions.
• Food photos: plate and ingredient photos you capture or share, plus width, height, and file size.
• Recipes and cooking: generated and saved recipes, steps, ratings, notes, collections, shopping lists, and pantry items.
• Nutrition and health metrics: optional sex, birth year, height, weight, activity, calorie and macro targets, meals you log (items, portions, calories, macros, meal slot, notes), daily totals, and water.
• Apple Health / Health Connect: meals, water, and (if you consent) weight or active energy, only when you turn sync on.
• Open Food Facts lookups: barcode/search queries needed to fetch product nutrition (we store the result you log, not a live feed of the Open Food Facts database).
• Subscription & credits: RevenueCat app user id, entitlement status, plan, store, credit balance, and ledger entries.
• Device & notifications: push token if you opt in; UI language, content language, units, appearance, and local preference flags.
• Support: messages you send to admin@umratech.com.
• Technical logs: server logs and security/rate-limit signals.

We do not receive or store your full payment card number or bank account details. Apple App Store, Google Play, and RevenueCat process payments.

We do not sell your personal information and we do not use your content, food photos, or health metrics to train our own AI models.

We do not require advertising identifiers for targeted ads, we do not use IDFA/ATT, and we do not use third-party advertising SDKs for ad targeting. Health and fitness data is never used for tracking.

We use personal information to:

• Create and secure your account and authenticate you via Clerk.
• Generate, store, and personalize recipes from your photos, text, and taste profile.
• Estimate calories and macros, keep your food diary, and power widgets.
• Sync optional health samples you enable with Apple Health or Health Connect.
• Meter credits, enforce plan limits, and sync subscription status from RevenueCat / the app stores.
• Send transactional or product notices you request (for example cook and meal reminders).
• Provide customer support and investigate abuse, fraud, or security incidents.
• Improve reliability and product quality using aggregated or de-identified signals where practical, unless you opt out of analytics.
• Comply with law and enforce our Terms of Service.

To generate recipes, step photos, dish identification, and calorie estimates, we send relevant parts of your request to OpenAI's API from our servers (Convex). This may include food photos, a dish name, taste-profile constraints, and locale.

OpenAI processes that data as our processor under OpenAI's API terms. Those API terms generally prohibit OpenAI from using API inputs and outputs to train their models. We do not grant OpenAI a right to use your content for training on our behalf.

We also run automated moderation on prompts before generation. AI recipes, photos, and nutrition numbers can be wrong. Cook EZ is not a medical device, does not diagnose or treat any condition, and does not replace advice from a clinician. Always verify ingredient labels if you have allergies.

Purchases are processed by Apple, Google, and RevenueCat. We receive subscription state needed to unlock the Service and allocate credits (for example active/grace/expired, plan, renewal, and period end).

We do not store your card details. Manage, cancel, or request store refunds through your Apple ID or Google Play account settings, subject to those platforms' rules.

Our marketing website may use essential cookies or similar technologies required for security, locale, and basic site operation. We do not run third-party ad pixels for behavioral advertising on the marketing site as of this Policy's date.

The mobile app may record product events (for example onboarding steps, paywall views, capture, and cook) to help us understand funnel performance. Event payloads are designed to exclude dietary restrictions, allergens, health metrics, weight, and photo contents.

You can turn analytics off in Settings → Data & privacy. When opt-out is on, PostHog captures nothing.

You can control push notifications in system settings. Local drafts and preferences stored on your device can be cleared by signing out, deleting the app, or clearing app storage.

We share personal information only with service providers that help us operate Cook EZ, when required by law, or with your direction. We do not sell personal information.

• Clerk: authentication and account profile.
• Convex: database, file storage, backend functions, and webhooks.
• OpenAI: recipe, vision, image generation, and moderation for your requests.
• Open Food Facts: barcode and packaged-food lookups (public ODbL dataset; we send the query needed to fetch a product).
• RevenueCat: subscription entitlements and billing sync.
• Apple / Google: sign-in (if you choose those providers), in-app purchases, and optional Health / Health Connect sync.
• Expo / hosting infrastructure: app delivery, push notifications, and website hosting.
• PostHog: product analytics, unless you opt out.
• Professional advisors or authorities when reasonably necessary for legal compliance, safety, or dispute resolution.
• A buyer or successor if we are involved in a merger, acquisition, or asset sale, subject to continued protection of your information.

We and our processors may process information in the United States and other countries where privacy laws may differ from those in your country. Where required, we rely on appropriate transfer mechanisms and contractual protections with processors.

If you access Cook EZ from the EEA, UK, or Switzerland, we process personal data as a controller for account, billing-state, and product operations described here, and we use processors listed above.

We keep account, recipe, nutrition, photo, credit, and subscription records for as long as your account remains active and as needed to provide the Service.

Failed or stuck generation jobs may be expired and refunded automatically after a short operational window.

After account deletion, we delete or irreversibly de-identify personal content associated with your user record through our deletion process (see Section 14), including food photos and health metrics we stored. Some records may remain for a limited time in encrypted backups, security logs, or payment ledgers held by Apple, Google, or RevenueCat, or where law requires retention.

We use industry-standard safeguards appropriate to a cloud app: encrypted transport (HTTPS), authenticated APIs, server-side secrets (never shipping private API keys in the apps), ownership checks on data access, rate limits, and moderated generation inputs.

No method of transmission or storage is 100% secure. Please use a strong unique password if you set one, protect your device, and contact us immediately at admin@umratech.com if you suspect unauthorized access.

Depending on where you live (including the EEA/UK under GDPR and certain U.S. states such as California under the CCPA/CPRA), you may have rights to:

• Access a copy of personal information we hold about you (including a JSON data export of recipes, logs, journal, preferences, and targets).
• Correct inaccurate information.
• Delete personal information (including by deleting your account in the app).
• Object to or restrict certain processing, including analytics opt-out.
• Data portability for information you provided.
• Opt out of "sale" or "sharing" for cross-context behavioral advertising: we do not sell personal information and do not engage in that advertising practice.
• Lodge a complaint with a supervisory authority.

Email admin@umratech.com with the subject line "Privacy request" and tell us which right you want to exercise. We may need to verify your identity (for example confirming control of the account email).

You can also download your data, update profile details, opt out of analytics, and delete your account in the Cook EZ app under Settings → Data & privacy.

We will respond within the time required by applicable law.

In the Cook EZ app, go to Settings → Data & privacy → Delete account and confirm. We then remove your user record and associated recipes, dishes, meal logs, daily nutrition, collections, shopping lists, pantry items, cook preferences, nutrition targets, journal check-ins, uploads, stored photos, credit ledger/balances, onboarding answers, and subscription rows in our database.

Deletion is irreversible. Purchase history and receipts remain with Apple, Google, and RevenueCat under their policies. Health samples already written to Apple Health or Health Connect remain on those platforms until you delete them there.

If you re-register later, you create a new account. Deletion begins when requested and is processed as quickly as practicable. Large accounts may complete in multiple steps as files and rows are purged.

Cook EZ is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Calorie tracking is blocked for users under 16. If you are 13 to 17, you may use Cook EZ only with permission of a parent or guardian, and only where allowed by the app stores and local law.

If you believe a child under 13 provided personal information, contact admin@umratech.com and we will take appropriate steps to delete it.

Product nutrition for packaged foods may come from Open Food Facts, available under the Open Database Licence (ODbL). Open Food Facts' terms apply to that dataset.

If you share recipe cards to TikTok, Instagram, or other platforms, those platforms' privacy policies govern what happens after you upload there. Cook EZ is not affiliated with TikTok, ByteDance, Instagram, or Meta.

Links on our website to third-party sites are not covered by this Policy.

We may update this Privacy Policy from time to time. We will change the "Last updated" date above and, for material changes, provide additional notice (for example in-app or by email) when required.

Continued use of the Service after an update means you acknowledge the revised Policy.

Privacy questions, requests, or complaints:

Cook EZ Email: admin@umratech.com Web: https://www.cookezapp.com Privacy Policy: https://www.cookezapp.com/en/privacy Terms of Service: https://www.cookezapp.com/en/terms