Privacy

Privacy practices for Ingredient Check on Chrome and Firefox. Detailed feature disclosures are in the full extension privacy policy.

The short version

• Scoring runs on your computer. Scores, settings and product labels are stored locally. Browser backup and optional Google features can also store the data described below.
• The extension does not sell data, show ads, or use analytics or tracking.
• Automatic rating, local OCR and certification-table lookups are enabled by default. Browser settings backup is enabled by default, subject to browser sync and permissions. Purchase history, Google sign-in, diagnostics and product sharing require your choices.
• This website has no analytics scripts and sets no cookies.

What the extension reads

On supported public retailer product and search pages it reads product titles, ingredients, nutrition, product IDs, certifications and prices needed for ratings and sorting. Cart rating reads identifiable product links and titles; it does not collect cart quantities, prices, totals, payment details or addresses. On narrowly scoped Amazon.com Orders pages it reads identifiable items to show scores. Saving purchase records and account sync remain separate opt-in choices.

What stays on your device

Your weights, goals, allergen and diet flags, avoid list, preferences and cached scores are kept in local extension storage. Product labels are kept for 30 days by default (adjustable from 1 to 90 days). Clear cached scores in the popup removes score and product caches. Optional purchase records are stored separately and have their own export and deletion controls. The sorted list and its current priorities live in session memory and are cleared when the browser closes. Saved shopping lists are separate from caches and purchase history, stay local, and can be removed from Saved products. Local photo checks do not upload or retain images.

Features that contact other services

• Automatic product lookups. Enabled by default. Amazon search lookups use your Amazon sign-in cookies. Retailer-preview lookups omit cookies; cart lookups on all supported stores also omit referrers. Amazon carts reuse saved public labels and can use the enabled barcode/local-photo readers below when a published text label is missing or unreadable. Cart readings are not shared. Retailers still receive normal connection information, such as your IP address.
• Local label OCR. Enabled by default on supported Amazon labels. It fetches public label images and processes them on your device; it does not send the image to an OCR service.
• Barcode lookup (Open Food Facts). Recommended in setup but requires permission. A product barcode is sent to Open Food Facts to find a missing label.
• Certification tables. Enabled by default. The extension requests owner-maintained certification tables from the Ingredient Check Google Apps Script backend. These table requests do not identify the products you view.
• Browser settings backup. Enabled by default. Your browser can sync weights, goals, allergen and diet choices, avoid list and preferences to your own browser account when profile sync and required permissions are enabled. Firefox also requires its optional data-sharing consent. Backup can be disabled in Settings.
• Google sign-in and settings sync. Sign-in requests openid email profile. Your name, email and Google picture URL are stored locally to show the account; the picture loads from Google's image host. Tokens stay in memory. Settings save/restore sends your preferences to the configured private Apps Script backend, keyed by a hash of the verified account ID. Automatic saving can be disabled. Signing out clears the local Google profile.
• Purchase history. Saving is off until enabled. Item scores can display without saving purchases; automatic missing-label lookups omit cookies and referrers. The compact graph and available daily/weekly/monthly averages use saved rated purchases. Setup's history choice enables automatic Google sync, which can be switched off independently. The reader imports Amazon order items; an explicit full-history scan visits available older order pages and pauses on verification challenges. Records can include product IDs and names, dates, purchase status, scores, ingredients, nutrition, warning matches, score breakdowns and hashed order groups. These records stay local or sync to the configured private backend. Addresses, payment details, prices and raw order numbers are not stored or uploaded. Only actual purchases drive trends.
• Shared product readings and diagnostics. Off by default. Product sharing can send product IDs and public label data to the configured shared backend. Opt-in diagnostic and contribution uploads are described in the diagnostics policy. They are separate from private purchase history.

Reports and store requests

The Report a problem or idea form sends nothing from the extension. You see everything it would include, and you choose whether to download a report file or open an email draft yourself. A screenshot is taken only when you click the toolbar button on an Amazon or retailer tab.

The Request a store form builds an email draft in your own email app. Nothing is sent until you press Send.

What the extension does not do

• It does not read your browsing history beyond the supported retailer pages.
• It does not sell your data or use advertising trackers. The network features above have their own controls and disclosures.
• It does not change quantities, prices, totals or checkout controls on carts.

Your controls and retention

Use Settings to disable automatic rating, certification lookups, backups or sharing. Clear cached scores in the popup; export or delete purchase records in Purchase history. Account deletion requires confirmation and remains visibly pending if it fails. Clearing local data does not delete an account backup. The configured backend owner operates the private spreadsheet that stores enabled Google backups and purchase records.

This website

The site uses static HTML and CSS, with no analytics scripts or application cookies. When hosted on Vercel, Vercel may process ordinary request metadata for hosting and security; see Vercel's privacy policy. External GitHub and email links open the services you choose to use.

Contact

Questions about privacy: jackson29382938@gmail.com.

Last updated October 9, 2026.