Feature shape
Advanced Cleaner
Advanced Cleaner should be careful and explain what will be removed before anything happens. The public page avoids magic cleanup claims and makes user review central.
Find temporary exports, failed package builds, old previews, duplicate reports, and cache files.
Show file type, size, path, age, source workflow, and effect before cleanup.
Backups, undo where possible, and excluded folders reduce accidental loss.
Avoid claiming system optimization or hidden-device cleanup beyond CRYA-owned/user-selected files.
| Best use | Clean CRYA temporary files, old package artifacts, duplicate previews, stale reports, and recover workspace space. |
|---|---|
| Do not promise | Do not claim universal speed boosts, battery fixes, malware removal, or system cleaning. |
| User consent | Destructive cleanup should show what will be removed and require user action. |
| Root paths | Root/system cleanup is risky and should be gated, documented, and recovery-first. |
| Support | If cleanup removes expected files, collect action history, file path, app version, and time. |
User workflow
How this utility should feel in the app
A CRYA utility should be useful, explicit about risk, and connected to support evidence when something fails.
Find CRYA-related cleanup candidates.
Check path, size, age, and workflow source.
Protect active projects, store submissions, and support evidence.
Remove only selected candidates.
Show freed space and remaining important files.
Related CRYA surfaces
Continue safely
Utility pages connect users to Toolkit workflows, docs, policies, and support without exposing protected admin controls.