Some warnings 1 confirmed warning. Checked: 400 reviews, the Android app’s code, the store listing and the privacy label.
From our automated analysis, 26 Oct 2026. Every label links to its evidence in the full report below.
This analysis describes version 1.28.0 of the app (the version number recorded inside the package we inspected), analyzed 2026-10-26 .
The store currently lists version 1.28.0, updated 2026-07-29.
Store screenshots supplied by the developer.
Fitdays, the painstaking effort of ICOMON's App development team which integrated more than 30 years experience of the weighing measurement industry, the App has been upgraded iteratively for more than 5 years in the Big Health Data. Verified by more than 3 million users worldwide, it has a variety of scientific models which could match different regions and ethnic differences more accurately.
Fitdays provides the faster and more accurate insight into body compositions, and helps with health management for better life.
● 13 Core Data
Analyzing body compositions
● Girth Chart Record
Helping with better bodybuilding
● Measurement Instructions
Guiding step by step
● Trend Chart
Tracking every changes of body
● Family Use
Full support up to 24 users
● 15 App Colors
Popular colors of choice…
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.
The store privacy disclosure (5 entries) names no tracking or advertising use, but the package ships 2 advertising/tracking SDKs: Meta (Facebook) SDK, Umeng
Tracking or advertising SDKs are present in the package that the store's own privacy disclosure does not account for.
Specific evidence of a useful property, within the stated scope.
No advertising or mediation SDK among the 2 SDKs detected in the package
No advertising or mediation SDK of any kind was found in the package.
Package artefact
Appworthy
sha256:823acfd5ca6ab9c2255b5056c390216160e3131970a746cee88f6cd5248f0e34Open observations that have not cleared the evidence bar.
The app's own text says: "After agreeing to the authorization, the original account will be frozen and cannot be logged in until the migration is completed."
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:823acfd5ca6ab9c2255b5056c390216160e3131970a746cee88f6cd5248f0e34The app's own text says: "Continue as %1$s"
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:823acfd5ca6ab9c2255b5056c390216160e3131970a746cee88f6cd5248f0e34The app's own text says: "Can be measured when the APP is not opened"
This observation has not cleared the required evidence standard.
The app's own copy describes working without a connection — offline mode, downloading for offline use, or content saved for later. Shown because readers filter on it; it is a feature, not a fairness property, and never counts for or against an app.
Package artefact
sha256:823acfd5ca6ab9c2255b5056c390216160e3131970a746cee88f6cd5248f0e34No 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.28.0, scanned 26 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.28.0 of the app (the version number recorded inside the package we inspected), analyzed 2026-10-26 .
The store currently lists version 1.28.0, updated 2026-07-29.
Each store’s release notes, as the developer wrote them. They are the developer’s words, not ours.
No release notes were provided for this version.
fitdaysAssessed 2026-10-26 from 400 user reviews, the app's package, the store listing and its privacy label.
What the stores publish. Store ratings are the stores’ numbers, not Appworthy’s, and are never averaged across stores.
No itemized purchase list is available for this listing.
This assessment is produced automatically. Six independent signals are read — user reviews, SDKs in the app package, the app's own on-screen text, the app manifest, the store listing and the store privacy disclosure — 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 subscription bills weekly; 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.