FoodNet

Privacy Policy

DRAFT - pending owner review

Last updated: August 2, 2026

FoodNet is a food app for iOS and a public website (a recipe archive, a read-only feed, and a chatbot), operated by an individual developer, Teddy Lazar. This policy explains, in plain language, what data FoodNet collects, how it is used, and what your choices are.

If anything here is unclear, contact us at tmlazar913@gmail.com.

What we collect

Account data. When you sign up we collect your email address, username, first and last name, and optionally a phone number. Signup does not require an invite code. If you sign up with one, we record which invite you used and how you heard about FoodNet (referral sources). Your password is never stored in plain text: we store only a salted bcrypt hash (bcrypt_sha256). FoodNet does not offer Google, Apple, or any other third-party sign-in, so no outside provider is told when you sign in. We verify your email address with a one-time token.

Sign-in tokens. We issue JWT access and refresh tokens to keep you signed in. On the website these are stored in httpOnly cookies.

Pantry and food data. Your inventory (what food you have, quantities, expiry dates, how each item was added: typed text, receipt scan, photo, speech, manual entry, or batch import), your saved and created recipes, meal plans, grocery lists, and cooking history.

Media you upload. Receipt photos, food photos, recipe images, post images, and profile avatars. Receipt and food photos are processed by AI to extract the items on them.

Voice input. If you use voice entry, your audio is sent to OpenAI's Whisper API to be transcribed to text. The text is then processed like typed input.

Chat assistant conversations. Messages you send to the FoodNet assistant, and any images you share in chat, are stored in your chat sessions.

Search history. Recipe searches by signed-in users are logged (the query text, tied to your account) to improve search quality.

Social content. Posts, comments, and reactions you create.

Website usage events. Two first-party events on the public website, a page view and a click on the "get the app" link, each stamped with the fn_visitor cookie described under Cookies. These are counted in aggregate and are not linked to your account. (Google Analytics, described below, is separate.)

How we use it

  • To run the app: matching your pantry items to our food catalog, computing nutrition, recommending recipes, planning meals, and building grocery lists.
  • To operate the chat assistant and its tools (recipe search, pantry updates, meal planning) on your behalf.
  • To send you email. Transactional email (verification, password reset, a one-time welcome after you verify) is always sent. Optional categories (promotional emails, app update announcements, invites from other members) are sent only while you have them enabled; each is a separate toggle in Settings and every such email carries a one-click unsubscribe link. We do not share email lists with third parties and we do not sell your data.
  • Analytics: we look at aggregate usage (for example search volumes and job health) in an internal admin dashboard. The public website also uses Google Analytics to measure traffic (pages viewed, referring site, approximate country, device type). The mobile app contains no third-party analytics at all, and there is no advertising anywhere.

AI processing

FoodNet uses external AI providers as processors. Be aware of what this means before you share something sensitive in chat:

  • Anthropic (Claude). Your chat messages, plus context the assistant needs (your profile, inventory, and the recipe you have open), are sent to Anthropic's API to generate responses. Anthropic is also used for offline data-quality jobs on catalog data (not your personal content).
  • OpenAI. Used for: speech-to-text (Whisper), reading receipts and food label photos (vision models), and text embeddings that power semantic recipe and food search. Recipe and food embeddings are computed from catalog text; chat-related processing can include your content.

Assistant memory. The assistant can propose durable "food memories" about your preferences (for example, a cuisine you cook often). These are only proposals: they are saved as candidates for your review and are not used as context until you confirm them. This feature is off unless you enable memory inference in your AI data settings. The assistant is instructed never to infer sensitive information (health, allergies, religion, identity).

Web search. The assistant can run cooking-related web searches through the Brave Search API. Only the search query text is sent, not your account data.

Chat transcripts are retained. Chat sessions are soft-deleted when you delete them: they stop being visible to you but are not immediately erased from our database.

What is public

