EFFECTIVE 2026-11-03

Privacy.

Dilated doesn't collect anything about you. There's no analytics, no telemetry and no account, in the app or on this site.

What stays on your Mac

Your settings, timers, history, statistics and holds live on your Mac and nowhere else. The direct build keeps them in ~/Library/Application Support/Dilated. The Mac App Store build keeps them in its sandbox container. Nothing is uploaded, and there's no copy on our side to ask for.

Permissions, and why Dilated asks

• Location. macOS only lets an app read the Wi-Fi network name if it has Location access. Dilated asks for it so a trigger can match the network names you pick. It doesn't request or record where you are.
• Bluetooth. Used to match the paired devices you pick for a trigger while they're connected. It doesn't scan for nearby devices or change their connections.
• Files and folders. Dilated reads only what you choose in an open panel: a download folder or file to watch, an app for a trigger, a custom sound. In the App Store build that choice is saved as a sandbox bookmark. Drive Alive writes a small hidden file to a drive's root, and only after you grant that drive.
• Notifications. Asked for only when you turn on banners.

Wi-Fi names, paired devices and chosen paths are read on your Mac to evaluate your triggers. They aren't sent anywhere.

Network use

The direct build checks for updates with Sparkle. It requests https://dilated.app/updates/appcast.xml and verifies the signed feed before installing anything. Sparkle's system profile option is off, so the request carries the usual HTTP details (your IP address, the app name and version, your macOS version) and no hardware or usage profile. Like any web host, ours can see that request in its server logs.

The Mac App Store build has no update code and makes no network requests. The App Store delivers its updates.

This website sets no cookies and loads no third-party scripts, fonts or trackers. Your browser fetches the page and, on the home page, a small file with the current release details, all from dilated.app.

Closed-lid companion

Closed-lid mode is optional. It needs a sudo rule limited to pmset -a disablesleep 0 and pmset -a disablesleep 1, and nothing else. The direct build installs the rule when you choose to. The App Store build can't run sudo from its sandbox, so it uses a separate Closed-Lid Setup companion that installs the same rule, a small script (dilated-power) and a LaunchAgent that restores normal sleep if the app disappears. All of it runs locally and none of it uses the network.

To remove them, use Remove in Dilated's Closed Lid settings, or in the companion. The direct build also has dilated lid-permission remove. By hand:

sudo rm /private/etc/sudoers.d/dilated
launchctl bootout gui/$(id -u)/com.codeswhat.dilated.closed-lid-repair
rm ~/Library/LaunchAgents/com.codeswhat.dilated.closed-lid-repair.plist
rm "$HOME/Library/Application Scripts/com.codeswhat.dilated.appstore/dilated-power"
sudo pmset -a disablesleep 0

Both builds share the sudo rule, so removing it turns closed-lid mode off in each. The installation guide has the full removal steps.

Contact

Questions about any of this: security@codeswhat.com. Dilated is MIT licensed and the source is public, so you can check these claims against the code.

Effective 2026-11-03. If this changes, the date changes with it.