Public beta
Terms of use
The practical rules and cooking-safety expectations for using the No Fluff Dinner public beta.
By using No Fluff Dinner, you agree to use the beta responsibly and to review its output before relying on it. These terms are intentionally short and match the service that exists today.
A changing beta
This is beta software. Features, providers, limits, and output may change, pause, or stop working. The app can contain errors, produce incomplete results, or be unavailable. Not every publisher or recipe URL will import successfully, including pages that block automated access or do not expose usable recipe data.
Check every recipe before cooking
You must verify ingredients, allergens, food-safety instructions, cooking temperatures and doneness, serving sizes, and quantities before you cook, serve, or eat a recipe.
Imported pages can be incomplete or parsed incorrectly. AI-generated recipes can also be inaccurate or unsuitable for a dietary or medical need. Use reliable food-safety guidance and ingredient labels, and get qualified help when needed. No Fluff Dinner is a recipe-organizing tool, not medical, dietary, or professional food-safety advice.
Public recipe URLs only
URL import may be used only for public recipe pages you are allowed to access. Do not use it to reach or probe private, local, internal, login-protected, unauthorized, or unlawful resources; bypass access controls; or retrieve content in a way that violates another service's rules or rights.
Publishers, authors, and attribution
Recipe publishers and authors retain ownership of their content. An imported card is a cleaned-up working view of third-party material, not a transfer of ownership or a claim that No Fluff Dinner created the source recipe. Keep the displayed source attribution and original link with imported cards and exports. You are responsible for having the right to use and share content you submit or export.
Reasonable use of the service
Do not:
- overload, disrupt, scrape, or automatically call the service in a way that creates unreasonable traffic or cost;
- bypass rate limits, request protections, or other safeguards;
- submit malicious code, deceptive requests, or content intended to interfere with the service or another system; or
- use the service for unlawful activity or to violate rights.
Requests may be rejected or limited to protect the beta, its users, and its external providers.
Privacy and feedback
Read the Privacy page for current data behavior and the Beta information page for known limitations. Questions and feedback can start on the Contact page.