VMoreCloud › Windows Server 2025 › Group Policy › Brave Browser
WINDOWS SERVER 2025 • GROUP POLICY • BRAVE BROWSER • ADMX

How to Deny Domain Users from Clearing Browsing History in Brave Using GPO On Windows Server 2025

Brave is built on Chromium, so it honors Chromium-style policies. This guide shows how to add the Brave policy templates to your domain, set the AllowDeletingBrowserHistory policy to Disabled, and confirm on a client that users can no longer clear their browsing and download history.

Author: Khurram Shahzad
Platform: Windows Server 2025, Windows clients
Technology: Group Policy, ADMX/ADML
Management: GPMC, PowerShell
Level: Intermediate
Reading Time: 10 minutes
Deny domain users from clearing browsing history in Brave using Group Policy on Windows Server 2025

Keep Brave history intact with one Group Policy setting

Brave reads policies from the BraveSoftware\Brave registry path. Load Brave’s ADMX templates into your domain, disable “Enable deleting browser and download history”, and every targeted computer picks it up through normal Group Policy refresh.

GPO
What this tutorial covers Downloading Brave’s policy templates, installing them in the domain Central Store, creating and linking a GPO, disabling history deletion, verifying the policy in Brave, optional hardening for private windows, a PowerShell alternative, and troubleshooting.
01

Add the templates

Brave publishes ADMX/ADML files so its policies show up in the Group Policy editor.

02

Disable one policy

Set “Enable deleting browser and download history” to Disabled in a dedicated GPO.

03

Verify on a client

Use brave://policy to confirm the policy is active, then test the Clear browsing data dialog.

Introduction

Organizations sometimes need browsing history to stay on the machine: for acceptable-use reviews, incident investigations, compliance or simply to stop users wiping evidence of a problem. By default, anyone using Brave can open the Clear browsing data dialog and delete their history.

Because Brave is Chromium-based, administrators can control it with the same kind of policies used for Chrome and Edge. The relevant setting is AllowDeletingBrowserHistory. Disabling it prevents users from deleting browsing and download history.

Example scenario In the vmorecloud.com lab domain, the security team wants staff laptops running Brave to keep a usable browsing history. You create a GPO on the Windows Server 2025 domain controller, disable history deletion, link it to the staff OU and verify the result on a domain-joined client.
Know the limits first This policy stops users from deleting history through the browser’s own interface. It is not a tamper-proof audit log. Microsoft’s documentation for the equivalent Edge policy notes that history is still not guaranteed to be retained, because users can edit or delete history database files directly and the browser itself can expire or archive items. If you need reliable records, pair this with network-level logging.

How It Works

ComponentRole
Brave ADMX/ADML templatesDescribe Brave’s policies so they appear in the Group Policy editor
Central Store (PolicyDefinitions)Domain-wide location where Group Policy tools read template files
GPOHolds the setting and is linked to an OU, domain or site
Registry pathHKLM\SOFTWARE\Policies\BraveSoftware\Brave
Policy nameAllowDeletingBrowserHistory; a value of 0 means Disabled
Client refreshGroup Policy writes the value; Brave reads it and applies it

Brave’s own documentation explains that Brave policies live under the BraveSoftware\Brave registry path, and it publishes policy templates in ADMX/ADML format for Windows.

Requirements

  • A Windows Server 2025 domain controller (lab example: server.vmorecloud.com) with the Group Policy Management Console
  • Domain Admin or equivalent rights to edit the Central Store and create GPOs
  • Brave installed on the domain-joined client computers you want to control
  • Client computers running a Windows edition that supports Group Policy (Home editions do not)
  • An OU containing the target computers (or users) for testing
Test first Create a test OU with one computer and one test user before you link the GPO to production OUs.
1

Step 1: Download the Brave Policy Templates

Brave publishes its policy templates on its support page for Group Policy. Download the policy templates ZIP file from there, then extract it on the domain controller.

Brave Support → Group Policy → Download Brave policy templates

Inside the extracted folder you will find the Windows templates. The ADMX definition file is in the windows\admx folder, with the matching ADML language files in a language subfolder such as en-US.

policy_templates\windows\admx\brave.admx policy_templates\windows\admx\en-US\brave.adml
2

Step 2: Copy the Templates to the Central Store

Copy the files to your domain’s Central Store so every administrator sees the Brave policies in Group Policy Management.

