How DevCleaner keeps you safe

Risk levels

Every category is rated by how much you lose if you delete it and need it again. The rating drives both the color of its size bar and whether it is ticked by default.

• SAFE Pure caches that regenerate on the next build or launch. Pre-selected, because there is nothing to lose.
• WARNING Slow or tedious to rebuild: simulator runtimes, downloaded LLM model weights, package stores. Never pre-selected. Worth keeping if you use them often.
• DANGER Things that can break your development environment if removed. Never pre-selected, and selecting one asks for an extra confirmation.

Files that are never deleted

Some files look like cache but hold your identity or your work. DevCleaner refuses to delete them regardless of which category you select:

• Cookies, local storage and session files
• Credential files and saved logins
• SSH keys

Your logins are untouchable by design. Cleaning an editor or browser-based app will not sign you out.

Running-app protection

Deleting a cache out from under a running app is the classic way to break things, for example wiping Xcode's package checkouts in the middle of a build. If you try to clean an app that is currently running, DevCleaner warns you first and lets you cancel or proceed deliberately.

Pending app updates are protected

Self-updating apps stage their downloaded update in a folder that looks like leftover junk. DevCleaner leaves those updater staging folders alone during automatic cleanups, so an app like Claude Desktop installs its update correctly instead of losing it. You can still clear updater leftovers manually when no update is pending.

Locked files and the administrator retry

A few caches are protected by macOS permissions. DevCleaner fixes permissions where it safely can, and if an item still cannot be removed it offers an administrator retry. If anything still fails, it tells you exactly which items and why rather than failing silently. See troubleshooting for the details.