Privacy
Quarry is a tool that reads its way through your development directories. That deserves a specific account, not a line about how much we value your privacy. Here is what it actually does.
It collects nothing and uploads nothing
Quarry has no account, no analytics, no crash reporting, and no server. Scan results, file paths, directory sizes, the names of your projects — all of it exists only on your own machine. None of it ever leaves the device.
It does not request Full Disk Access
Quarry does not ask for Full Disk Access. What it reads is developer storage — Xcode derived data, simulators, archives, package caches, and the project roots you add yourself.
That choice has a cost, and it belongs here rather than buried: Quarry cannot check when your backups last succeeded, because that needs the permission it does not request. So confirm your backups are current before removing anything — Quarry will not pretend to know.
The one network request: checking for updates
Quarry makes exactly one kind of network request — asking
quarry.liuzhekan.com for an update manifest. It contains which
versions exist. It contains nothing about you.
That request is off by default. Quarry asks on first launch, and you can say no.
Honestly, even that one request is not zero information. Like any HTTP request, the server sees:
- your IP address
- when the request happened
- your Quarry and macOS versions, carried in the User-Agent
None of it is used for analysis or shared with anyone, but it does exist, so it is written down here. Decline the check and not even this happens.
Updates are verifiable
Every update is signature-checked before it installs, so you know it came from us.
Quarry is still in development. This describes the mechanism as it will work once it ships.
Scanning changes nothing
A scan does not modify the contents, modification time, permissions, ownership, or location of anything it looks at. macOS advancing access times as a natural consequence of directory enumeration is unavoidable; Quarry neither writes it back nor "fixes" it, and never uses it as grounds for a cleanup suggestion.
Quarry does not delete files itself. Removal is always delegated to the tool that owns the data, with no force flags of any kind — those tools' refusal conditions are the safety property of this design. It never deletes local snapshots either: those are macOS's to manage.
Contact
Questions about any of this: milky.eggy@gmail.com.