No Big Dish
简体繁體
← Home

Privacy · ZENDER, LLC

Privacy Policy

Effective date: 2026-11-16

This policy explains how the No Big Dish iPhone app, web version, ZENDER, LLC website, and our email correspondence handle information. The app is developed and maintained by ZENDER, LLC. “We” means ZENDER, LLC. If the Chinese and English versions differ, the English version controls.

1. Information processed on your device

No account is required. The iPhone app includes its built-in recipes and resources; cooking, planning, pantry management, and on-device text recognition can run on your device. AI recipe creation, AI receipt reading and AI meal suggestions require an internet connection; see Section 6A. The app has no ads or ad-tracking code, and no service that automatically uploads crash reports from the app. Usage sharing is off by default and starts only after you choose to share, as described in Section 6B. AI request metering, short-term operation records and daily operational and cost totals are described in Section 6A; information provided by Apple is described in Section 6.

To provide its features, the app stores or calculates:

The app also uses recipe quantities, household size, its local ingredient nutrition table, and recorded ingredient unit prices to calculate estimated food categories, amounts, nutrients, and meal costs on your device. A meal share card may display estimated protein, carbohydrates, and fat per person. The app does not read Apple Health data or automatically upload your personal records for these calculations. Apart from AI processing in Section 6A and usage sharing you separately enable in Section 6B, the app does not automatically upload these personal records to us or a cloud recognition service. Usage sharing sends only the local summary listed in Section 6B, not individual meal records or step-by-step cooking logs. System backups and copies you choose to share are explained in sections 4 and 7. If you choose AI recipe creation, AI receipt reading or AI meal suggestions and consent to sending, the information specified in Section 6A is sent and handled as described there.

The iPhone app also reads available subscription entitlement information provided by Apple and caches the latest subscription status on your device, such as the tier, product identifier, expiration and renewal status, and update time.

2. Receipt photos and selected images

Receipt recognition is available only in the iPhone app. You can scan one or more receipt pages with the document camera or select one image through the system photo picker. The app uses Apple Vision to recognize text on that iPhone. It does not upload receipt photos and does not require an API key. Recognized text stays on the iPhone by default; only if you have an AI subscription, choose AI receipt reading, and consent to sending is the recognized text sent, as described in Section 6A.

The app uses the photo for recognition and does not save it as a receipt image archive. An original image selected from your photo library remains managed by that library. Recognized text is used to prepare a draft for review. When you save, the resulting pantry and spending records retain the relevant items, store, date, currency, amounts, and product information. Spending records may also contain names, prices, or recognized product-line text for products that were not added to your pantry.

You can review and edit the results before saving, or cancel. Cancelling does not add pantry or spending records for that receipt. You choose whether to record the spending as well.

You can take or select a photo for a meal share card, or use a collage of recipe images without a photo. The app processes the selected image and generates the card on your device; it does not automatically upload images to us. Preview images are processed in memory. Native image selection, sharing, or saving may create temporary image files, which the app attempts to clean up when you close the preview, finish the action, or next open the app. Images you choose to save to Photos, download, or share are separate copies and are not deleted when you close the preview.

Screenshot text recognition also uses Apple Vision on your iPhone without an online recognition service. The screenshot itself is not sent to us or Anthropic. Recognized text can fill the recipe input; after you review it and consent to sending, it is handled under Section 6A. Original images in Photos and their backups are managed by the system and your settings.

3. Camera, photos, and notifications

When you choose to photograph a receipt or take a photo for a meal share card, the system may request camera permission. If you decline, features that do not require taking a photo remain available. Images are selected through the system photo or file picker. The app reads the images you select and does not request permission to read your entire photo library. When you choose to save a meal share card to Photos, the iPhone app requests permission to add images so it can save that finished card; this does not give it access to read your other photos. You can manage these permissions in system settings.

