DiscoverBrowse CategoriesHow it worksMethodologyFor developers
Da Fit
MO YOUNG LIMITED · Lifestyle

What’s the catch? Nothing we could corroborate against this app.

Analyzed automatically from 6 independent signals that had to agree — not a hands-on test, and not human-reviewed.

0 on the catch list · analyzedConfidence: High6 signal sources833 reviews scannedNot human-reviewedas of 2026-10-04
 Which version this describes

This analysis describes version v2.5.0-124-g92d6b1c68-dirty of the app (the version number recorded inside the package we inspected), analyzed 2026-10-04 . The app may have changed since.

The store currently lists version 2.9.24-104-ge898488cf6, updated 2026-10-04.

What the analysis found

Each finding shows what agreed and how strongly. Automated analysis

Context 1

Measured and published because a reader would want to know — deliberately not a charge. The measurement alone does not show a harm.

Asks for more sensitive permissions than similar apps
MeasuredPublished as context — deliberately not a charge · from the app manifestartefact 9c4532ee8cdb…
The package requests substantially more of the device's sensitive permissions than the typical app in its category. This is a measurement, not an accusation: a permission is granted because a feature needs it, and a wide request list is a reason to look rather than a finding on its own.
What we saw: Requests 12 sensitive permissions (ACCESS_BACKGROUND_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION, CAMERA, READ_CALENDAR, READ_CALL_LOG, READ_CONTACTS, READ_EXTERNAL_STORAGE, READ_MEDIA_IMAGES, READ_PHONE_STATE, READ_SMS, RECORD_…

Positive evidence 1

Things this app does right, published at the same strengths as the catch list.

Developer says data deletion can be requested
Measuredfrom the store listingview evidence
The developer's data-safety disclosure on the store states that users can request deletion of their data, or the app's own text offers a way to delete the account. This restates what the developer declares; it is not a test of whether deletion works. Apple publishes no equivalent disclosure, so on an Apple-only listing only the app's own text can support it.
What we saw: The developer's store data-safety disclosure states that data deletion can be requested; we have not seen a deletion control in the app's own text

One source only — shown, not confirmed 1

A single kind of evidence. We publish these because withholding them would be the bigger distortion, and we do not treat any of them as a finding we stand behind.

Reported by users: Aggressive ad load
One source onlyShown, not confirmed — the only source is user reviews.view evidence
Advertising volume or placement that interrupts normal use: ads between every action, unskippable or forced full-screen ads.
What we saw: Aggressive ad load: raised by 19 distinct reviewers (2.3% of 833 reviews scanned)

What reviewers said

Verbatim excerpts from public store reviews, shown as corroborating user reports. They are not Appworthy audit evidence, and a quotation is not proof of the finding it sits under.

Aggressive ad load

watch is pretty good, however, now being spoilt by pop up adds telling me I have viruses which is untrue. dafit should be more selective on the advertising it provides as it is seriously damaging their reputation. I am very close to…

4★ · Google Play · 2026-10-05

How the automated analysis works

Automated, corroborated, and never human-reviewed without a person.

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.

 Not yet human-reviewed

Several measurements above say “Not assessed” because no artefact we hold can answer them. A human review is what resolves those — and it can remove a favourable band as easily as add one.

Hands-on inspections are not yet open.

 How this page was produced
Analyzed 2026-10-04 Version analyzed: v2.5.0-124-g92d6b1c68-dirty6 independent signals833 reviews scannedConfidence: HighNot human-reviewedVocabulary v1.13Methodology v1.3
Signals run: 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.