\\vmorecloud.com\SYSVOL\vmorecloud.com\Policies\PolicyDefinitions
  • Copy brave.admx into the PolicyDefinitions folder
  • Copy brave.adml into the PolicyDefinitions\en-US folder

If the PolicyDefinitions folder does not exist in SYSVOL yet, you can create it, or copy the files to the local folder on the machine you manage Group Policy from.

C:\Windows\PolicyDefinitions
Keep the ADMX and ADML together The ADMX file goes in PolicyDefinitions and the ADML file goes in the language subfolder. A mismatch is the most common reason the Brave node does not appear.
3

Step 3: Create and Link the GPO

Open Group Policy Management on the domain controller and create a dedicated GPO.

Server Manager → Tools → Group Policy Management

Right-click your target OU and choose Create a GPO in this domain, and Link it here. Name it so its purpose is obvious, for example:

Brave - Deny Clearing Browsing History

Use a separate GPO for this setting so you can enable, disable or roll it back without touching other browser policies.

4

Step 4: Disable Deleting Browser History

Right-click the new GPO and select Edit. In the Group Policy Management Editor, go to:

Computer Configuration → Policies → Administrative Templates → Brave

Find the setting named Enable deleting browser and download history. The easiest way is to use Filter Options in the editor and search for “history”, since folder layout can differ between template versions.

Open the setting, select Disabled, and click OK.

Why “Disabled” blocks deletion The policy is called “Enable deleting browser and download history”. Enabling it, or leaving it not configured, lets users delete history. Setting it to Disabled stops them.
Sync side effect Microsoft documents that disabling the equivalent Edge policy also disables history sync and open tab sync. Brave handles sync separately, so test how it behaves in your environment before you roll the policy out widely.
5

Step 5: Apply the Policy and Verify on a Client

On a domain-joined test computer, refresh Group Policy:

gpupdate /force

Then close all Brave windows and start Brave again. Verify the policy in the browser:

  1. Open brave://policy and click Reload policies. AllowDeletingBrowserHistory should appear with a value of false, set by platform policy.
  2. Open brave://management to confirm the browser reports it is managed.
  3. Press Ctrl+Shift+Delete to open Clear browsing data and try to delete browsing and download history. The deletion should not be available.

On the client, you can also confirm the registry value written by Group Policy:

reg query "HKLM\SOFTWARE\Policies\BraveSoftware\Brave" /v AllowDeletingBrowserHistory # Expected: AllowDeletingBrowserHistory REG_DWORD 0x0

To see which GPO delivered the setting, generate a report:

gpresult /h C:\Temp\gpreport.html
6

Step 6 (Optional): Block Private Windows and Tor

Denying history deletion does not stop users from browsing without saving history in the first place. Private windows do not record history, so consider restricting them in the same GPO.

  • Private windows: the Chromium policy IncognitoModeAvailability set to 1 disables private windows. Brave’s documentation uses this exact setting as its example.
  • Tor windows: Brave documents a Brave-specific policy, TorDisabled, where 1 disables Tor.

Find them in the Group Policy editor with Filter Options, or set them as registry values under HKLM\SOFTWARE\Policies\BraveSoftware\Brave.

Check your policy before you block Blocking private browsing can affect legitimate privacy needs and may have legal or HR implications. Confirm with your security and legal teams, and communicate the change to users.

PowerShell Alternative

If you prefer to build the GPO from the command line, or the Brave node does not show up in the editor, you can write the registry value directly into a GPO with the Group Policy PowerShell module:

# Run on the domain controller or a machine with RSAT Group Policy tools $gpo = New-GPO -Name "Brave - Deny Clearing Browsing History" Set-GPRegistryValue -Name $gpo.DisplayName ` -Key "HKLM\SOFTWARE\Policies\BraveSoftware\Brave" ` -ValueName "AllowDeletingBrowserHistory" ` -Type DWord -Value 0 New-GPLink -Name $gpo.DisplayName -Target "OU=Staff,DC=vmorecloud,DC=com"

Change the OU distinguished name to match your environment. This writes the same registry value the ADMX template would set, so it does not depend on the templates being installed.

Troubleshooting

The Brave node is missing in the editor

Check that brave.admx is in PolicyDefinitions and brave.adml is in the en-US subfolder. Reopen Group Policy Management after copying. If you see an XML parse error, review the template file Brave provided.

The policy does not appear in brave://policy

Run gpupdate /force, restart Brave fully and click Reload policies. Confirm the GPO is linked to the right OU, security filtering includes the computer, and the computer is in the scope you expect.