If you allow notifications, the app schedules timer and cooking-start reminders locally, without push messages from our servers. Notifications may show dish names and steps. Depending on your settings, iOS may display them on the lock screen or a paired Apple Watch. You can change notification permissions and previews in system settings.

4. Imports, exports, and sharing

You can export a pantry file, a favorites-and-recipe-notes file, a shopping list, or a cooking activity log. In addition to pantry items and change history, a pantry file may include unit prices, package information, and records such as whether ingredients were used up. Logs may include recipe notes and content recorded when you select ‘I want to cook this.’ None of these is a complete backup of all app data. Importing a pantry or favorites-and-notes file reads the file on your device and replaces the corresponding data. You can also export My Dishes, which may include source notes. Recipe inputs, drafts awaiting review, and My Dishes records may have copies in system backups. Check the specific export; an export of one category is not a complete backup.

The iPhone app uses the system share sheet to send an export to the app or destination you choose. The web version uses browser sharing, downloads, or copying. These actions do not automatically send files to ZENDER, LLC. If you choose email, cloud storage, or another service, that recipient’s practices govern its copy. Review the contents before sharing.

You can generate and preview a meal share card, then choose to share it through the system or browser, save it to Photos, or download it. Depending on the available data, the card includes your selected photo or a recipe-image collage, the date and meal, dish names and rice information, the number of dishes, cooking time, and estimated nutrients per person and meal costs. Items may be omitted when data is insufficient, and costs may cover only some ingredients. The card may also contain a QR code that opens the relevant recipes. The information shown on the image is included when you share it with your chosen recipient. Review the preview before deciding to save or share it.

Saved feedback stays on your device; the app does not send it automatically. When you choose to send feedback, the app prepares an email to hello@zenderllc.com. It fills in the app version, platform, device model and operating system (browser information in the web version), along with the relevant dish names, steps, time recorded, selected reasons, and your comments from the selected feedback. Feedback about a meal may list that meal’s dishes; general feedback may not relate to a particular dish or step.

You can review the email body before sending and decide whether to send it in the email interface. The iPhone app uses the system mail composer; the web version opens an email tool. Including a cooking log is unchecked by default. A log is added only if you select that option: as an attachment on iPhone or in the email body on the web. If the web email is too long, only the more recent part of the log may be included, with a notice explaining the omission. The app does not automatically include pantry records, spending records, or photos.

5. The web version and company website

The web version stores the records described in section 1 in the browser on your current device. It does not automatically upload your personal cooking, pantry, planning, or spending records. It does not offer receipt photo recognition. The usage statistics in Section 6B are currently offered only in the iPhone app.

The company website and the currently deployed web version are hosted on GitHub Pages. When you visit or update them, your browser requests pages, application files, and recipes from GitHub. GitHub processes technical information, including your IP address and the addresses of requested files, to deliver and protect the service. See the GitHub Privacy Statement.

A meal-card QR code or recipe-sharing link may include identifiers for the selected recipes in its URL. Links generated by the app do not include your photo, spending, nutrition estimates, or cooking log, and do not add an account or sharer identifier. When a recipient opens the link, their browser requests the web version hosted on GitHub Pages and selects those recipes locally. Recipe parameters in the link may form part of the request URL received by the hosting service and of copies retained by a browser or sharing service.

The company website has no account system, advertising, analytics scripts, or tracking cookies. The currently deployed company website, web version, and iPhone app use system fonts and do not load fonts from Google Fonts. The web version uses local storage and caching for records and offline files.

AI requests pass through our server on Cloudflare Workers and Cloudflare’s network. Cloudflare processes technical information such as IP addresses and the request’s country or region to deliver and protect the service. This is separate from the subscription usage records in Section 6A. See Cloudflare’s privacy policy. AI features are offered only in the countries and regions supported by our model provider, Anthropic. When you open the subscription page or before you use AI, the app asks our server whether AI is available where you are. This check carries none of your content and our server does not record it (Cloudflare still processes the IP address and country as usual). The server uses the request country or region provided by Cloudflare to determine availability; this AI regional restriction does not apply to app features that do not require AI.

