Terms of Service

flavorarchitect.dev · The University of Arizona · Nutritional Sciences & Wellness Foods Lab

Last updated: October 8, 2026

flavorarchitect.dev is an Open Educational Resource built by the lab's recipe prototyping work. Using it means you agree to the terms below. They are written in plain language and kept short on purpose; if anything here is unclear, contact the lab before relying on it.

Using the tool

The tool is free, needs no account, and asks for no personal details. You may use it for teaching, study, research, and your own kitchen experiments. You are responsible for the briefs you enter, the prototypes you save, and anything you publish from them.

The tool sees only what you type and select. What it stores, where it goes, and how to have it removed is described in the Privacy Policy — read that page together with these terms.

Research prototypes, not clinical advice

Every Lab Prototype is a research-grade teaching prototype: a gram-based starting point built to show how molecular flavor bridges and dietary guidelines interact. It is not a prescription, a meal plan, a medical nutrition therapy order, or a validated clinical intervention.

A prototype has not been tested by the lab unless you test it. Recipes are not costed, not batch-tested, not shelf-life tested, and not certified for any allergen claim. If you have a medical condition, are pregnant or breastfeeding, take medication that affects diet, or are feeding someone who does, confirm any prototype with a Registered Dietitian or your clinician before eating it regularly.

Do not present a prototype as clinically validated, as university dietary guidance, or as a treatment for any condition.

Food safety is yours to manage

Prototypes name ingredients and general method, but the tool does not verify kitchen conditions. Follow standard safe-handling practice: cook proteins to the internal temperatures in the USDA Food Safety and Inspection Service charts, treat raw eggs and raw flour as unsafe until cooked, refrigerate prepared food within two hours, and store finished meals in food-safe containers.

Allergen cross-contact is a real risk in any kitchen: a prototype that excludes an allergen is not allergen-free unless your ingredients and surfaces are. Shared fryers, cutting boards, and utensils can reintroduce what the recipe left out.

The shared library and what you contribute

Every prototype you generate is saved to a single shared, public library that anyone with the site address can browse, compare, and copy. There is no private or draft space.

By generating a prototype you confirm that the brief is yours to share, that it contains no personal information about yourself or anyone else, and that nothing in it is confidential, contractual, or owned by a third party. You keep ownership of what you write. You grant the lab a non-exclusive permission to host, display, and archive the result so the classroom exchange can work.

You may remove a prototype at any time with the Delete control on its card in the Library. Removal is immediate and cannot be undone, so copy anything you want to keep first. The lab may also remove entries that break these terms.

Nothing protected by FERPA — student records, grades, rosters, assignments, disability or accommodation detail — may be entered here. The library is not a protected record system; see the Privacy Policy for the full notice.

Generative AI use: disclosure and citation

This disclosure follows The University of Arizona Research Integrity Program's Generative AI in Research guidance, the Professional Conduct Policy (UHAP 7.01.04), and the Code of Academic Integrity.

How AI is used here. Every Lab Prototype — the molecular pairing, the DGA/Culinary Medicine audit, the gram-based formulation, method, and nutrition estimates — is drafted and synthesized by generative AI (Google Gemini 2.5 Flash). Grocery lists, prices, and aisles are AI estimates. Sensory and spoon-level tags are assigned by an OpenAI model. The site itself was built with AI-assisted coding (Lovable) under the lab's direction.

Your responsibility. You are ultimately responsible for any work that uses a prototype. Check every value against USDA FoodData Central and the cited sources before relying on it. Enter only public information: follow the university's Information Resource Classification Standards, and never enter confidential, regulated, or FERPA-protected data.

When you must disclose. Under the Resnik & Hosseini (2026) scheme the university references, disclosure is mandatory when AI helps design experiments, generates content or data reported in your work, or analyzes or interprets data. Using a prototype as a recipe, formulation, or nutrition figure in a paper, poster, course material, or grant application falls in that category: describe the tool, how you used it, and how you verified it, and cite it as shown below. Follow your funder's rules as well — NSF and NIH both bar GenAI tools from peer review and expect AI use to be described in proposals.

Keep documentation. Save your brief and the full prototype output (Copy Summary or Print/PDF), just as you would keep raw data, so you can show how AI was used if the work is questioned.

