One finding. One exact proof item. One independent recheck.
This two-minute fictional example shows what HatchCheck found, the bounded developer task, the screenshot returned, and the narrow result that screenshot established.
Before → fix → proof → recheck
What happened in this fictional App Checkup
Fictional example
Conflict found → Task sent → Proof received → Rechecked
Every fact in this visual comes from the fictional account-deletion example below. The returned screenshot supports only the recorded screen, build, and role—not navigation, whether deletion completes after confirmation, legal compliance, approval, or overall readiness.
- 1. Conflict found
Settings
No in-app deletion control was shown in the supplied screenshot.The recorded submission material said users could delete their account inside Settings.
- 2. Task sent
Exact developer task
Add a clear in-app account deletion path for the recorded app scope.
Return: Return one screenshot showing the in-app deletion path from account settings.
- 3. Proof received
Settings
In-app deletion path shownA current screenshot showed the in-app deletion path in fictional build 42 for the recorded founder role.
- 4. Rechecked
In-app deletion path established for the recorded scope
The in-app deletion path was established for fictional build 42 and the recorded founder role.
Still unknown
- • A public account-deletion URL was not checked for this finding.
- • Privacy and store wording were not checked for this finding.
- • Billing and paid access still need separate human review.
See the exact evidence and proof details
- Conflict found
Report v1
FitCoach Pro in-app account deletion path was not verified
The supplied Settings screenshot did not show an in-app deletion path, while the recorded submission material said users could delete their account inside Settings.
- What the supplied material shows
- No recorded in-app deletion control.
- What the submission says
- Users can delete their account inside Settings.
- Bounded task
Developer task
One bounded change with one exact proof item
- Finding ID / return code
- fitcoach-account-deletion-path
- Finding
- FitCoach Pro in-app account deletion path was not verified
- One bounded change
- Add a clear in-app account deletion path for the recorded app scope.
- Exact safe proof to return
- Return one screenshot showing the in-app deletion path from account settings.
Full fictional developer handoff
- What HatchCheck observed
- FitCoach Pro supports coach/client account creation. Uploaded Settings and Profile screenshots show logout and profile editing, but HatchCheck could not verify a Delete Account path.
Done when
- A person using the recorded role can reach a visible account-deletion path from inside the app.
- The screenshot shows the path and app scope requested by HatchCheck.
Handoff safety
Send safe summaries and report links only. Do not include secrets or private material: production secrets, private keys, signing certificates or other signing files, production .env files or other production environment files, credentials, tokens, app-store credentials, cookies, auth headers, customer data, payment data, private URLs, raw production logs, or raw sensitive logs.
Return only the evidence requested for this finding. Anything else remains outside this bounded recheck.
- Proof reviewed
Returned proof
HatchCheck could use the returned item in this recheck
Returned proof HatchCheck can use in this recheck
A current screenshot showed the in-app deletion path in fictional build 42 for the recorded founder role.
Outside this finding
Public deletion URLs, privacy wording, billing review, and behavior outside the recorded build and role were not part of this finding's recheck.
- Established for recorded scope
Report v2
In-app deletion path established for the recorded scope
HatchCheck inspected the returned screenshot and changed only the state supported by that exact item.
- Recheck result
- The in-app deletion path was established for fictional build 42 and the recorded founder role.
- Independent authority
- The developer response did not clear the finding; HatchCheck made the scoped recheck decision.
Still unknown
- A public account-deletion URL was not checked for this finding.
- Privacy and store wording were not checked for this finding.
- Billing and paid access still need separate human review.
Apple or Google approval, legal compliance, and behavior outside the supplied evidence remain not verified.