6. Contacting us and information provided by Apple

When you email hello@zenderllc.com, we receive your email address, your name if supplied, your message, and attachments. Feedback emails sent through the app also include the version, platform, device or browser information, feedback details, and any cooking log you choose to include, as described in section 4. We use them to respond, investigate problems, and keep necessary correspondence. If you choose to send a cooking log, we may also use it to improve recipe timings and scheduling. Email is handled through Google Workspace. We do not sell this information or use support emails for advertising.

If you choose to share diagnostics and usage information with app developers, Apple may provide us with crash reports and aggregated usage statistics through its developer services. These come from Apple and are separate from the activity logs stored locally by the app. For Apple’s practices and controls, see Apple’s Privacy Policy and Device Analytics & Privacy.

The iPhone app uses Apple StoreKit to read and update AI subscription entitlements. Apple may provide product and transaction identifiers, purchase and expiration information, trial and renewal status, and signed transaction data. When you use AI features, the app sends Apple’s signed subscription credential to our server to verify the signature and eligibility; it is not sent to Anthropic. The production server also supports verification of Apple sandbox subscriptions used for review or testing, with usage counted separately from production subscriptions. For eligibility and limits, the server records transaction identifiers, months, and usage; this does not create additional storage of your method text or generated content. The name-only exception is described in Section 6A. The app does not ask for your Apple account password or payment-card details; Apple handles payment. This processing is separate from Apple’s diagnostic statistics.

You can also report or give feedback on AI content through the app. It prepares an email to hello@zenderllc.com for you to review and send yourself; the complete recipe is not attached by default. Content or attachments you write or choose to include are sent with the email. We handle received email under this section and Section 7.

6A. AI recipe creation, receipt reading and meal suggestions

When you choose AI recipe creation and consent to sending, the app sends the dish name, method text, number of servings, extra requests, and interface language to our server on Cloudflare, which forwards them to Anthropic’s commercial API to generate a recipe. Not every recipe-creation action calls AI: suitable existing recipes or method cards can be used on your device. An AI request does not automatically include your pantry, spending records, photos, or cooking logs. The dedicated source-URL field is not sent; URLs you paste into the method text are sent with that text. The current AI recipe flow does not read that webpage or download video or audio. Review your input and avoid including unnecessary personal information.

AI receipt reading: if you have an AI subscription, choose to let AI read a receipt, and consent to sending, the app sends only the text your phone recognized on that receipt (the lines its rules could not read, with the rest of the receipt text as context; the whole receipt when you tap “Let AI read it again”), which lines to read, and the currency the app guessed, to our server on Cloudflare, which forwards them to Anthropic’s commercial API. Receipt photos are not sent. You review and edit the results on your phone before anything is saved. Receipt text can include the store, date, items, and amounts; keep that in mind before sending. This consent is asked for and recorded separately from consent for AI recipe creation; both are withdrawn together in Settings › Help. Our server does not store receipt text or write it to our own operation logs. Each read counts as one receipt toward a separate monthly receipt limit; it does not use your AI recipe creation allowance.

AI meal suggestions: the app’s own suggestions (based on your pantry, recent meals and time) run on your device without AI. If you have an AI subscription, type a sentence about what you feel like, and consent to sending, the app sends that sentence to our server on Cloudflare and on to Anthropic’s commercial API to turn it into selection conditions (such as how long, not spicy, ingredients to use or avoid, budget). The app then picks candidate meals on your device and sends a summary of them — dish names, about how long they take, estimated cost, and short reasons such as which ingredients from your pantry they use and how many days you have had them — with your sentence, so that AI can choose one and say why. Your full pantry, receipt details and cooking history are not sent. This consent is asked for and recorded separately and is withdrawn together with the others in Settings › Help. Our server does not store the sentence or the candidates or write them to our own operation logs. Each suggestion counts toward a separate monthly suggestion limit and does not use your AI recipe creation allowance.

