Some warnings 1 confirmed warning. Checked: 61 reviews and the Android app’s code.
From our automated analysis, 31 Oct 2026. Every label links to its evidence in the full report below.
This analysis describes version 1.3.1 of the app (the version number recorded inside the package we inspected), analyzed 2026-10-31 .
The store currently lists version 1.3.1, updated 2026-07-21.
Store screenshots supplied by the developer.
TasteBot is an AI recipe generator that creates meals tailored to your goals, diet, allergies and cooking style.
Tell TasteBot how you like to eat and what you’re aiming for—building muscle, losing weight, low sugar, eating paleo, etc.—and every recipe is generated with those preferences in mind.
How it works
• Set your goals, diet, ingredients to avoid, and cooking style in a quick onboarding flow.
• Either type what you’re craving, ingredients you have on hand, or tap “Surprise me” to let TasteBot come up with ideas for you.
• Get a complete, easy-to-follow recipe plus nutrition you can use to track macros.…
From the developer’s store description.
For developers and the curious
The evidence, sources, measurements and versions behind every label above.
Findings that met the published evidence standard.
Paywall is server-configured and A/B tested via RevenueCat Paywalls, Superwall — the offer shown can differ per user
The app ships a remote paywall-experimentation SDK, so the offer shown is configured server-side and may differ per user — including from anything we or a reviewer saw.
Package artefact
Appworthy
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7Open observations that have not cleared the evidence bar.
Progress is gated behind watching an ad: "Watch an ad to generate for free"
This observation has not cleared the required evidence standard.
Advertising volume or placement that interrupts normal use: ads between every action, unskippable or forced full-screen ads.
Package artefact
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7Use is rationed by a refillable meter: "Out of energy"
This observation has not cleared the required evidence standard.
Use is rationed by an energy/hearts/lives meter that runs out and forces a wait or a purchase.
Package artefact
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7Cancellation copy routes the user away from a direct control: "Before you cancel, please consider accepting this offer"
This observation has not cleared the required evidence standard.
Cancelling the subscription is blocked, hidden, multi-step, or simply does not take effect.
Package artefact
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7Progress itself is for sale: "Get more energy"
This observation has not cleared the required evidence standard.
Advancement or competition is gated behind spending money rather than playing.
Package artefact
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7The app's own text says: "Thanks for your interest. We will share more once you're back online."
This observation has not cleared the required evidence standard.
The app's own screens offer a way past sign-up — guest access, skipping, or browsing before registering — rather than gating the product behind an account. The store's privacy disclosure is checked alongside it: that disclosure is self-reported, so it corroborates this credit rather than establishing it.
Package artefact
sha256:326edd9af98886d40f1fc2fa21c62ea42785d0895a10308c00fb0a68a3a70ca7No review-based observation is published in this assessment. That does not establish that reviewers had no problems.
“Not assessed” means we could not measure it. It is never a zero and never a pass.
Android package 1.3.1, scanned 25 Oct 2026. These describe that package, not the current store version.
Supporting measurements: not a complete list of possible harms or positives. Measurement vocabulary 1.4 · how these are measured
This analysis describes version 1.3.1 of the app (the version number recorded inside the package we inspected), analyzed 2026-10-31 .
The store currently lists version 1.3.1, updated 2026-07-21.
Each store’s release notes, as the developer wrote them. They are the developer’s words, not ours.
General performance improvements and bug fixes
No release notes were provided for this version.
tastebotAssessed 2026-10-31 from 61 user reviews and the app's package.
What the stores publish. Store ratings are the stores’ numbers, not Appworthy’s, and are never averaged across stores.
From the store listing. Billing terms are read from each purchase’s name — the stores don’t publish them — so treat them as a strong hint, not a disclosure.
This assessment is produced automatically. Four independent signals are read — user reviews, SDKs in the app package, the app's own on-screen text and the app manifest — and each candidate finding is filed under the sources that support it.
No charge stands on one kind of evidence — with one published exception. A finding is either a measured fact that anyone can reproduce (an ad SDK is in the package; every recurring plan the store lists is named as weekly, the term read from the purchase names, with a list cut off at the store’s 10-item maximum not assessed; the privacy label omits a tracker we can see), or it is an interpretation — and an interpretation needs independent sources to agree before it reaches the catch list. The exception is a harm only users can see: a charge may publish from reviews alone, as “Reported by N users”, once enough reviewers raise it to clear that charge’s own published bar. That agreement rule is what replaced the human reviewer, not a model’s confidence.
There is no overall score, on purpose. A 0–99 number was published here until 2026-09-15. It was withdrawn because it discriminated too weakly to be the instrument — 44.7% of every pair of apps tied — and because a single number is a verdict where a count is an observation. What publishes instead is a row of measurements, each of which says what was counted and, where we could not look, says that instead.
Findings under One source only are real reports we do not stand behind as findings. They are shown because withholding them entirely would hide a genuine complaint, and labelled because publishing them as charges would be an accusation off a single source.
Write to [email protected], or use the form. Name the finding, the app version and the evidence that needs correcting. Factual corrections are free and never depend on buying anything.