If you deployed the Nudge Security browser extension through your MDM, use that same MDM to remove it. Extensions installed by policy are locked in place, so end users can't uninstall them from the browser. Removal works by taking away the policy that installed the extension. Once the device picks up that change, the browser removes the extension on its own.

Please note: Every MDM and every browser handles extension removal a little differently, and vendors update their tools often. Your team knows your environment best, so you'll need to confirm the right removal steps for your setup. This article is a starting point, with links to each vendor's documentation to help you get there. We recommend testing the change on a single device before rolling it out broadly.

A Nudge Security extension deployment usually includes up to three pieces. Remove all of the ones you deployed so nothing is left on the device.

If Nudge is the only entry in a profile, you can usually unassign or delete the whole profile. If the profile also manages other extensions, edit it to remove only the Nudge Security entry.

Browser behavior can change between versions, so use the vendor references below to confirm current behavior for the browsers in your environment.

These browsers automatically uninstall an extension once it's removed from the force-install list. Brave supports the standard Chromium policies, applied through its own registry path on Windows and the com.brave.Browser preference domain on macOS.

Atlas supports a narrower set of MDM-managed preferences than Chrome, delivered to the com.openai.atlas.web preference domain. Remove the Nudge Security entries you deployed to that domain, then verify removal on a test device before rolling the change out broadly.

Deleting the Nudge Security entry from ExtensionSettings doesn't always uninstall the extension. To remove it reliably, change its installation_mode to blocked. You can clear the entry later if you want users to be able to reinstall.

The Nudge Security extension for Safari ships inside the Nudge Security Extension app, so uninstalling the app through your MDM removes the extension. If you used Apple's Safari extensions management configuration to keep the extension enabled, remove that configuration too. It applies to supervised Macs running macOS 15 or later.

Newer browsers such as Comet and Dia are evolving quickly, and their vendors haven't published detailed enterprise policy documentation yet. If you deployed the extension to one of these browsers, check with the browser vendor for current guidance on removing managed extensions, and test the change on a single device first. Nudge Security support is also happy to help you work through it.

The steps below describe the general approach for each MDM. Your MDM's own documentation is the authoritative source, so check it for the details that apply to your version and configuration.

Edit the configuration profile to remove the Nudge Security extension ID, or unassign or delete the profile. Do the same for the profile that delivers the managed configuration. For Safari on macOS, change the Nudge Security Extension app's assignment to Uninstall.

On Windows, how a removed setting is handled depends on the underlying configuration service provider (CSP). Some CSPs remove the setting, while others keep it, which Microsoft calls tattooing. If the extension remains after you unassign a custom OMA-URI profile, set the policy to Disabled, let devices sync, and then delete the profile.

Microsoft documentation: What happens when a profile is deleted or no longer applicable

Remove the target computers from the configuration profile's scope, or add them to the exclusions. The profile is removed the next time each computer checks in. Remove the scope before deleting the profile from Jamf Pro. If you delete the profile first, computers that haven't checked in yet may never receive the removal command. For Safari, remove the Nudge Security Extension app from scope as well.

Jamf documentation: Computer Configuration Profiles

Remove the Custom Profile Library Item that contains the Nudge Security policies from the Blueprints or Assignment Map branches it's assigned to. Do the same for the Nudge Security Extension app if you deployed Safari.

Iru documentation: Custom Profiles Overview and Library Overview

If you distributed the extension from the Browsers module, remove the distribution from the target groups. To actively remove it from devices, create an Add-on Management policy that includes the Nudge Security extension and select the option to remove the selected extensions where they're already installed.

ManageEngine documentation: Add-on Management and Distribute Extensions

Delete the configuration profile from Fleet, or move the hosts to a team where the profile doesn't apply. Fleet reverses a removed profile's settings automatically, sending SyncML Delete commands on Windows hosts.

Fleet documentation: Custom OS settings

Changes apply the next time each device checks in with your MDM. You can trigger a manual sync from your MDM console or on the device. To confirm removal on a device:

If the extension is still installed after a sync, check for a second profile that also force-installs it. On Windows, also check for a leftover registry policy under the browser's policy key, such as HKLM\SOFTWARE\Policies\Google\Chrome or HKLM\SOFTWARE\Policies\Microsoft\Edge.