dush for Mac, the command line and this website
Privacy Policy
dush for Mac collects nothing and sends nothing. This page says exactly what it reads, what it keeps and where.
Last updated
Who's responsible
Andrea Rinaldi is responsible for dush and for this site. Contact: gibbone-aromi-3e@icloud.com.
No data protection officer is appointed, because none of the cases that require one apply here.
What dush collects
Nothing. dush for Mac has no analytics, telemetry or tracking, no device identifiers, no accounts, no ads and no in-app purchases. It sends no crash reports. It shares nothing with anyone.
It works offline
dush for Mac works fully offline. The App Store version holds no network entitlement, the permission an app needs to connect, so macOS itself refuses any connection from it.
Notifications for watched folders are local too: macOS shows them on your Mac.
What it reads
To measure your disk, dush reads the names, sizes and dates of files and folders. It doesn't read what's inside your files.
Two things go further, and only when you ask for them:
- Quick Look is macOS's own preview. macOS shows the file, and nothing leaves your Mac.
- A report you open. When you open a JSON report written by
dush --json, dush reads that file, because showing it is what you asked for.
What it keeps
dush keeps these only on this Mac, in the app's own folder. It doesn't sync or upload any of them.
- Scan history: what you scanned, when, and the names, paths and sizes of the biggest items it found.
- Settings: your choices, including your watched folders and their limits.
- Remembered Apple Intelligence answers, with the details of the item each one is about, so the same question isn't asked twice.
- A read-only bookmark of the disk access you gave, so you don't have to give it again.
Clear History removes the saved scans, and only those. Your files aren't touched, and remembered answers and settings stay. In Settings › General you can keep scans for 30 or 90 days, or stop saving them.
Three more things to know:
- The scanning engine writes counts and timings to macOS's own log on your Mac. Paths and names show there as
<private>, and dush sends that log nowhere. - When you export a scan, the file goes where you save it. What happens to it next is up to you.
- A backup of your Mac, like Time Machine, can include the app's folder, as it can any other folder.
Disk access
macOS keeps apps out of your disk until you allow it.
- A folder you drop or choose needs nothing more.
- For anything else, you choose your startup disk once, in the system's panel. dush keeps that access read-only.
- Full Disk Access is optional. It lets dush measure the folders macOS keeps private, like the Trash and Safari's caches. Only you can turn it on, in System Settings.
Apple Intelligence
Apple Intelligence works only when you ask it about an item, and it runs on your Mac. dush gives the on-device model:
- the item's path and size, and whether it's a file or a folder;
- how many items sit directly inside it, and the names and sizes of the 10 largest;
- its last-modified date;
- in a follow-up, the conversation so far. The model can also ask for the same count, names and sizes for a subfolder of that item.
What sits inside and the date each have a switch in Settings › AI. Both start on. The model never gets file contents.
Items dush protects are answered locally and never given to the model, not even by name inside their parent folder: credentials and keys, system folders, iCloud Drive, and personal folders as a whole. You can still ask about a single item inside a personal folder.
The app shows what was asked, under the answer.
The App Store
Apple runs the App Store. Downloading dush there falls under Apple's Privacy Policy and App Store & Privacy, not this page.
Apple can give developers figures about their apps, which it says are aggregated and don't identify you. If you've turned on Share with app developers, in System Settings › Privacy & Security › Analytics & Improvements, Apple may also share crash data and other analytics with developers. That sharing happens on Apple's side, not in dush: the app sends nothing itself.
This website
This site has no cookies and no analytics, and it loads nothing from another site. Every file it shows comes from the same place as the page.
The one thing it keeps in your browser is the light or dark mode you pick with the button in the header. It sits in the browser's local storage under the name dush-theme, it is written only when you press the button, and it is sent nowhere. It's a setting you asked for, so the site needs no consent banner for it. Your browser's settings clear it, and the site works without it.
It's hosted on GitHub Pages. To answer a request, GitHub receives your IP address, the page you asked for, the time, and what your browser says it is. GitHub keeps those for security and to stop abuse, and it decides how long: the GitHub Privacy Statement gives the criteria and lists the companies GitHub uses. GitHub is the controller for that data. This site never sees those logs and keeps nothing of its own.
GitHub is in the United States. For data from Europe it relies on the EU-US Data Privacy Framework and on the European Commission's standard contractual clauses.
Links to other sites carry no referrer, so the page you came from isn't passed on.
If you write to us
Write to gibbone-aromi-3e@icloud.com and you share what you write, and your address. It's read, answered, and kept in an iCloud mailbox, so Apple stores it too. It's deleted 12 months after the last message.
Issues on Codeberg are public: anyone can read them, and search engines can find them. Codeberg's privacy policy covers what Codeberg does with them. The Support page says what to put in a report.
Answering an email rests on a legitimate interest: replying to people who write. Nothing else is done with what you send.
Your rights
For what you send by email, you can ask to see it, have it corrected, have it erased, have its use limited, or object to it being used at all. GitHub, Codeberg and Apple answer for their own data, under the statements linked above.
Write to gibbone-aromi-3e@icloud.com. It costs nothing, and you get an answer within a month.
If the answer doesn't satisfy you, you can complain to the Garante per la protezione dei dati personali, Piazza Venezia 11, 00187 Roma, Italy, or to the authority where you live.
The command-line tool
The dush CLI collects nothing either. It touches the network only in dush update, which looks up the latest release through git and upgrades through brew. A copy you built from source is fetched with git and built again with the Swift tools, which download what the build needs.
Changes to this policy
dush can't tell you about a change itself: it has no network and no accounts. So changes are announced here. This page gets the new text and a new date at the top, and its full history stays public on GitHub. If a change comes with a new version of the app, that version's notes on the App Store say so too.
This page is written in eight languages. If a translation ever disagrees with the English, the English is the one that counts.