Privacy and local data

DevSweep scans and hashes files locally. It requires no account. Licence validation uses a signed offline payload; no activation server is contacted. The app includes no advertising, telemetry or crash-upload SDK.

One exception, stated up front: DevSweep can check for its own updates. That check is off until you enable it, and it is described in full under Network behavior.

What is stored

Preferences, configured project folders, protected paths and the optional licence key: macOS UserDefaults for com.devsweep.DevSweep.
Cleanup receipts: ~/Library/Application Support/DevSweep/history.json. Receipts contain paths, item identifiers, dates, classifications, actions, results and regeneration guidance. They remain until you remove the history file. Corrupt history is preserved and blocks new cleanup rather than silently resetting the record.
Storage trends: one local capacity sample per day, retained for 90 days. Samples contain dates and free/total byte counts, not filenames. Use Settings → Clear trend to delete them.
Duplicate hashes and candidate paths: memory only for the current view; they are not uploaded or written as a scan database. Approved duplicate removals produce normal cleanup receipts.
Update preferences: whether automatic checks are enabled, and the date of the last check, in the same UserDefaults domain. The update signing key stored in the app is a public key only.
macOS may retain its own local crash reports according to system policy. DevSweep does not collect or transmit them.

Network behavior

DevSweep itself does not upload scan results, paths, hashes or source code. Git inspection uses local refs and does not fetch or verify the current remote state. Installed tools invoked by the app retain their own behavior. Homebrew auto-update and analytics are disabled for DevSweep commands. Some tool operations and subsequent regeneration may access their registries; offline regeneration is not guaranteed.

Update checks — the one exception

DevSweep can check whether a newer version exists. This is the only request the app makes, and it is the only part of DevSweep that is not local.

It is off until you turn it on. Settings → Updates. Nothing is checked before that.
What is sent: an ordinary HTTPS GET for the release feed. No identifier, licence key, scan result, path or machine profile is attached. System profiling is disabled in the bundle (SUEnableSystemProfiling is false). As with any web request, the host sees your IP address and the app version in the user agent.
Where it goes: the release host named in Settings, which is the same host the app was downloaded from.
What comes back: a signed list of releases. Every update is verified against DevSweep's Ed25519 update key before it is allowed to replace the app; an update that fails verification is discarded.
Nothing installs itself. Automatic download and automatic installation are both disabled in the bundle. An update is applied only when you choose to apply it.

This exists because DevSweep is not notarised and is not distributed through the App Store. Without an update channel, a safety defect in a tool that deletes files could not be corrected on a machine that already had it installed.

Checkout and remote crash reporting are not enabled. Any future network feature requires explicit configuration and an updated disclosure. Optional macOS notifications are local notifications, with no DevSweep push server.

Permissions and exclusions

Full Disk Access is optional. Skipped locations and incomplete measurements are shown. Choosing a folder for duplicate detection authorizes local inspection only; moving copies to Trash requires a separate confirmation. Protected personal locations and source trees are excluded from duplicate cleanup. Do not share receipts or exported screenshots unless you intend to disclose the paths they contain.