Service terms, as the service stands right now.
A short, honest page on what FUUEL offers today, what it does not yet offer, what we ask you not to do here, and where to write with questions.
What FUUEL offers today
Three things, only the first two are open.
The product ships in pieces. The free tier is open now; the personalized plan is waitlisted until Subscribe goes live.
The personalized plan joins the other two — under one subscription with no add-on pricing — the moment payments go live.
What FUUEL does NOT yet offer
The shape of the product, clearly stated.
Three lines that say plainly what is not on the table right now.
How submissions are handled
How the data you submit is handled.
What is stored when you join the waitlist, what is stored when you send a contact-form message, and how either row is removed on request, is described in full on the Privacy page.
The short version: each surface stores only what you typed in its fields, sends a best-effort notification to the operator, and is removed on a single written request. Read the full breakdown — including transports, retention, and what is not done with the data — on the Privacy page.
Acceptable use
What you may not do with this site.
The site is free to read and the forms are there for real sign-ups and real messages. The lines below describe the small set of behaviours that are not welcome here.
- No automated scraping, crawling, or harvesting of recipes, course content, or any other content on this site at a rate that exceeds normal human use.
- No automated submissions to the waitlist or contact-form endpoints — bulk sign-ups, form spam, address harvesting, or any similar abuse of either form.
- No abuse of either form — submitting content that is unlawful, harassing, defamatory, or unsolicited commercial.
- No attempt to reverse-engineer, decompile, or otherwise extract the source of the site, the visitor beacon, or any rate-limiting or abuse-detection logic.
- No commercial redistribution of the recipes or course content without the operator's written permission.
- No use of the service in any way that violates applicable law.
The operator may suspend, rate-limit, or block access — including by discarding submissions to either form — in response to any of the above.
No medical or nutritional advice
Recipes and the course are educational, not medical advice.
The recipes, the course, and the eventual personalized meal plan are educational and informational. They are not medical advice, not nutritional advice from a licensed professional, and not a substitute for individualized dietary or clinical guidance.
If you have a food allergy, intolerance, or other dietary restriction, a medical condition, are pregnant or nursing, are feeding a child, take medication that interacts with food, or have any other clinical dietary need, please consult a qualified professional — a registered dietitian, your physician, or another licensed provider — before following anything on the site.
The operator is not a healthcare provider. Nothing on this site is intended to diagnose, treat, cure, or prevent any disease or condition.
Disclaimer of warranties
The service is provided as is.
The service, the recipes, the course, the waitlist copy, and any other content on this site are provided "as is" and "as available".
To the maximum extent permitted by applicable law, the operator makes no warranty of accuracy, completeness, fitness for a particular purpose, non-infringement, or uninterrupted or error-free operation. The operator does not warrant that any nutritional information shown on the site is accurate for any specific ingredient, recipe, or dietary goal; that any recipe is suitable for any specific reader; or that the site will be available at any particular time or free of bugs.
Use of the site is at your own risk. If a term in this section is held unenforceable in your jurisdiction, the remaining terms still apply.
Limitation of liability
To the maximum extent permitted by law.
A short, plain-English cap on what the operator can be held liable for if something here goes wrong.
To the maximum extent permitted by applicable law, the operator is not liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, or other intangible loss, arising out of or related to your access to, use of, or inability to use the service — even if the operator has been advised of the possibility of such damages.
The operator's total aggregate liability for any and all claims arising under or related to these terms is capped at the greater of (a) the fees paid by you to the operator in the twelve months preceding the claim and (b) one hundred US dollars (US$100). Because no billing is collected today, in practice (a) is zero.
Nothing in this section is intended to exclude liability that cannot be excluded under applicable law — including liability for fraud, for death or personal injury caused by negligence, or for any other liability that applicable law says cannot be limited by contract.
Governing law and venue
Governing jurisdiction.
Which law governs these terms and where any dispute would be heard.
These terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws principles. Any dispute arising out of or relating to these terms or the service that the parties cannot resolve informally is brought exclusively in the state or federal courts located in Delaware, and you consent to personal jurisdiction in those courts.
If you are a consumer in a country that gives you the right to bring a claim in your local courts, nothing in this section removes that right.
A question about these terms.
If anything on this page reads wrong, write to fuuel@polsia.app — corrections land here, and the page is updated.
Effective date. This page applies from the date it was published and until it is updated.
Updates. As the product moves from waitlist to live Subscribe, this page is updated to describe what is then offered, what is now collectible, and how billing data is handled. The most recent change is reflected in the language above, not in a dated changelog — read the whole page.