PRIVACY · NOVEMBER 8, 2026
Browse without an account.
Browsing the website
The website does not use advertising trackers, accounts or payment collection. Optional analytics cookies are described below. Searches and filters are part of the page URL, so they may appear in your browser history and server logs. The web server and hosting provider may receive ordinary request information such as an IP address and browser details.
Website analytics
If you choose Allow analytics, we use PostHog to understand page visits, campaign referrals, interactions and app-link clicks, with masked session replay. Sanitized error reports include stack traces with error messages and page context removed. It uses a browser identifier and cookies or local storage to connect sessions. Inputs and replay text are masked. Elements marked for exclusion are not recorded. Search terms, barcodes, URL filters and fragments are excluded from event URLs; supported campaign tags are retained. We disable IP-based location enrichment. PostHog stays off until you agree. Change your choice using Analytics choices at the bottom of any page. Withdrawing stops future collection and clears the analytics identifier; it does not delete data already received by PostHog.
We also use Cloudflare to keep daily counts of food results viewed, results opened and comparisons made. For our PAA guide, we also count guide views, clicks to food browsing or the app overview, and whether that destination opens. These counters include only the action, the page type or guide, and the outcome. They do not store your search, barcode, selected foods or an identifier for you. We delete daily totals older than 90 days.
Read more about how Google uses data from sites that use its services.
The iPhone and iPad app
Scan history and setup choices are stored on your device. Saved foods are stored on your device. Searching or scanning sends your search or barcode to our food lookup service. If you enter an establishment number on a product page, we send that number and the product identifier to the lookup service. Barcode recognition runs on your device; the scanner does not take or upload photos.
The app does not require a 2table account. Saved foods, scan history and preferences remain on your device; we do not provide account-based cloud sync. Apple handles subscription purchases, which can be restored using the Apple Account used to buy them.
Recommendations use your latest ten scans and the store chain attached to each scanned product to look for reviewed alternatives at that chain. Our product service receives the product identifier and store chain for each request. Recommendations do not require store selection or location access. Optional scan-location sharing is a separate setting described below.
Earlier app versions could save package photos and barcode or establishment-number reads on your device. Existing photos can remain in the app’s limited local collection. If you enable Contribute package photos in Settings → Privacy, pending contributions from those earlier scans can upload cropped photos and scan details privately to 2table to improve product matches. The current barcode scanner creates no new photo contributions. A region is included only when scan-location sharing is enabled; precise coordinates and account identifiers are not included in photo contributions. Estimated plants are stored separately from numbers read from a package. Contributed photos are not posted publicly. Apple device attestation helps block forged uploads; a device verification key and security counters are kept for this purpose. Turning this off cancels unsent contributions and stops future uploads; it does not erase photos already received or your local copies. Incomplete uploads are removed after seven days. Unreviewed contributed photos are removed after 90 days. Photos retained as reviewed product evidence may be kept longer. Scan details support product matching and evidence review. You can contact us about removal. Because contributions have no account identifier, a barcode and approximate scan date can help us locate a submission. Remove a scan from History to remove its package photos from this phone.
After your first successful scan, we offer optional scan-location sharing. If you agree, the app requests location access while you use it. It rounds coordinates to an approximate area before sending them to 2table with the scanned barcode, matched product identifier when available and the scan hour. These signals help us improve regional product coverage and matches; they do not establish the store or the food's origin. The stored scan record has no account identifier. A separate device verification key and security counters protect the upload service. We store location records privately in Supabase and delete records older than 90 days in a daily cleanup. Failed submissions are retried when you next use the app and discarded if they are at least 23 hours old. Turning off Share scan location in Settings → Privacy stops future sharing and removes unsent records; it does not erase records already received. The app does not track location in the background. Scanning works without permission. Scan-location sharing is separate from PostHog usage analytics. Our intake and hosting providers also process request information, including IP addresses, to deliver the service and limit abuse. That is separate from the rounded location stored in scan records.
If you enable Share usage data in Settings → Privacy, the app uses PostHog to understand steps such as opening a result, saving a food or completing onboarding. These events include an app-generated identifier and basic device information, but not the food you selected, search text or barcode. IP-based location is disabled. Sharing is off until you choose it. Turning it off in Settings → Privacy stops future collection and optional replay; it does not delete earlier events already received by PostHog. With usage sharing enabled, sanitized error reports may include app stack traces; they exclude search text, barcodes and raw request bodies.
Interaction replay is optional and off until you agree. It records masked screens and taps through PostHog to help us find confusing steps. Text and images are masked; camera, barcode entry, sharing and payment screens are excluded. No audio is recorded. A visible indicator lets you stop recording, and you can withdraw permission in Settings → Privacy.
When subscriptions are enabled, Apple handles payment and RevenueCat checks purchase and subscription status using an app-generated customer identifier. RevenueCat also measures offer views and paywall interactions so we can compare subscription options. We do not receive your payment-card details. If you allow usage analytics, we also link the analytics identifier to the subscription customer record to measure which offers work. Turning usage sharing off stops future linking; previously received data is not automatically erased.
Corrections
Saving a correction downloads a file locally and does not send it to us. If email contact is available, you choose whether to send the prepared message through your email provider. Do not include payment information or other sensitive personal details.
Links to other services
Links to publishers and the App Store take you to services with their own privacy practices. App Store links may include a campaign or product identifier; they do not include an identifier for you.
Questions
Contact hello@2table.app about privacy.