Please assume the following is visible to everyone, including logged-out visitors to the FoodNet website:

  • Posts are always public. There is no private-post option. Your posts, their images, comments, and reaction counts are visible to the FoodNet community and appear on the public website feed, which logged-out visitors can read.
  • Public profiles and recipe catalogs are opt-in. Your published recipe catalog is only visible at your public profile if you turn on the public-profile setting (is_profile_public). This setting gates your recipe catalog page; it does not hide your posts.
  • The recipe archive and public website content are visible to everyone.

Do not post anything you would not want public.

Storage and retention

  • Where. Data is stored on AWS infrastructure in the United States: the application database, and media files in Amazon S3 (post images, recipe images, avatars, receipt and food photos). Media is served through short-lived presigned URLs, not public buckets.
  • Chat-uploaded media. Images you share with the assistant are tracked in a retention registry with a concrete deletion deadline. The default retention is 30 days; you can set your own retention window (1 to 365 days) in your AI data preferences.
  • Chat sessions. Soft-deleted on request (hidden, not immediately erased).
  • Deleted inventory items. Trashed pantry items are retained for about 30 days.
  • Account deletion. Deleting your account deactivates it immediately: you can no longer sign in and your profile, posts, and recipes stop being visible to anyone else. Your data is then held for 30 days, so that an accidental or regretted deletion can be reversed by contacting us. After 30 days your account and the personal data attached to it are erased. Two things outlive that window: content you made public that other members have since saved or copied into their own accounts, and aggregate counts that identify no one.

Third-party services

  • AWS (S3, SES, hosting). Stores our database and media, and sends our transactional email. US-based infrastructure.
  • Anthropic. Processes chat assistant conversations and related context to generate responses.
  • OpenAI. Processes voice recordings (transcription), receipt and food photos (vision), and text for search embeddings.
  • Brave Search. Receives cooking-related search queries when the assistant searches the web.
  • USDA FoodData Central. We look up nutrition data by sending food name text queries only. No personal data is sent.
  • OpenFoodFacts. Same: food name or barcode queries only. No personal data is sent.
  • Google Analytics. Runs on the public website only, never in the mobile app. It receives the page you viewed, the site that referred you, your approximate location derived from your IP address, and your browser and device type. IP addresses are anonymized by Google before storage, we have Google Signals (cross-device advertising features) switched off, and the data is retained for 14 months. It does not run on the admin or docs pages.

We do not sell personal data to anyone, and no ad networks run on FoodNet.

Cookies

Three kinds of cookies are used on the website:

  • Authentication. httpOnly cookies holding your access and refresh tokens, used only to keep you signed in.
  • Visitor id (fn_visitor). A first-party httpOnly cookie holding a random id, kept for one year. It stamps the two usage events described under "What we collect" and rate-limits the public chatbot so one visitor cannot exhaust it. It is not tied to your account and is not shared with anyone.
  • Analytics. Google Analytics sets its own cookies to count returning visitors and group page views into sessions. These are set on the public website only, not on the mobile app.

There is no advertising cookie of any kind. You can block the analytics cookies with your browser's tracker blocking or a "do not track" extension, and the website works normally without them.

Your choices

  • Delete your account from the app, which deactivates it at once and erases it 30 days later, as described above.
  • Delete chat sessions at any time (soft delete).
  • Delete posts and comments you have made.
  • Keep your profile private. The public-profile setting is off by default; your recipe catalog is not publicly listed unless you turn it on.
  • Control AI data settings. Memory inference is opt-in, proposed memories require your confirmation, and you can set your own media retention window and training-consent preference in AI data settings.
  • Control your email. Every non-essential email (promotional emails, app update announcements, invites from other members) includes a one-click unsubscribe link, and the same categories can be toggled any time in Settings. Transactional email (verification, password reset) is not affected by unsubscribing.

Children

FoodNet is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has an account, contact us and we will remove it.

Changes

We may update this policy as FoodNet changes. We will update the date at the top and, for significant changes, notify you in the app or by email.

Contact

Questions, data requests, or concerns: tmlazar913@gmail.com