Uninstall DingTalk on Mac

Before removing DingTalk (钉钉), check which required conversations and files you can actually access through your organization’s account. Locate downloads using the installed version’s actual settings or the folder you chose when saving, copy wanted files to an independent location and open the copies; do not assume either cloud sync or the support folder below contains everything. These steps cover the official installer from DingTalk's site and the Homebrew cask dingtalk, which installs the same .pkg under bundle id com.alibaba.DingTalkMac; the recorded test used the Homebrew cask. The Mac App Store build uses a different bundle id and was not tested here.

Before moving the app, locate its FinderSync or share extension identifier. In Finder, use Show Package Contents on DingTalk.app, open Contents/PlugIns, and inspect each .appex's Contents/Info.plist for CFBundleIdentifier (read the plist with Quick Look or a plist editor). If no embedded extension is present, skip this step. Substitute the identifier actually read for <extension-id> in ~/Library/Containers/<extension-id> and ~/Library/Application Scripts/<extension-id>, inspect those exact folders and remove only data belonging to the extension you are uninstalling. Keep other extensions and the parent folders.

Quit DingTalk and remove the app

Quit DingTalk from its menu, then move DingTalk from Applications to the Trash. DingTalk commonly adds itself as a login item; open System Settings › General › Login Items & Extensions and turn it off there if you do not want it opening at every login, since removing the app does not always clear that entry by itself.

Where DingTalk keeps its data

Most of these paths come from the Homebrew DingTalk cask's zap list, which matches what the official .pkg installer writes to the same locations; the crash-reporter leaf Caches/KSCrash/DingTalk and the FinderSync extension's Container and Application Scripts folder are not in that zap list at all, so they survive even a zap you run yourself outside Mole, and only Mole's own review reaches them.

Check the result

Run these read-only commands in Terminal:

pgrep -ilf DingTalk
ls -d "$HOME/Library/Application Support/DingTalkMac"
pkgutil --pkgs | grep -i dingtalk

No output from pgrep means DingTalk is not running. The ls command proves only whether that local directory exists, not that downloaded files are intact. Inspect the actual files or a usable backup; "No such file or directory" concerns that path alone, and a permission or read error leaves the check unresolved. A com.alibaba.DingTalkInstaller line from pkgutil means the installer's package receipt remains; it is a record, not a running program.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

Running brew uninstall --cask --zap dingtalk yourself runs the cask's zap list on its own, regardless of what you ticked in Mole's review list. Because DingTalk installs through a .pkg, ordinary uninstall removes the files tracked by com.alibaba.DingTalkInstaller.app before forgetting that receipt and deletes the app directly, even without zap. Homebrew DingTalk cask

The zap list includes ~/Library/Application Support/DingTalkMac, so a zap removal also moves your local DingTalk data and downloaded files to the Trash, whatever you ticked in Mole. Save those files first, or remove only the app without zap:

brew uninstall --cask dingtalk

Account and subscription

Removing DingTalk does not sign you out of your account, and it does not remove you from any organization or team. What remains accessible through your organization’s account depends on its retention and access rules; verify required conversations and files before removing local copies rather than relying on uninstalling to preserve them.

What Mole lists

~/Library/Application Support/DingTalkMac is listed but unselected while Remove data and settings with apps is off, the default. Enabling it can preselect eligible app-owned data; untick this row to keep local files and settings. Caches, preferences, saved window state and WebKit data tied to DingTalk's own bundle id are selected by default; the installer helper's cache and preferences, the older com.dingtalk.mac preferences file, are listed as review rows, and the FinderSync extension's container is listed too. Mole does not manage the login item; turn it off in System Settings if it is still listed.

What this test covered

The recorded uninstall used the Homebrew cask on September 17, 2026, with a development build of Mole. The app and the zap list's paths were removed. The crash-report leaf Caches/KSCrash/DingTalk was left the first time and has been listed since. The FinderSync and share-extension containers stayed behind because macOS refused to move them, and the login item stayed listed in System Settings. Signing in and enterprise chat sync were not tested.