Apple’s signed subscription credential goes only to our server for verification, not to Anthropic. The app stores the consent version and time locally; later requests under the same version reuse that consent rather than asking every time. You can withdraw it in Settings › Help; a later AI request will ask again. If the categories of information sent or the recipient change, we will update the consent version and ask again. Withdrawal cannot undo requests already sent and processed.

If the first draft fails checks on your phone, the app sends the original input, AI draft, and list of problems to our server and then to Anthropic for up to two automatic revisions. Your consent covers these requests. Each generation or automatic revision counts toward AI usage. Manually adjusting quantities or running checks on your phone does not itself count as an AI request.

Except for the name-only originals described below, our server does not store your submitted method, extra requests, or generated recipes in a content database or write them to our own operation logs. Request processing and third-party retention still occur as described here; this is not a claim that information never passes through servers or third parties.

Exception: when you enter only a dish name (no method or extra requests), we keep one copy of the AI-generated recipe that passed the checks on your device — only the dish name, the number of servings, the interface language and the recipe itself, not linked to your subscription, your device or anything that identifies you — and other users who enter the same dish name may receive that copy. Recipes generated from a method or extra requests you wrote are not kept.

This exception applies to name-only requests with no method or extra requests sent. The dedicated source-URL field stays on the device; filling that field alone does not exclude this exception. To verify that the original came from the server, the server first stores a pending draft. After the phone’s checks pass without relevant warnings, it confirms the draft using a verification digest; only confirmed drafts are available for reuse for the same dish name and serving count. The server also stores technical fields such as prompt version, times, and verification digests. This original-recipe table has no subscription transaction or device identifiers and does not link the recipe to a user. It does not retain quantities or tags you edit during review. Pending and reusable drafts do not automatically expire; the operator can delete or replace them. Deleting your local recipe does not delete this independent original. Receiving a reusable draft does not call the model or count toward AI usage; asking AI to write a fresh version does.

For subscription eligibility and usage limits, we store the subscription transaction identifier (Apple’s originalTransactionId), UTC month, and AI usage (AI recipe creation usage, AI receipt reads and AI suggestions are counted separately). Eligibility and usage processing for production, review, or test subscriptions does not require your name, email, or device identifier. A transaction identifier identifies the same subscription; not all server records are anonymous. Each month’s usage records are deleted by a daily cleanup job once 90 days have passed after that UTC month ends; under normal operation, the daily schedule may add about one day. When the production server accepts sandbox subscriptions, it marks their usage separately and keeps a monthly aggregate sandbox usage count for a separate limit. These counts follow the same cleanup rule and do not add retention of user method text or generated content.

To monitor the AI service, troubleshoot faults and control service costs, we separately combine service metering into daily totals by UTC date, feature and production or test environment: the number of model calls and how many of them returned a normal response, a refusal or an error; how many name-only requests were answered with a saved original recipe instead of calling the model; the number of tokens used; and the estimated cost in US dollars, together with how many calls had no cost estimate. The aggregate table does not store dish names, user input, generated content, receipt text, subscription transaction identifiers, support IDs or IP addresses, and does not count subscriptions. We do not use these totals for individual profiles, audience measurement or user behavior analysis, or send them to Anthropic or a third-party analytics platform. Only the developer and maintainer can view them through a restricted administrative interface. Daily totals are retained on a rolling 90-day basis and removed by a daily cleanup task; normal scheduling may add about one day. Estimated costs are not the provider’s final bill. Subscription quota records and short-term operation records retain their separate retention periods described in this section.

