A cleaneryou can trust.
It removes caches and uninstalls apps on macOS. What it may permanently delete is a fixed list decided before the release, not a judgement it makes about your files.
One license. macOS only, feature-complete, not released yet.
01Safe catalogueDelete
02Other removalsTrash
03Your filesNever touch
Three verdicts, decided before you run it.
A cleaner's screenshot tells you nothing about whether to trust it. The rule governing permanent deletion tells you everything.
Deleted for good
Only what is in the safe-category catalogue
A fixed list shipped with the release, holding clearly regenerable files. Membership never comes from looking at a file — it is decided before you run the app.
Moved to the Trash
Everything else it removes
App-managed state, orphaned leftovers, caches outside the catalogue. Recoverable, so a mistake costs you a restore rather than a file.
Never touched
Anything you made
User-created content is never searched for, suggested, or removed — even during an uninstall, and even when its name matches the app exactly.
Every other cleaner asks youto trust its judgement.This one shows you its list.
The safety is the product.
A fixed catalogue, not a guess
It may permanently delete only what is in its safe-category catalogue, a list shipped with the release. Nothing is ever judged safe by looking at the file itself.
The Trash, not oblivion
Anything outside that catalogue is moved to the Trash rather than deleted, so a mistake costs you a restore rather than a file.
It says how it knows
When uninstalling, a leftover is either a verified association — an exact bundle identifier, container or launch item — or a likely one, matched by name. The two never look the same on screen.
It hands off what is not its job
A Homebrew cask, a system extension, a login item: it names the right owner to act through instead of reaching in itself.
Nothing happens without a review.
01
It asks for access first
Full Disk Access is requested up front and explained, because a maintenance app that cannot see the disk will quietly under-report rather than fail.
02
You read the list
Every selected item, its size, and for an uninstall the evidence that ties it to the app, on one screen before anything is removed.
03
It reports what actually happened
The estimate before a run and the measured change in free space afterwards are two different numbers, and it shows you both.
Where it has got to.
Every screen is built. It has not been signed, notarized, or opened as a product yet.
- Platform
- macOS only
- Built
- Clean, Uninstall, Optimize, Storage, History, Settings
- Opened
- Not yet
- Released
- Not yet
The things people ask.
Can it delete something I wanted?
Permanent deletion is limited to the safe-category catalogue, which contains only clearly regenerable files. Everything else goes to the Trash, so it is recoverable.
What stops it touching my documents?
User-created content is never searched for, suggested or removed, even during an uninstall and even when the name matches the app exactly. That is a rule at the removal boundary, so it binds every screen rather than one.
Can I protect specific things?
Yes. The exclusion list is a set of paths and applications it may never remove, and it is enforced at the same boundary as everything else.
Why does it want Full Disk Access?
Because without it macOS hides most of what a cleaner is for, and an app that silently reports less than the truth is worse than one that asks.
Does it promise to make my Mac faster?
No. Optimize runs a named set of maintenance actions and reports what each one did. Speed is not a claim it makes.
When can I have it?
There is no date. Every screen is built. It ships when it is signed, notarized, and actually opened.
Not released.The risky half is built.
The removal core, its safety rules and its tests are built. The source is public. A download comes after someone has sat in the app.