Key Takeaways
- A gluten-free diet does not hand an app a number to chase. It hands it a yes or no question about every single item, which is a different job from counting.
- "Gluten-free" on a package is a voluntary claim. Under the FDA rule it means less than 20 ppm of gluten, and the regulation does not require the manufacturer to test for it.
- The allergen line is not a gluten line. Wheat is one of the nine major food allergens that must be declared in the United States. Barley and rye are not, so malt, malt extract, malt vinegar and brewer's yeast can sit in an ingredient list with nothing flagged.
- Whole aisles sit outside that rule. The NIDDK notes it does not apply to meat, poultry and some egg products, which are regulated by the USDA, nor to most alcoholic beverages.
- The most useful field for this diet is one almost no app has: how a dish was prepared and by whom. Cross-contact happens after the label is printed.
The question usually arrives short. I cannot eat gluten, what do I put on my phone. It sounds like the question someone on a diet asks, and it is not, because you are not trying to land near a number by the end of the day. You are answering the same question over and over, in a supermarket aisle, in front of a menu, in somebody else's kitchen: can I eat this, yes or no.
Almost every food app on the shelf is a calculator, and a calculator is the wrong shape for a yes or no. This page does not rank apps. Rankings go stale in a season, and the right pick depends on how strict your own situation has to be. What follows stays true longer: what a label actually guarantees, why the allergen field will not do the work you want it to do, a checklist you can run inside an app store in a few minutes, and a seven-day test that settles it on whatever you already have installed.
Why a yes or no goal breaks a calculator
A calorie tracker is a device for approaching a number from one side. Every design decision follows from that: a daily budget, a bar that fills, a total that resets at midnight. None of those decisions helps with the question a gluten-free diet asks, and several of them get in the way.
| What a calorie app is built around | What a gluten-free day is actually made of |
|---|---|
| One target you get close to by evening | A separate verdict for every item that goes in the basket |
| A wrong entry moves a total by a little | A wrong entry is the one thing the log existed to catch |
| You log after eating | You need the answer before eating, in the aisle or at the counter |
| Portion size is the variable that matters | The ingredient list and the preparation are the variables that matter |
| A food is a row of numbers | A food is a claim, an ingredient list, a factory and a kitchen |
| Yesterday's entry is still correct today | Recipes get reformulated, and a claim belongs to a package, not to a brand |
None of this makes a tracker useless. It means the thing you need it to do has moved, and the app worth keeping is the one that moved with it.
What a gluten-free label guarantees, and what it does not
Most of the confusion about gluten-free apps is really confusion about labels, so it is worth having the rules in front of you before you judge any software. In the United States the term is defined by regulation, and the definition is narrower than most people assume.
The claim is voluntary. The FDA defined the term and established conditions for its voluntary use in food labeling. A product without the claim is not a product with gluten in it. The agency says as much: producers of foods that are free of gluten by nature, such as bottled spring water, fresh fruit and fresh seafood, may simply choose not to say so on the pack.
The threshold is a threshold, not a zero. A food labelled "gluten-free", "no gluten", "free of gluten" or "without gluten" must not contain an intentionally added gluten-containing grain, and any unavoidable presence of gluten in the food must be less than 20 ppm.
Nobody is required to test. Asked directly whether manufacturers must test for gluten to make the claim, the FDA answers no. Manufacturers are responsible for compliance and may test, and the agency enforces through post-market monitoring, sampling and inspections. Testing is a choice they make, not a box they had to tick before printing the box.
The claim belongs to a product, not to a company. The same document is blunt about this: if a manufacturer uses the claim on some of its foods, that does not mean every food it makes is free of gluten. Any app that lets you mark a brand as safe is teaching you a habit the regulation does not support.
Put those four together and you get a table your app should behave according to.
| What you see | What it actually means | What an app should do with it |
|---|---|---|
| "Gluten-free", "no gluten", "free of gluten", "without gluten" | Less than 20 ppm gluten under the FDA regulation, claimed voluntarily | Store it as a claim with the date you saw it, not as a permanent property of the product |
| No claim anywhere on the pack | Nothing in either direction. Naturally gluten-free foods often carry no claim at all | Send you to the ingredient list rather than to a red verdict |
| "Contains: wheat" | Wheat is a major food allergen and its source must be declared | Treat as a stop, and never treat its absence as a pass |
| No "contains" statement | Says nothing about barley or rye, which are not major food allergens | Search the ingredients for malt, malt extract, malt vinegar and brewer's yeast |
| "Made in a facility that also processes wheat" | A voluntary advisory. The FDA does not prohibit it on a label that also bears a gluten-free claim | Keep it visible inside the entry. It is information, not a verdict, and the decision is yours |
| A third-party certification logo | The certifier's own standard, which is separate from the FDA claim | Record which certifier, because the number behind the logo is not the agency's number |
| Meat, poultry and some egg products | USDA-regulated. The NIDDK notes the FDA rule does not apply to them | Not assume one rule covers the whole database |
| Most alcoholic beverages | Regulated by the Treasury Department, also outside the FDA rule | The same, and beer deserves its own caution because it is brewed from malted grain |
| "Gluten-free" on a restaurant menu | The regulation covers packaged foods. The FDA recommends that restaurants making the claim be consistent with its definition | Record what you were told and by whom, because no database can verify a kitchen |
The allergen field is not a gluten field
This is the single most common way a food app gets a gluten-free user in trouble, and it is a structural mistake rather than a bug. Apps inherit allergen data from product databases, and allergen data in the United States is built on a list that was never a gluten list.
Congress passed the Food Allergen Labeling and Consumer Protection Act in 2004, and it identified eight foods as major food allergens. The FASTER Act added sesame, effective at the start of 2023. The FDA states the current list plainly: the major food allergens are milk, eggs, fish, Crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame. Wheat is on it. Barley and rye are not.
So a label that carries no "contains" statement has told you something about wheat and nothing at all about the other two gluten grains. The NIDDK spells out where the second one usually hides: barley may be found in malt, malt extract, malt vinegar, and brewer's yeast. The FDA adds that malt vinegar is made by fermenting an infusion of barley malt and therefore cannot be used in a food bearing a gluten-free claim at all.
The same NIDDK page lists the other quiet route in. Many ingredients and additives, including colourings, flavourings, starches and thickeners, are made from gluten grains, which is why gluten turns up in candy, condiments, hot dogs and sausages, ice cream, salad dressing and soups. None of those categories looks like bread, and none of them will trigger an allergen warning unless wheat is involved.
The checklist: what a gluten-free app has to do
Nine things. The first four decide whether the app can answer your question at all. The rest decide whether you are still using it next month.
- An ingredient list inside the entry. Not just calories and macros. If an app cannot show you what is in the product, it cannot help you decide anything, no matter how good its charts are.
- A verdict you can trace. When the app says gluten-free, it should be able to say why: because the pack carries the claim, because a certifier says so, or because a person typed it in. A verdict with no origin is a guess wearing a badge.
- A search that knows the aliases. Wheat travels under durum, emmer, semolina and spelt. Barley travels as malt, malt extract, malt vinegar and brewer's yeast. Triticale is a wheat and rye hybrid. An app that only matches the word gluten is checking spelling, not food.
- A wall between "no wheat declared" and "gluten-free". These are two different statements and an app should never derive the second from the first. See the test in the box above.
- Somewhere to record preparation and provenance. A shared fryer, a shared toaster, a dish a kitchen made gluten-free on request. The NIDDK defines cross-contact as gluten reaching gluten-free food, and notes it can happen when foods are grown, processed, stored, prepared or served. Almost all of that happens after the barcode.
- Editable entries with a visible source. You will find wrong data. The question is whether you can correct it, and whether you can tell a verified entry from something a stranger typed in. Even the reference databases pass data through: USDA FoodData Central states that information in Branded Foods is received from food industry data providers, so an app is usually showing you a manufacturer's own text rather than an independent reading of the product.
- Barcode scanning that fails into the ingredient list. Scanners miss, and products get reformulated between the scan and the shelf. What matters is where the miss lands: on a readable list, or on a confident number pulled from a similar product.
- A safe list you build yourself. This diet is repetitive by design, because once something is verified you buy it again. If your app has no way to keep a personal list of items already checked, you will re-check the same yoghurt every fortnight and then stop using the app.
- Export. CSV or anything you can open elsewhere. The list of products you have verified is the asset you are building here, and it should outlive your interest in any one app.
Notice what is not on that list: photo recognition, streaks, coaching, a recipe feed. They can be pleasant. None of them tells you whether the sauce on the shelf in front of you has barley in it.
A seven-day test
Install one candidate, not four. Seven days, one question each day.
- Day one, your own shelf. Scan five packaged items you already own. Count how many gave you a readable ingredient list rather than only a macro panel.
- Day two, the aliases. Search the app for malt extract, semolina, brewer's yeast and triticale. If it treats them as ordinary words with no connection to gluten, you have learned what the search is worth.
- Day three, the allergen trap. Find a product with barley malt and no wheat, and see what the gluten-free filter says. This is the test that separates an allergen field from a gluten check.
- Day four, the aisle. Take a product you have never bought before and count the taps to a yes or no. Then check whether the answer came with a reason attached.
- Day five, somebody else's kitchen. Log a meal you did not cook, including what you were told about how it was prepared. If there is nowhere to put that, the app only works in your own house.
- Day six, the safe list. Try to answer one question inside the app: which products have I already verified. If the answer takes longer than scrolling your own memory, the app is not saving you anything.
- Day seven, exit. Export the week and open the file. Then decide: did this app answer questions before meals, or only describe meals afterwards. Only the first kind is worth a place on your home screen.
Red flags
- A gluten-free filter that gives a verdict with no explanation of where the verdict came from.
- A verdict derived from the allergen field. It cannot see barley or rye.
- A photo estimate that returns a safe or unsafe answer about a cooked dish. A photograph cannot see a shared fryer.
- Entries that carry macros but no ingredients, especially for sauces, dressings, soups and processed meat.
- Brand-level trust: one product carrying the claim marking a whole manufacturer as safe.
- Supplements or enzyme products sold inside the tracker. Once the app has something to sell you, its advice has a second job.
- No export, and no answer about where the food data came from.
When a note on your phone is enough
If you shop in the same two shops and cook the same dozen dishes, an app is optional. Keep a note with the products you have verified, the brands that have let you down, and the questions that work on a waiter. That is a complete system and it costs nothing.
A tool starts earning its place when the variety goes up: travel, eating out, a shared kitchen, a canteen you did not choose. That is also when a weak database and a slow logging flow start costing you actual meals. If you are working on the food side first, our gluten-free weekly meal plan covers the cooking, our gluten-free guide to campus dining covers the case where somebody else runs the kitchen, and what AI meal planner apps actually do covers the category one level above this question.
What we are building
BeCute is being built against the checklist above rather than against a calorie budget: the ingredient list where you can read it, a verdict that says where it came from, a personal list of items you have already verified, and a place to write down how a dish was prepared when the answer came from a person rather than a package.
What is not true yet: you cannot install BeCute tonight and run the seven-day test on it. That is exactly why the test above is written for whatever is on your phone right now.
If you want to hear the day that changes, put your email on the early access list. One email, no drip campaign.
FAQ
What should I actually look for in an app for a gluten-free diet?
An ingredient list you can read inside the entry, a verdict that tells you where it came from, a search that recognises malt, semolina, spelt and triticale as gluten, and somewhere to record how a dish was prepared. Everything else is decoration. If an app shows only calories and macros, it cannot answer the question you are asking it.
Can I trust an app's gluten-free filter?
Only as far as it will tell you what it is reading. Many filters are built on allergen data, and in the United States that data is built on a list of nine major food allergens which includes wheat but not barley or rye. A product with barley malt and no wheat is the case that exposes the difference, and it is worth testing deliberately before you rely on any filter.
Does a "gluten-free" label mean there is no gluten at all?
No. The FDA rule allows an unavoidable presence of gluten below 20 ppm, the claim is voluntary rather than mandatory, and manufacturers are not required to test in order to make it. It is a meaningful standard, and it is a standard rather than a zero. The FDA also notes that a claim on one product says nothing about the rest of that manufacturer's range.
Why does my app show no allergens on a product that contains malt?
Because malt usually comes from barley, and barley is not one of the major food allergens that must be declared in the United States. The NIDDK lists malt, malt extract, malt vinegar and brewer's yeast as places barley shows up. An app that equates "no allergens declared" with "no gluten" will keep making this mistake in the same direction.
Do gluten-free rules cover restaurants and meat products?
Not in the same way. The FDA regulation applies to packaged foods, and the agency recommends that restaurants making a gluten-free claim on a menu be consistent with its definition. The NIDDK notes the rule does not apply to meat, poultry and some egg products, which the USDA regulates, nor to most alcoholic beverages. An app that treats every entry as equally regulated is flattening a distinction that matters in the shop.
Can I use BeCute for this today?
No. BeCute is in early access and there is nothing in the app stores to install yet, so the honest answer is that you cannot run the seven-day test on it. What we can tell you is what it is being built to do, which is the checklist above. If you want to be told the day that changes, the early access list is the whole mechanism.
Sources
- U.S. Food and Drug Administration. "Questions and Answers on the Gluten-Free Food Labeling Final Rule" (voluntary claim under 21 CFR 101.91; unavoidable gluten less than 20 ppm; testing not required; a claim on one product does not cover a manufacturer's whole range; malt vinegar; packaged foods and restaurants). fda.gov
- U.S. Food and Drug Administration. "Food Allergies" (FALCPA 2004, the FASTER Act, and the list of nine major food allergens). fda.gov
- National Institute of Diabetes and Digestive and Kidney Diseases. "Eating, Diet, & Nutrition for Celiac Disease" (grains that contain gluten; barley in malt, malt extract, malt vinegar and brewer's yeast; hidden ingredients; cross-contact; testing before starting the diet; foods outside the FDA rule). niddk.nih.gov
- USDA Agricultural Research Service. "About FoodData Central" (Branded Foods information is received from food industry data providers). FoodData Central
Written by
Oleksandr PaduraFounder & CEO at BeCute
Oleksandr Padura is the founder of BeCute. He built BeCute to make personalized nutrition planning accessible to everyone through AI technology.
Published: 2026-08-24
Disclaimer: This article is for informational purposes only and is not a substitute for professional medical advice, diagnosis, or treatment. Always consult a qualified healthcare provider before making changes to your diet or health routine.