Privacy Policy

1. Our Privacy Philosophy

We do not require you to create an account, provide an email address, or share your identity to use Keto Peek. We do not sell your personal information to advertisers. Some features send data to our servers so we can return a verdict. The details are below.

2. Information We Process

Barcode scanning

When you use the barcode scanner, your browser uses the camera to read the code. The decoded numeric barcode (e.g. UPC or EAN) is sent to Keto Peek's API over HTTPS. Our servers query nutrition sources such as Open Food Facts and, when configured, USDA FoodData Central or UPCitemdb to build a result or recover a title/brand hint. These requests are not tied to a user account. We don't have accounts.

Typed product name

When you search by food or product name, your query text is sent to our API over HTTPS so we can resolve it against databases or other configured logic and return a result. If deterministic sources do not find enough data, configured AI providers such as Gemini or OpenAI may be used to infer structured nutrition. Again, there is no account ID attached.

Device storage

Your recent scan history is stored in your browser's local storage, capped at the newest 20 results and automatically pruned after 90 days. Your latest result for the result screen is held in session storage for that browsing session. Saved History may include valid Open Food Facts thumbnail URLs so the History list can show product images; invalid legacy thumbnail URLs are dropped. We cannot read those browser stores from our servers. You can remove saved History rows in the app, clear all History, or clear site data for Keto Peek in your browser settings.

Keto Peek's service worker stores a small offline shell and static assets so the app frame can reload. It does not cache analyze API responses, barcode/text lookup requests, or upload bodies.

3. Cookies and Analytics

Keto Peek does not run third-party ad trackers or cross-site tracking cookies to follow you around the web.

We use Vercel Web Analytics and Vercel Speed Insights for pageview, performance, and low-cardinality product-health measurement. We do not send barcode digits, typed queries, product names, ingredients, image URLs, or free-form nutrition text as analytics event properties.

Our hosting provider may collect standard technical information, such as IP address, request timestamps, and URLs, when you use the site and API. When production rate limiting is configured, Upstash Redis may store IP-derived counters for short minute/hour windows so the API can limit abuse.

• We do not sell your usage data to advertisers or data brokers.

4. Data Security

We do not maintain a user account database (there are no logins). Much of what you see in the app, including history and the current session result, stays on your device unless you send a barcode or text query to our API for processing.

API traffic is sent over HTTPS. Like any online service, hosting and infrastructure may retain short-lived logs for security and operations; we still design the product so we are not building a dossier on individuals.

Server-side provider responses from Open Food Facts, USDA FoodData Central, and UPCitemdb may be cached for up to 30 days to improve speed and reduce repeated third-party calls. Clearing browser History removes your device's saved result list, but it does not purge those server-side provider caches.

5. Third Parties and Images

Our app may contain links to other websites (such as detailed food guides). We are not responsible for the privacy practices of those external sites and encourage you to read their policies.

Some result, History, scan-preview, or food-search thumbnails may load directly from Open Food Facts or its image CDN. Those image elements use no-referrer, but the image provider can still receive normal browser request information such as IP address, user agent, and the requested image URL. Local History keeps only thumbnail URLs that pass the shared Open Food Facts product-image policy.

6. Updates to This Policy

As Keto Peek evolves, we may update this policy to reflect new features. The "Effective Date" at the top will always show the most recent version.