Sample disclosure: "Recipe formulations were generated with flavorarchitect.dev (Google Gemini 2.5 Flash) on [date] from a researcher-written brief, then reviewed and verified by the authors against USDA FoodData Central."

Reusing a prototype: license and attribution

Prototypes and their documentation on this site are released under Creative Commons BY-NC-SA 4.0. You may copy and adapt them for non-commercial use, provided you give attribution and release your version under the same license.

Attribution line: flavorarchitect.dev, Alan Pruitt, UA Designated Campus Colleague (DCC), and Michael J. Clark, SNS, MPA — The University of Arizona · Nutritional Sciences & Wellness Foods Lab.

In a reference list, cite the tool as: Pruitt, A., & Clark, M. J. (2026). flavorarchitect.dev [AI-assisted recipe prototyping tool]. The University of Arizona · Nutritional Sciences & Wellness Foods Lab. https://flavorarchitect.dev

Cite the lab's open textbook as: Casey, C., Going, S., Hingle, M., & McCullough, L. (Eds.). (2024). Culinary medicine (2025 ed.). University of Arizona. https://opentextbooks.library.arizona.edu/culinarymedicine/

Commercial licensing, white-labelling, or resale of prototypes generated here needs written permission from the lab. Source data the tool draws on — USDA FoodData Central, the 2020–2025 Dietary Guidelines for Americans, and the lab's open textbook Culinary Medicine (© 2024 Arizona Board of Regents, CC BY-NC 4.0) — should be cited alongside the tool; the USDA sources remain in the public domain.

Acceptable use

Please do not:

  • Enter personal information about a student, patient, client, or anyone who has not agreed to it — including names, ID numbers, or health details tied to a person.
  • Use the tool to build a competing commercial service, or to resell generated prototypes without permission.
  • Overload, scrape, or probe the tool or its services in ways that degrade it for other users, or attempt to bypass its access controls.
  • Use it to produce content that is unlawful, harassing, or that misrepresents a prototype as verified clinical guidance.
  • Use The University of Arizona's name, marks, or the lab's name to imply endorsement of a product, diet, or service.

Estimates: nutrition, prices, and equipment

Nutrition figures, molecular compound matches, shelf-price estimates, and aisle suggestions are model-generated approximations aimed at the sources and the store area you set. They are useful for comparison and teaching, and they are not guarantees. Verify nutrition values against USDA FoodData Central, and confirm prices and availability in store before purchasing or publishing.

Estimated prices are not quotes from a specific store, and aisle order varies by location. Equipment suggestions assume nothing: where a tool is named, an alternative is offered so a prototype stays usable in the kitchen you actually have.

The nutrition figures are teaching approximations. They are not an FDA-compliant Nutrition Facts panel and may not be used as one — on a packaged product, a menu, or anywhere else a regulated label is required.

Availability and changes

The tool is provided for educational use and may be modified, paused, or withdrawn at any time, including for reasons outside the lab's control. No uptime is promised. Keep copies of anything you need — the library is an archive for sharing, not a storage service for your records.

No warranty and limits on liability

The tool and its outputs are provided as is, without warranty of any kind, to the fullest extent the law allows. You choose what to cook, feed to others, publish, or teach from, and you are responsible for those decisions. To the extent permitted by law, the lab and The University of Arizona are not liable for loss or damage arising from use of the tool or from acting on a prototype.

The University of Arizona policies

This tool is operated under the policies of The University of Arizona, and these terms are governed by the laws of the State of Arizona. The University of Arizona and its marks belong to the university; using this tool does not transfer any right to them. Nothing here is a statement of university policy or an official university position.

Changes to these terms

If the tool's behavior or these terms change, this page is updated and its "Last updated" date changes. Because the tool collects no email addresses, material changes are noted on the site itself rather than announced privately. Continuing to use the tool after an update means you accept the current version.

Contact

Questions about these terms, permission requests, or a prototype in the library: contact Alan Pruitt, UA Designated Campus Colleague (DCC), The University of Arizona · Nutritional Sciences & Wellness Foods Lab at alanpruitt@arizona.edu. You can also reach the tool at flavorarchitect.dev.

These terms describe how the tool currently operates. They are published as an educational resource and are not legal advice — before the lab offers the tool commercially, charges for it, or collects personal data, they should be reviewed against the applicable institutional and state requirements.