Common questions.

No. MenuRegistry produces informational allergen audits. We are not a law firm and the audit report is not a legal opinion. It is not a substitute for review by a qualified compliance attorney or registered dietitian, and it does not certify that your menu is legally compliant with any federal, state, or local law. See our Disclaimer for the full statement.

The audit is useful but not infallible. We use automated language analysis to read your menu and infer ingredient content from item descriptions. Accuracy depends heavily on how much detail your menu descriptions contain: a dish listed as “Caesar salad” gives the engine less to work with than one that spells out “romaine, anchovy Caesar dressing, shaved Parmesan, croutons.” Items where confidence is low are flagged as MEDIUM or LOW risk rather than silently passed. We do not claim 100% accuracy. See our Disclaimer for what the audit results mean and what they do not mean.

All 9 FDA major allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame. Sesame was added as the ninth major allergen effective January 1, 2023 under the FASTER Act and is included in every audit. For a detailed breakdown of each allergen and where it commonly appears on menus, see our allergen reference page.

Re-run the audit whenever your menu changes. Free accounts get one audit; Pro accounts include unlimited audits per location. The Pro audit log keeps every version, so you can track what changed between runs and demonstrate a consistent compliance history over time. If you update menu descriptions to address flagged items, re-auditing is the only way to confirm the flags have been resolved.

Not in the current version. The PDF reflects the audit output directly. Editing the report would defeat the purpose of a tamper-evident document. If your menu descriptions are the source of a flag, the right path is to update the menu descriptions themselves — adding ingredient detail that lets the engine make a confident determination — and then re-run the audit.

Pasted text: typically under 30 seconds for a standard restaurant menu. PDF upload: 1–3 minutes, depending on file complexity and whether text is embedded or needs to be extracted from an image layer. Image uploads follow the same range as PDFs. Very large menus (multiple pages, dozens of items) may take slightly longer.

No. The audit engine runs through Anthropic's API under commercial terms. Anthropic does not train its models on customer API data per those terms. Your menu content is used solely to produce your audit and is not used for any model training purpose. See our security page and our Privacy Policy for details.

Uploaded menu files are stored in Vercel Blob on US-East infrastructure, encrypted at rest. Audit results and metadata are stored in a US-East database. No menu data is stored outside the United States. See our security page for the full infrastructure breakdown.

Uploaded menu files are deleted from storage 90 days after upload. Your audit results and the per-dish matrix are retained in your audit log until you delete them or close your account. See our security page for the full retention schedule.

Yes. Cancel at any time from your account at /app/billing, which opens the Stripe customer portal. You retain access to all Pro features until the end of your current paid billing period. We do not require notice and there is no cancellation fee.

Annual plans: pro-rated refund on the remaining unused period if you cancel. Monthly plans: no refund on a partial month, but you can cancel at any time to stop future charges. If you believe you were charged in error, email hello@menuregistry.com.

A location is a single restaurant address with one associated menu. A franchise group operating 5 addresses under one brand has 5 locations. A single address that operates under two separate menus (for example, a restaurant with a separate bar menu and a dining room menu) counts as one location. Multi-location Group pricing covers 2–10 locations under one account. For more than 10 locations, email hello@menuregistry.com about Enterprise pricing.

Direct integrations with POS platforms and delivery aggregators are on the roadmap. The goal is to let a single verified allergen dataset propagate to every channel your menu touches without manual copy-paste. We are not committing to a specific timeline, but it is a core part of where the product is headed. If this is a priority for your operation, email hello@menuregistry.com — it helps us prioritize.

MenuRegistry is built against the federal 9-allergen standard and California's ADDE Act today. New York and Illinois have legislation in committee that mirrors California's ADDE framework. We will adapt the audit and reporting to cover those requirements when they become law. The federal 9-allergen base means any MenuRegistry audit already covers the floor that every forthcoming state bill is likely to require.

Not yet. A developer API for submitting menus and retrieving audit results programmatically is on the roadmap. If you have a specific integration use case — embedding audit results in your own platform, running batch audits for a large portfolio, or triggering re-audits on menu change events — email hello@menuregistry.com to get on the early-access list.