Privacy
Updated 11 October 2026
A barcode or label detail is used to check published food-safety warnings. You do not need an account.
Who handles your data
Lexio Apps Ltd is responsible for the personal data handled by Eat or Yeet. We are registered in England and Wales, company number 11633419, at The Old Court House, Clark Street, Morecambe, England, LA4 5HR. For privacy questions or requests, email anthony@lexio.app.
Details used for a check
Barcode numbers and any label details you enter are sent to the service to compare against official warning data. Barcode lookups may also use Open Food Facts for product name and brand details. Product metadata does not decide a warning match.
No scan history
Website checks do not require an account or create a history of individual checks. A signed anonymous browser identifier helps enforce rate limits. It does not contain your name or email address.
Optional website and app analytics
Website analytics stays off until you choose Allow analytics. Choosing No analytics does not affect food checks. You can change your choice using Analytics preferences in the footer. In the embedded ChatGPT result app, the choice applies only to the current view and can be changed there. Browser privacy signals, including Do Not Track and Global Privacy Control, keep optional analytics off.
With your consent, we send PostHog the page category, check method, chosen UK or US region and broad result category. The embedded app sends only that its view opened or a tool was requested, the tool name and the host's reported app category. We do not send product details, shopping text, conversations, credentials, names, email addresses, full page URLs or your network address. We do not use automatic click capture, screen recordings or analytics profiles. Every event receives a new random identifier, so these events do not track your activity across pages or visits.
We remember your website choice in a cookie for 180 days. A browser-storage timestamp tells other open tabs when the choice changes; it contains no analytics or user identifier. The embedded app keeps its choice in memory only. Withdrawing consent stops future optional events. It does not erase earlier counts, which we cannot link back to you.
Our basis for optional analytics is your consent. PostHog stores these unlinked usage events in its EU Cloud service. Its plan controls how long events remain available to query: currently one year on the free plan or seven years on paid plans. Those query windows do not guarantee automatic deletion. See PostHog's retention information, or contact us with questions.
Using a Notion list without connecting
You can duplicate the shopping-list template and check products on this website yourself. This does not give us access to your Notion account or list. We receive the product details you submit for a website check, as described above. Results appear on this website and are not written back to Notion.
Agent connections
An agent can send the product details you provide to our read-only tools. We do not save those inputs as a check history or log barcodes, label details or protocol bodies. Your agent provider may retain the conversation and tool results under its own privacy policy. Hourly integration limits use a salted hash of the connecting network address. Daily counters are shared across connections and contain no network address. Hourly counters become eligible for cleanup two hours after their window starts; daily counters after two days. Scheduled cleanup removes expired counters in batches. Private shopping-list reviews use a server-only operator key to call the review service. That key is never given to shoppers or created separately for each customer. Integration calls do not create browser identifiers or public result links. We also count tool operations, their broad outcome and rounded duration in PostHog to monitor reliability and usage. These server metrics use a fresh identifier for each call and exclude network, account, workspace, session and conversation identifiers, inputs, results and error text. They do not depend on optional website or app analytics.
Connected Notion lists
If you connect a Notion list, we store its authorizing Notion user, workspace and bot identifiers, list and field mapping, warning country, management session and review state in Cloudflare D1. Notion access and refresh credentials are encrypted before storage. Our backend can decrypt them to carry out the reviews you request. The stored account identifiers are personal data, even though we do not save your profile name, email address or avatar. Notion may send profile details during authorization, but we select and save the identifiers needed for the connection.
Reviews read only the configured shopping fields, including the item, bought flag and any supported brand, barcode or packet details. They write only dedicated review fields and do not read unrelated pages or save shopping item text as a history. Review jobs are created when a connected item changes; we do not poll your workspace. If you enter personal information in a configured shopping field, we may process it during a review. Use product details only.
We use these identifiers to keep your connection separate from other users, find your chosen list and let you manage reviews. We retain the connection while it is connected, including while paused. Pausing does not delete credentials or revoke access. Management sessions expire after 30 days.
Disconnect first stops new work and waits for active reviews to finish. When disconnection completes, we delete the stored credentials, list mapping, queued work, counters and management sessions, and ask Notion to revoke access. Your shopping list stays in Notion. If Notion cannot revoke access automatically, remove Eat or Yeet from the connection settings in Notion. A hashed session receipt lets your browser confirm disconnection for seven days, then becomes eligible for scheduled cleanup. It contains no Notion credentials or shopping items. A private operator key authorizes the website to call the review tool; it is not stored in your list or sent to your browser.
Why we use personal data
We use the personal data needed to provide a connected-list service you request under our terms of use. Our lawful basis is performance of that contract. We use limited rate-limit and security data for our legitimate interest in protecting the service from abuse. Connecting is optional; without the required identifiers and credentials, automatic Notion reviews cannot run.
Services that help us run Eat or Yeet
Vercel hosts the website and API, and Cloudflare runs the backend and stores connection records. Notion receives requests to read your connected shopping fields and write review results. PostHog receives only the limited analytics events described above. These providers may process data outside the UK, including in the United States. Their data-processing terms describe the contractual safeguards for international transfers: Vercel, Cloudflare, PostHog and Notion. Contact us if you need information about the safeguards that apply to your data.
Public links are optional
If you create a public link, it is available for 24 hours. It contains a generic result, the check date, covered region, and an official warning reference when one matched. It does not include the barcode, batch code, or label details you entered.
Location preference
Your UK or US warning location is saved in a browser cookie for one year. This is a preference you choose, not your device location. The scanner and manual checks use the same selection.
News links
The service fetches food-safety headlines from publisher feeds. Opening a news link takes you to the publisher website, where its privacy policy applies.
Your privacy rights
You can ask for access to your personal data, correction or deletion, and request restrictions or a portable copy where those rights apply. You can object to processing based on legitimate interests. Email anthony@lexio.app; we may need information to confirm that the request concerns your connection. Do not send credentials or passwords. You can also complain to the UK Information Commissioner's Office.
Warning data
Results compare the information you provide with published data from the selected official food-safety sources. A missing match does not tell you whether food is safe to eat.