How to uninstall Voicenotes on Mac

Voicenotes keeps your notes and recordings in your Voicenotes account; its FAQ says all notes are secured in the cloud. The Mac app itself leaves only small settings and cache folders behind, so the parts to handle are the permissions you granted it and the account, which removing the app does not touch. This guide covers Voicenotes from its official download and from the Homebrew cask voicenotes.

Before you remove it

1. Open Voicenotes and check that your latest recordings show up in your account on another device or on the web, so nothing is still waiting on this Mac.
2. Removing the app does not cancel a subscription or delete your account. Handle those in your Voicenotes account if you are leaving.

Quit Voicenotes and remove the app

1. Quit Voicenotes from the Voicenotes menu. In the recorded test it ran four processes, including Sparkle's Autoupdate, which Mole's Status page folded into one Voicenotes row.
2. Search Activity Monitor for Voicenotes and check that nothing is left.
3. Move Voicenotes from Finder's Applications folder to the Trash.

On first launch the updater loaded two short-lived session jobs, com.voicenotes.app-sparkle-progress and com.voicenotes.app-sparkle-updater; in the test both were gone after the uninstall. No login item appeared.

Remove the permissions you granted

Voicenotes' Mac guide asks for several permissions on first launch, including screen recording and accessibility, and has you add Voicenotes by hand if it does not appear in the list. macOS keeps those entries after the app is gone. Open System Settings › Privacy & Security, look under Microphone, Screen & System Audio Recording and Accessibility, select Voicenotes in each list where it appears, and click the minus button.

Where Voicenotes keeps its data

Check the result

pgrep -il voicenotes
launchctl list | grep -i voicenotes
ls -d "$HOME/Library/Application Support/Voicenotes" "$HOME/Library/Application Support/com.voicenotes.app"

• No output from pgrep means Voicenotes is not running.
• No output from launchctl list means no updater job is loaded. A com.voicenotes.app-sparkle line means an updater job from this login session is still loaded; it should not survive a log out or restart.
• ls -d prints each folder that still exists and reports "No such file or directory" for the rest.

If you installed it with Homebrew

The voicenotes cask's zap list is ~/Library/Application Support/Voicenotes and the preferences file. brew uninstall --cask --zap voicenotes moves them to the Trash. Your notes are in your account, not in either one. To remove only the app:

brew uninstall --cask voicenotes

Mole adds --zap only when every path on the zap list sits inside ~/Library, none of them touches a row you left unchecked, and no other installed app claims them. ~/Library/Application Support/Voicenotes is listed but not selected by default, so Mole leaves --zap out unless you tick that row.

What Mole lists

For Voicenotes from the official download:

• ~/Library/Application Support/Voicenotes is listed but not selected. Its logs folder is a separate row selected by default.
• ~/Library/Application Support/com.voicenotes.app, the caches, HTTP storage, preferences and temporary caches filed under com.voicenotes.app, Caches/SentryCrash/Voicenotes and the Crashlytics cache for the app are selected by default.
• Privacy permissions are not files and are not listed; remove them in System Settings as above.

What this test covered

On September 26, 2026, Voicenotes 2.0.7 was installed from its official zip, opened once without signing in, and uninstalled with a development build of Mole with every row ticked. Status showed one Voicenotes row with four processes using about 77 MB. Ten items went to the Trash, including both Application Support folders, the Sentry and Crashlytics caches and the preferences file, and nothing from the list was left on disk. The two Sparkle session jobs from the first launch were gone after the uninstall. Earlier, on September 22, 2026, the same version was removed the same way without a failure. Signing in, recording, permissions and a Homebrew install were not tested.