Last updated: October 12, 2026
This Privacy Policy explains how FUNGEE LLC ("we," "us," "our," or "FUNGEE LLC") collects, uses, shares, retains, and deletes information when you use the IngrediCheck website (the "Site"), mobile applications (the "App"), and companion browser extension (the "Extension"), together the "Services".
We collect personal information only when it is needed to operate, secure, support, and improve the Services, or when you choose to provide it. We do not sell your personal information.
We use Supabase for authentication, database, storage, and backend services. Depending on how you use the Services, we may collect a Supabase user ID, guest or anonymous session identifiers, authentication metadata, email address, and information returned by Google Sign-In or Sign in with Apple. Google and Apple process sign-in information under their own privacy policies.
IngrediCheck evaluates grocery products against the food preferences you choose to provide. We may collect family profiles, member names, avatar choices, generated avatar references, food notes, allergies, intolerances, dietary restrictions, health-related food concerns, lifestyle preferences, ethical preferences, taste preferences, regional preferences, and invite or family-sharing information.
When you scan, search for, or submit product information, we may process barcodes, product names, ingredients, nutrition facts, allergen statements, package photos, source URLs, product database matches, analysis results, favorites, feedback, votes, comments, and scan history. Camera access is used to scan barcodes and capture product or package photos you choose to submit.
The Extension is a companion to the mobile App. Sign in to the App with Google or Apple, then use the same sign-in method and account in the Extension to access your family's saved food notes. When you open the Extension on a product page, it reads relevant page content, including the page URL and title, product metadata, ingredient and nutrition text, image references, and linked nutrition content where available. It sends this information to IngrediCheck's backend and AI services to analyze the product against your food notes and provide a result. Product URLs and results may be saved in your account's scan history. The Extension does not automatically analyze every page you visit or collect your complete browsing history.
The Extension stores your authentication session, account information, family food notes, recent and favorite products, cached analysis references, and first-run preference in local browser storage. Cached analysis references expire after seven days. We use PostHog for Extension analysis events, including the result status, retailer domain, error message when applicable, browser and operating system information, and an identifier associated with your signed-in account or a generated anonymous identifier. The Extension does not use session replay or record your keystrokes. Uninstalling the Extension removes its local browser storage; it does not delete account data held by IngrediCheck. Use the account deletion options below to request deletion of account data.
If you use IngrediCheck chat features, we may process and store your messages, conversation context, assistant responses, uploaded chat images, and related conversation metadata so the chat can answer questions and maintain conversation history.
We may collect app-generated or platform-derived device identifiers, platform, operating system version, app version, build number, timezone, locale, preferred language, store country, notification permission status, push notification subscription identifiers, network request metadata, IP address, error logs, diagnostics, and security events. We use OneSignal to help deliver push notifications.
We use PostHog in our mobile apps to understand app usage, diagnose bugs, measure feature performance, and improve reliability. PostHog may collect app events, screen and lifecycle events, device and session metadata, diagnostic logs, network telemetry, screenshots, and session replay data. Session replay may capture app screens, images displayed in the app, and text entered into app fields. We also use PostHog on our website to understand landing-page traffic, referral sources, and how visitors move toward downloading the app; on the website PostHog receives page URLs, referring URL, browser, device type, coarse geographic location derived from IP address, an anonymous per-visitor identifier, campaign attribution parameters when present in the URL (such as utm_source, utm_medium, utm_campaign, fbclid, and gclid), and a limited set of specific interaction events including clicks on our App Store and Google Play download buttons, clicks on ingredient-checker guide links, and clicks on selected in-article links; the website integration does not capture form input, keystrokes, or session replay. We use Vercel Analytics and Vercel Speed Insights on our website to understand traffic and performance. Apple and Google may provide app store analytics, diagnostics, and review-related information.
We use Google Ads conversion tracking to measure whether visitors click our app download buttons after interacting with an ad. Google may use cookies and similar identifiers for this measurement. Learn more about how Google uses information from sites that use its services.
We do not load this advertising measurement tag when your browser sends a Global Privacy Control signal.
We use Google Analytics for Firebase in our Android app to measure app acquisition, onboarding completion, trial starts, and lifetime purchases and to understand which Google Ads campaigns lead to app usage and purchases. Google may process app-instance and advertising identifiers, app and operating system information, session and engagement events, and approximate location information. Our onboarding, trial-start, and lifetime-purchase measurement events do not include names, email addresses, Supabase account IDs, store order IDs, purchase tokens, allergy or dietary selections, food profiles, scan contents, or chat messages. Trial and lifetime events can include the verified purchase value and currency. We use verified RevenueCat transaction information in our backend to prevent duplicate or unverified purchase events. We do not enable advertising personalization for this integration. We use a request to our website to determine an approximate country from your IP address before enabling this measurement. This Firebase Analytics integration remains disabled for users identified as being in the United Kingdom, European Economic Area or Switzerland, and when we cannot determine a country. This notice itself does not constitute consent. Learn more about how Google uses information from apps that use its services.
We use AppsFlyer to measure which organic sources and ads lead to app installs, onboarding, and purchases. When this measurement is enabled, AppsFlyer may receive an app installation identifier, app launch and onboarding events, device and app information, IP address (which can indicate approximate location), and attribution information such as a campaign or referral source. The native AppsFlyer SDKs do not receive our app account ID. On eligible Android sessions outside the restricted regions described above, AppsFlyer may collect the Google Advertising ID when the device makes it available; RevenueCat also receives that identifier to help attribute verified subscription events. Deleted advertising IDs and device tracking opt-outs are respected. Advertising-ID collection remains disabled when regional eligibility is unknown or restricted. RevenueCat purchase events include the App User ID associated with the purchase. On iOS, we do not request Apple's App Tracking Transparency permission for this integration. The iOS SDK disables advertising-identifier and IDFV collection, does not set an app account ID, and applies a filter intended to block user-level sharing with connected ad partners.
RevenueCat sends verified purchase and subscription events to AppsFlyer for eligible customers, including product, purchase status, time, price, and currency. This can include renewals while the app is closed. For iOS, AppsFlyer’s app-level Aggregated Advanced Privacy setting restricts partner attribution data to aggregate, anonymous reporting, while native SDK partner sharing remains blocked. Apple’s SKAdNetwork and AdAttributionKit provide privacy-preserving campaign measurement without a tracking-permission prompt. We do not use an iOS customer-wide RevenueCat filter to block eligible Android subscription measurement. The customer's AppsFlyer installation identifier can still change when they use another device or platform. Campaign measurement without Tracking permission relies on available aggregate attribution methods. Eligible Android attribution and conversion data may be shared with connected ad networks for campaign measurement and optimization. We do not send food profiles, allergies, scan contents, chat messages, names, or email addresses to AppsFlyer through this integration.
IngrediCheck offers a one-time 24-hour Day Pass, Monthly subscriptions with trials where available, and one-time Lifetime access. Purchases are processed by the applicable app store, such as Apple App Store or Google Play. We use RevenueCat to manage purchases and access to paid features. We do not receive or store your full payment card details. RevenueCat and our backend process account identifiers, transaction identifiers, product information, purchase timestamps, amounts, currency, and purchase-status information to confirm transactions, provide access and support, prevent duplicate processing, and support the advertising measurement described above.
If you contact us, request account deletion, or send feedback, we collect the information you include in that request. Our website may store newsletter form submissions in your browser's local storage and may open your email client so you can send messages directly to us.
We use the information we collect to operate and secure the Services, create and maintain accounts, authenticate users, sync data across devices, manage family profiles, personalize product and ingredient analysis, provide scan and chat history, process images and product information, deliver push notifications, respond to support requests, troubleshoot bugs, detect abuse, analyze usage, improve product quality and AI accuracy, maintain product databases, enforce our terms, and comply with legal obligations.
We may disclose your information in response to subpoenas, court orders, or other legal requirements; to exercise our legal rights or defend against legal claims; to investigate, prevent, or take action regarding illegal activities, suspected fraud or abuse, violations of our policies; or to protect our rights and property.
In the future, we may sell to, buy, merge with, or partner with other businesses. In such transactions, user information may be among the transferred assets.
We share information with service providers that help us run the Services, including Supabase for authentication, database, storage, and edge functions; Fly.io and related cloud infrastructure for backend services; OneSignal for push notifications; PostHog for analytics and session replay; Vercel for website hosting, analytics, and speed insights; Google for advertising measurement as described above; AppsFlyer for mobile attribution and purchase-conversion measurement; RevenueCat for purchase and subscription management; Apple and Google for sign-in, app distribution, app review, app store analytics, and purchases where applicable; and product data providers such as OpenFoodFacts or our hosted product inventory. AppsFlyer may also pass eligible Android attribution and conversion data to connected advertising partners as described above.
IngrediCheck uses AI systems to analyze ingredient lists, product information, product images, chat messages, and user-provided food preferences. Information you submit for analysis may be processed by our AI infrastructure and third-party AI or inference providers, which may include Anthropic, OpenAI, Google Gemini, Groq, Cerebras, and other providers configured for a particular feature. These providers process information to return model outputs, maintain service security and reliability, and comply with their legal obligations.
We retain account-linked app data while your account is active or as needed to provide the Services. After you delete your account or submit a verified deletion request, we remove or de-identify account-linked records from active systems within 30 days, unless we need to keep limited information for legal, tax, accounting, fraud prevention, security, dispute resolution, or support reasons. Backup copies may persist until they are overwritten or expire in the ordinary course of business, generally within 90 days.
Operational logs, diagnostics, analytics, crash data, and security records are retained only as long as reasonably needed for reliability, security, debugging, product improvement, or legal compliance. Support emails and privacy requests are retained as long as needed to respond to the request and maintain a record of our response. De-identified, aggregated, or non-identifying product information, model outputs, analytics, and product database contributions may be retained after account deletion.
You can request deletion in the app by opening Settings, choosing Delete Data & Account, and confirming the deletion prompt. The app sends a deletion request to our backend and signs you out. If you are using the app without a signed-in account, you can use Reset App State to clear local app data from your device; resetting local app state does not delete server data linked to a signed-in account.
You can also request deletion at ingredicheck.app/delete-account or by emailing owner@ingredicheck.app. To help us verify and process the request, include the email address or sign-in provider associated with the account, or enough information to identify the account or app session.
When deletion is completed, we delete or de-identify account identifiers, food profile records, family member records tied to your user, scans, uploaded scan images, chat conversations, uploaded chat images, feedback, device-user login links, and push notification links associated with your account, subject to the retention exceptions described above. Deletion may not remove product facts, de-identified product database entries, aggregate analytics, support correspondence, app store transaction records, security records, or legal records that no longer identify you or that we must retain.
You can update or remove food preferences in the app, delete scans and local app data where the app provides those controls, turn off camera or notification permissions in your device settings, unsubscribe from or disable push notifications, sign out of your account, or request account deletion. You can also contact us for help with privacy requests.
We use reasonable administrative, technical, and organizational measures to protect information, including access controls, authentication, and cloud security controls. However, no system is completely secure, and we cannot guarantee absolute security.
Information may be processed, stored, and used outside of the country in which you are located. Data privacy laws vary across jurisdictions, and different laws may be applicable to your data depending on where it is processed, stored, or used.
The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Our website and apps may use local storage, secure storage, browser storage, session storage, or similar technologies to operate the Services, remember preferences, maintain sessions, cache content, store local app state, and understand performance. OAuth providers such as Google and Apple may use cookies or browser storage during sign-in.
If you have questions about this Privacy Policy or want to make a privacy request, contact us at owner@ingredicheck.app.
From time to time, we may change and/or update this Privacy Policy. Changes will be posted on this page with an updated date. If changes are material, we may provide additional notice where required.