Users can still clear history

Check that the policy value is 0 under HKLM\SOFTWARE\Policies\BraveSoftware\Brave and that no conflicting GPO overrides it. Review the result with gpresult.

It works on some computers only

Look for computers outside the linked OU, Home editions that do not support Group Policy, or machines that have not refreshed policy yet.

History disappears anyway

Users can still delete history files directly, and the browser expires old history. For dependable records, add network-level logging or a web proxy.

Policy templates seem outdated

Download the latest Brave templates and replace the files in the Central Store. Brave’s documentation says the latest templates are always available from its Group Policy page.

Best Practices

  • Use a dedicated GPO for browser history controls
  • Test in a pilot OU before wide deployment
  • Keep the Brave ADMX files current in the Central Store
  • Document why the policy exists and who approved it
  • Combine the policy with network or proxy logging for reliable evidence
  • Use security filtering or OU scoping to target the right users or computers
  • Tell users that browser history controls are in place
Do not treat this as full monitoring Blocking deletion in the interface is one control. It does not capture or protect history if someone removes files directly or uses another browser.

Comparison of Deployment Methods

MethodBest forNotes
GPO with Brave ADMX templatesActive Directory domainsPolicies appear in the editor with descriptions
GPO registry value (PowerShell or Group Policy Preferences)Quick or scripted deploymentWorks without installing the templates
Intune with imported ADMXCloud-managed devicesBrave notes ADMX is the format used with MDM solutions
JSON policy file on macOS and LinuxNon-Windows devicesPolicy names and values are set in a JSON file in Brave’s managed policy folder

Frequently Asked Questions

What is the Brave policy that stops users deleting history?

AllowDeletingBrowserHistory, shown in Group Policy as “Enable deleting browser and download history”. Set it to Disabled (registry value 0).

Does this work for both browsing and download history?

Yes. The policy covers browsing and download history deletion.

Where is Brave’s policy registry path?

HKLM\SOFTWARE\Policies\BraveSoftware\Brave.

How do I check that Brave is receiving the policy?

Open brave://policy and click Reload policies, or open brave://management to see whether the browser is managed.

Can users still browse privately?

Yes, unless you also disable private windows with the IncognitoModeAvailability policy. Private windows do not save history.

Does this guarantee history is retained?

No. It blocks deletion through the browser interface only. Users can still modify files directly, and the browser can expire old items.

Do I need Windows Server 2025 specifically?

No. The steps work on any supported domain controller with Group Policy Management. This guide uses Windows Server 2025 because it is the lab platform.

Conclusion

Summary checklist Download Brave’s policy templates, copy the ADMX and ADML files to the Central Store, create a dedicated GPO, set “Enable deleting browser and download history” to Disabled, refresh policy on a test client and confirm it in brave://policy. Add private-window and Tor restrictions only if your policy requires them.

Want more Group Policy tutorials?

Explore practical Windows Server, Active Directory and Group Policy guides on VMoreCloud.

Explore more tutorials →

Sources & Further Reading

Khurram Shahzad, Hybrid Cloud & Virtualization Engineer and author at VMoreCloud
👤 About the Author
Khurram Shahzad
Hybrid Cloud & Virtualization Engineer
Hybrid Cloud & Virtualization Engineer specializing in VMware (VCF, vSAN, Aria), Microsoft Azure, AWS, Windows Server, Microsoft 365, Entra ID, Intune, Linux, Nutanix, Proxmox, networking, backup & disaster recovery, Cisco and FortiGate. I share practical technical guides, infrastructure projects and insights to help IT professionals build and manage modern IT environments through VMoreCloud.
🖥️ VMware🔷 Azure☁️ AWS🪟 Windows Server🐧 Linux🗄️ Virtualization🛡️ Cybersecurity🔗 Networking💾 Backup & DR✖️ Nutanix🟠 Proxmox
📄
120+
Articles Published
👥
10K+
Readers
🎓
Learning & Sharing
A Stronger Tech Community
View all articles →
“Learn  |  Build  |  Share”
☁️ VMoreCloud|Tech Knowledge for a Better Tomorrow
IT  •  Cloud  •  Virtualization  •  Security  •  Open Source

Technical note: Steps were written for a Windows Server 2025 domain controller managing Windows clients running Brave. Policy names, template layout and behavior can change between Brave versions, so confirm in brave://policy and test in a pilot OU before wide deployment.

Leave a Reply

Your email address will not be published. Required fields are marked *