idam reads your whole Mac, shows you what is actually taking up room, and tells you which of it is safe to let go of. You decide. It moves things to the Trash and never further.
idam after a full scan. Every figure here comes from your disk and stays on it.
The question
Where did my disk space go, and what here is actually safe to let go of?
Most cleaners answer the first half and guess at the second. idam ranks what deserves your attention, explains why, and then stops — because it is the only one of the two questions a program can honestly answer alone.
How it behaves
These are not settings. They are properties of the build.
Scan, analyse, recommend — then it waits. idam has no automatic cleanup, no scheduled sweep, and no button that removes something you have not looked at.
Removal goes through the macOS Trash, and that is the only removal path in the codebase — so there is no permanent-delete call to hit by accident. Emptying the Trash stays with you and Finder.
macOS does not reliably record when a file was last opened. Where idam cannot know, it says so, and that item stays out of the cleanup funnel instead of being padded into a bigger number.
idam ships without the network entitlement. Nothing about your filesystem leaves your Mac — not because of a policy, but because the app has no way to send it.
Measured, not estimated
Numbers from a real 400,000-file tree. Rescans are faster still: idam reads the filesystem's own change log, so an unchanged disk costs milliseconds rather than a second walk.
to walk, classify and index 400,000 files
files per second, sustained
peak memory — 64 MB of it a SQLite page cache idam asks for on purpose
sent anywhere, ever
Limits
Every storage cleaner has a list like this. Most of them keep it internal. Publishing it is the only way you can judge whether the recommendations are worth trusting.
trashItem is the only removal path that exists in the
source. There is no other code to call.
Getting started
The obvious objection
Because "where did my space go" cannot be answered from a folder. A storage analyser that only sees your Documents folder will tell you your Documents folder is the problem.
macOS has no way for an app to request Full Disk Access on its own, which is why the toggle is yours to flip and why idam has to explain itself first.