To suspend subscriptions that abuse AI, we separately store the subscription transaction identifier, suspension time, and a reason code. The record is kept while the suspension is in effect, has no automatic expiration, and is not removed by monthly cleanup. The operator deletes the row when the suspension is revoked. Matching requests are rejected before usage is charged or a model is called: they consume no AI usage, read no webpage, and make no model request. Recipes already saved on the phone are unaffected. Suspension applies to a subscription, not an identified person. You can contact hello@zenderllc.com.

To act on reports about AI-written content, the server derives a support ID from the subscription transaction identifier using a keyed one-way hash and sends it to the app with AI responses. The app keeps it on your phone and shows it under Settings › Help › Contact us. When you report AI-written content, the email preview includes the support ID by default; you can untick it before sending. The support ID cannot be turned back into the transaction identifier. We use it only to find the matching subscription in the usage and suspension records above, and we do not store it separately.

After subscription usage records, suspension records, daily operational and cost totals, or the weekly usage totals in Section 6B are deleted from the current database, Cloudflare’s database history recovery feature may still restore earlier copies, currently for up to 7 days on the free plan or 30 days on paid plans. Deletion does not immediately erase every recoverable copy.

The server is configured to disable automatically generated per-invocation logs while keeping our own operation records, such as events, statuses, feature and result codes, the model used, token counts and estimated cost, a sandbox-environment flag, and cleanup statistics. These do not contain your submitted content or generated recipes. Cloudflare Workers Logs currently retains records for about 3 days on the free plan or 7 days on paid plans. Cloudflare’s technical processing to deliver and protect the service is described in Section 5.

Anthropic generally deletes commercial API inputs and outputs from its systems within 30 days; contracts, abuse prevention, security, or legal obligations can require longer retention. Commercial API content is not used for model training by default without explicit agreement. Our not storing a category of content does not prevent Anthropic’s temporary retention under its rules. See Anthropic’s Commercial Terms, commercial retention guidance, and training guidance (checked November 13, 2026).

While the native iPhone app waits for an AI result, it temporarily stores the request, response, and processing state as request working files on the device. Their directory is marked as excluded from iCloud and computer system backups. The app attempts to remove these files when processing finishes. Cancellation or errors can leave files behind; on a later app launch, it attempts to remove files last modified more than a day earlier. This is not guaranteed background deletion at exactly 24 hours or a secure-erasure guarantee. Ordinary recipe inputs, review drafts, My Dishes, and source notes are stored separately on the device, are not subject to that one-day rule, and may have copies as described in Sections 4 and 7.

6B. Optional usage statistics

Usage sharing is off by default. If you choose to share, the app starts collecting local counters with the next full week and sends at most one summary a week: a range for meals completed in the app that week (0, 1–2, 3–4, 5–7 or 8 or more), whether you used Pantry, receipt scanning, meal planning, suggestions or recipe templates, and the public app version and interface language. It also includes a common protocol version and the UTC Monday date for that week, not the times of individual actions or your local time zone. Weeks start on Monday in UTC. We use it only to understand and improve the app’s features, not for ads or personalized recommendations.

This channel does not send dish names, pantry contents, receipt text or amounts, photos, individual meal records, step-by-step cooking logs, location, a permanent device or installation identifier, subscription credentials, transaction identifiers or support IDs. It includes no identifier for connecting reports across weeks. Summaries go through Cloudflare to our dedicated aggregation service, not to Anthropic or a third-party analytics platform. Network services still process technical information such as IP addresses to make the connection. Our statistics receiver does not write IP addresses, request headers or individual reports to a database or logs, or use them to identify, deduplicate or link devices. Each received summary is immediately merged into separate weekly totals; we retain no individually browsable report or personal activity timeline. Only the developer and maintainer can view the totals.

You can preview the next summary and review recent sending history in Settings › Usage statistics, and turn sharing off at any time. Declining or turning it off does not affect free features, subscription price or allowances, or paid AI access. Turning it off stops collection and sending and clears unsent local statistics. A request already in progress may have reached the server. Received summaries merged into totals cannot be located, deleted or withdrawn individually; they are removed under the retention rules below. This switch does not change the processing needed to provide AI services described in Section 6A.

