Privacy

Effective 21 September 2026

The app

Nothing DirWiz scans ever leaves your Mac. File names, folder names, paths, sizes, scan results, snapshots and settings are stored locally on your Mac and stay there.

DirWiz contains no analytics, no crash reporting and no accounts. It sends no telemetry about what you scan or what you do in the app.

Reading your disk requires the Full Disk Access permission, which you grant in System Settings and can revoke there at any time.

DirWiz never asks for your name, your email address or any other personal details. The version from this site asks for a license key once the free trial ends.

When the app goes online

This part is about DirWiz 2.0 and later, downloaded from this site. Versions 1.x made no network connections at all.

The app talks to one server, api.dirwiz.app, which I run. It connects at these times:

• When you click Activate or Deactivate in the License window.
• Once a day, to look for a newer version. You can switch this off in Settings under Updates.
• When you choose Check for Updates yourself.
• When you click Install and Relaunch in the update window, to download the new version.

It never connects at any other time. There are no license checks in the background. Once a Mac is activated, DirWiz keeps working with no connection at all.

When a newer version is found, Install and Relaunch downloads it from api.dirwiz.app inside the app, checks that the file is exactly the one my release signed and that it is signed by the same developer, replaces the app in your Applications folder and reopens it. Nothing installs by itself: the check only tells you, and the install always needs your click. Buttons such as Buy, Download and Release notes open a link in your web browser. The link goes to api.dirwiz.app or dirwiz.app first, which may send your browser on to another site, such as the reseller's checkout page. The app does not load those pages itself. A Download link opened from the app carries the same details as the update check (build, macOS version and chip type), so that you get the right file.

What is sent

When you activate or deactivate a license, the app sends:

• Your license key.
• A one way hash that identifies the Mac, so that activations can be counted. It is derived from the Mac's hardware identifier. The identifier itself never leaves your Mac.
• A label such as "Mac 3FA9C1". It is never your computer's name.
• The app version and build number, and the number of the license format the app can read (currently 1).
• When you deactivate, the activation id that this Mac was given when you activated it.

When the app looks for a newer version, it sends the app version, the build number, your macOS version and the chip type (Apple silicon or Intel). That request carries no license key and no device hash. When you click Install and Relaunch, the download that follows is a plain request for the file and carries nothing else.

The app sends no cookies and keeps none. Nothing about your files, folders or scan results is part of any request.

Like any web request, these reach the server from your IP address. The server sees the address while it answers. It is not stored with any of the data above.

Who handles it and what is kept

Cloudflare hosts this website and my license service. As with any hosting provider, it processes standard request data such as your IP address to deliver the answer and to protect the service.

My service checks every license key with the payment reseller that issued it. To activate a Mac, it sends the reseller the license key and the label. To deactivate one, it sends the license key and the activation id, which the reseller issued in the first place. The reseller's answer to an activation includes the name and email address on the order. My service discards them. It does not store or log them.

For each activation my service stores a hash of the license key, the device hash, the activation id, and when the record was made and last used. They are there so that reinstalling DirWiz on the same Mac does not use up another activation. Deactivating a Mac deletes its record. My service does not store the license key itself, your name, your email address or your IP address.

My service also keeps daily totals: how many downloads of each build, how many clicks on Buy and which button or link they came from (this site, the app or a link in an email), how many update checks from each build, how many activations worked or failed, and how many deactivations. These are plain counts. They contain no license keys, no device hashes, no IP addresses and nothing else that points to a person or a Mac.

If you want an activation record removed, write to me and I will delete it.

The Mac App Store version

The Mac App Store version, when available, makes no network connections at all. This is more than a promise. That build has no network permission, so macOS itself blocks any connection it could try to make. It has no License window and it does not look for updates, because Apple handles the purchase and the updates. If you want a DirWiz that is fully offline, that is the version to get.

This website

dirwiz.app is a static site. It sets no cookies, runs no analytics or tracking scripts, and loads nothing from other companies' servers. Like any website, the hosting provider (Cloudflare) processes standard request data such as your IP address to serve pages and to protect the site.

Download and Buy links go through api.dirwiz.app. It adds one to the daily totals described above and then sends your browser on to the file or to the reseller's checkout page. A Buy link also tells the checkout which button it came from (for example "site"), so that tag shows on the order. I do not collect or keep anything beyond that.

Buying DirWiz

Purchases on dirwiz.app are handled by an online reseller that acts as the merchant of record. The reseller collects your payment details, your email address and your billing address, and its own privacy policy covers them. The checkout page names the reseller and links to that policy. I never see your card details.

I can see the order in the reseller's dashboard: the name, email address and billing address you gave at checkout, and whether the payment went through. I use them only to help with an order, a refund or a lost key.

After you pay, the reseller sends your browser to dirwiz.app/thanks with your license key, your email address and a payment reference in the page address, so that the page can show you the key. The page reads them inside your browser, removes them from the address bar straight away, and does not store them or send them anywhere. Like any page address, it passes through the hosting provider (Cloudflare) when the page loads.

Email

If you write to me, I receive your email address and whatever you send, and I use it only to reply. It is never shared or added to any list.

Changes

If any of this ever changes, this page changes first, with a new date at the top.

Contact

support@dirwiz.app · Okan Erturan, trading as Tilqui