Privacy
Last updated: 23 Oct 2026
This page explains what happens when you use the Food Says Hi lookup. Food Says Hi is operated by Qomza, LLC.
Information you submit
A lookup is sent only when you press the submit button. Your food name or resized photo, optional food-type choice, and optional note go to Qomza through this site's Worker. Your photo's file name stays on your device; it is not sent. The Worker also sends technical request metadata: your Cloudflare connecting IP, browser language preference, a request identifier, the lookup type, and this site's platform, app identifier, version, build and environment. Please do not include sensitive personal information.
How long your lookup details are kept
Qomza’s gateway keeps what it receives for each lookup — your food photo or name, any optional food-type choice, any optional note, and the request metadata described above — along with the result it returns and related service information in its records. These records are not deleted automatically; they stay there until the gateway operator removes them. Only send details you are comfortable having kept there.
Feedback saved in this browser
This browser stores feedback drafts, pending revisions, and accepted feedback details so you can retry a send or edit an earlier revision. This can include the message and any reply email you choose to provide. These details remain in this browser's site storage until you discard them in the feedback panel or clear site data. Removing a local copy does not remove feedback already sent to Qomza; those records follow the retention described above.
Site performance analytics
This site is configured for Cloudflare Web Analytics. Cloudflare Web Analytics reports visits and page views, landing pages and referring sources, approximate country-level location, browser, and browser performance such as page-load timings and Core Web Vitals. When Cloudflare injects the beacon for this site, the beacon sends data to this site's /cdn-cgi/rum endpoint. Cloudflare says it discards the beacon's source IP at its nearest data center without storing it in core databases or logs, and does not track individual end users across its customers' sites. Read Cloudflare's RUM data and privacy details and Web Analytics dimensions.
Optional analytics and session replay
PostHog analytics and session replay are enabled at 100% by default on the public production site until the provider free-plan cap, with a brief banner to review or change either setting. You can reopen Privacy settings from the footer. Your saved choice stays in this browser until you change it or clear site data; Global Privacy Control and a saved rejection keep both features off. Analytics records page views, safe public clicks and form actions, and lookup outcomes. A lookup outcome can include the random operation ID and, when the gateway returned one for that lookup, its request ID; these identifiers are not derived from your food name, note, or photo. Events can include a general lookup status, but do not include your food name, note, photo, or the returned identification details. Qomza can use these identifiers to match analytics events, and any related session recording, to the lookup records kept by its gateway. Each event also carries the consent state that applied when it was captured. On PostHog's free plan, session replay recordings are retained for 30 days. Replay can include ordinary public page text and public images, but masks form values and excludes the photo you upload or receive back. It does not record network headers or bodies, console output, JavaScript exceptions, canvas content or inline image data. PostHog uses a namespaced browser cookie and local storage; when optional tracking is off, the SDK is opted out and replay is stopped. PostHog processes this data through its EU service. See PostHog's privacy information.
Operational diagnostics
We use Sentry's EU ingestion service to diagnose site and service failures. It receives bounded outcomes, durations, HTTP status and technical correlation identifiers for a lookup only after you submit it, and for feedback only when a delivery attempt is made. The Worker also records the result and duration of its request to the analysis or feedback service. Error diagnostics contain a sanitized error type and stack. Diagnostics do not include your food name, note, photo, request or response body, email address, or browser identity. We disable replay, page-behaviour and interaction tracking, including DOM and element details. Operation counts and duration distributions are recorded for these submitted operations; performance traces are sampled at 5%. Local development is labelled separately from production. Source maps are uploaded from the managed build path to help diagnose errors.
Abuse prevention
For abuse prevention, Cloudflare applies a best effort limit configured for 10 requests that reach the analysis limiter per 60 seconds per connecting IP in each Cloudflare location. Enforcement can vary by location, and people sharing a public IP may share the allowance.
Questions
For privacy questions, or to ask Qomza about the records kept for a lookup or request their removal, contact Qomza, LLC or email hello@foodsayshi.com. The contact page lists the postal address for legal notices.