An unsent summary is kept locally for up to 14 days after its reporting week ends. The server keeps only combined weekly totals and removes them through a daily task once 90 days have passed after the reporting week ends; normal scheduling may add about one day. Your device keeps copies of the last four sending attempts for you to inspect or delete. In the native iPhone app, these statistics files and your sharing choice are excluded from system backups; sharing defaults to off after restoring a backup or reinstalling. Deleting a local copy does not delete server totals. Database recovery copies may remain for the periods described in Section 6A. Failed or unconfirmed requests are not retried, so reports may be missed; the results do not represent all users or an exact number of people.

7. Retention, deletion, and system backups

Records remain on your device until you delete them, the app removes older records under its retention rules, or your device or browser clears the data. Some old plans, shopping states, logs, and history are removed as time or record limits are reached. The app should not be used as a permanent archive.

On the relevant screens, you can edit or delete plans, meal and spending records, remove favorites, clear recipe notes, or delete unsent feedback entries. ‘Clear pantry’ removes pantry items and change history; it does not delete data belonging to other features. Auxiliary records such as ingredient unit prices, package information, and answers about whether ingredients were used up may also remain. Related content may still exist in older logs, undo records, or change history after an individual record is deleted. Closing a meal-card preview or deleting local records does not delete copies already saved to Photos, downloaded, shared, or sent. Emails sent to us are handled under the support-email retention terms below. You can also delete local My Dishes records and related recipe inputs. Deleting a local copy does not delete independent server records; their retention rules are described in Section 6A.

Using “Delete App” in iOS removes its app data from the device. “Offload App” can retain data and is different. You can remove web records by clearing that website’s data. Deleting the app, clearing pantry data, or clearing browser data does not delete files you already exported, copies you sent to someone else, or originals kept in your photo library.

The app has no personal-record cloud sync or remote backup service of its own. iCloud backups, computer backups, or photo services you enable may hold copies of local records, depending on your settings; recipe inputs, review drafts, My Dishes, and source notes may be included. The native AI request working files described in Section 6A are separately excluded from system backup; this does not exclude other local records. In the native app, the usage-sharing choice, counters, unsent summary and sending copies in Section 6B are separately excluded from backup; backups of other app data still depend on system settings. Deleting local data does not mean all backups are deleted. We cannot remotely view or restore local records you have not sent. Email you send us and AI processing, subscription usage, suspension, daily operational and cost totals, name-only original-recipe records, and optional weekly usage totals are handled under Sections 6, 6A and 6B.

We retain support emails and attachments as needed to respond and resolve the matter, or to meet legal obligations. You can email us to request access to, correction of, or deletion of information you sent us. We will explain any information we must retain.

8. Children, future features, and policy changes

The app is a general-audience cooking tool and is not directed at children under 13. We do not knowingly collect personal information from children.

All built-in recipes, cooking cards, pantry tools, receipt text recognition, shopping lists, meal plans, nutrient estimates, spending records, and other non-AI features are free to use without a subscription. Only AI recipe creation, AI receipt reading and AI meal suggestions require an AI subscription, available monthly or annually, with a 7-day free trial for eligible Apple Accounts. After the trial, the subscription renews automatically at the price shown before purchase unless canceled in advance. You can manage or cancel it in your Apple Account subscription settings. Apple handles subscriptions and trial eligibility. AI features are subject to usage limits and the online processing and storage exceptions described in Section 6A. Usage sharing is a separate, voluntary choice. Declining or withdrawing does not affect those features or prices. If later features change how information is handled, we will update this policy and the relevant App Privacy disclosures, and obtain consent where required. This page will show the updated effective date.

9. Contact

For privacy questions or requests, email hello@zenderllc.com.
ZENDER, LLC
Texas, United States