Brave Browser: 1.96.61 to 1.99.55

[removed: Setting the ][added: This ]policy [removed: to True or leaving it unset gives users control of Autofill for addresses in the UI. Setting the policy to False means Autofill never suggests or fills address information, nor does it save additional address information that users submit while browsing the web.][added: is deprecated. Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

Setting the policy to 0 (the default) means you can access [removed: the developer tools ][added: Chrome DevTools ]and the JavaScript console, but not in the context of extensions installed by enterprise policy or, since version 114 and if this is a managed user, extensions built into the browser. Setting the policy to 1 means you can access [removed: the developer tools ][added: Chrome DevTools ]and the JavaScript console in all contexts, including that of extensions installed by enterprise policy. Setting the policy to 2 means you can't access [removed: developer tools,][added: Chrome DevTools,] and you can't inspect website elements. This setting also turns off keyboard shortcuts and menu or context menu entries to open [removed: developer tools][added: Chrome DevTools] or the JavaScript console. As of Brave version 99, this setting also controls entry points for the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed' (value 2), users cannot access source viewing via keyboard shortcut or the context menu. To fully block source viewing, you must also add 'view-source:*' to the URLBlocklist policy. As of Brave version 119, this setting also controls whether developer mode for Isolated Web Apps can be activated and used. As of Brave version 128, this setting will not control developer mode on extensions page if ExtensionDeveloperModeSettings policy is set. [added: This policy affects Chrome DevTools, direct Chrome DevTools Protocol (CDP) access (for instance, when launched with --remote-debugging-port or --remote-debugging-pipe), and Chrome DevTools Protocol (CDP) access via chrome.debugger APIs. Both this policy and the RemoteDebuggingAllowed policy apply: RemoteDebuggingAllowed controls whether remote debugging can start, while this policy restricts whether individual targets can be inspected even when remote debugging is running. ]The [added: DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies take precedence over this policy. The ]availability of [removed: Developer Tools][added: Chrome DevTools] is determined in the following order of precedence:[removed: ][added: ]1. If a URL matches a pattern in the DeveloperToolsAvailabilityAllowlist policy, [removed: Developer Tools][added: Chrome DevTools] are allowed. 2. If the DeveloperToolsAvailabilityAllowlist is set and the DeveloperToolsAvailabilityBlocklist is not, any URL not on the allowlist is blocked. 3. If a URL matches a pattern in the DeveloperToolsAvailabilityBlocklist policy, [removed: Developer Tools][added: Chrome DevTools] are blocked. 4. If [removed: a URL][added: neither policy] is [removed: not covered by the allowlist or blocklist,][added: set, or if a URL matches neither list,] this policy (DeveloperToolsAvailability) is [added: used as ]the [removed: fallback.][added: fallback mechanism.]

[removed: Specifies whether users can let Brave use Generative AI to better understand forms and help them fill more fields. 0 = Has the same effect as 1. Before M153, the setting allowed Google to use relevant data to improve its AI models. Relevant data may include prompts, inputs, outputs, source materials, and written feedback, depending on the feature. 0 is the default value, except when noted below. 1 = Allow the feature to be used, but does not allow Google to improve models using relevant data (including prompts, inputs, outputs, source materials, and written feedback). 1 is the default value for Enterprise users managed by Google Admin console and for Education accounts managed by Google Workspace. 2 = Do not allow the feature. If the ][added: This ]policy is [removed: unset, its behavior][added: deprecated. Its usage] is [removed: determined by the GenAiDefaultSettings policy. For ][added: discouraged. Read ]more [removed: information on data handling for generative AI features, please see https://support.google.com/chrome/a?p=generative_ai_settings.][added: at https://support.google.com/chrome/a/answer/7643500]

[removed: Setting the ][added: This ]policy [removed: to True or leaving it unset gives users control of Autofill for addresses in the UI. Setting the policy to False means Autofill never suggests or fills address information, nor does it save additional address information that users submit while browsing the web.][added: is deprecated. Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

This policy [removed: controls whether active WebSocket connections are disconnected when a page enters back/forward cache. Active WebSocket connections previously prevented a page from being stored in back/forward cache, but Brave has changed this behavior to disconnect the WebSockets instead, allowing the page to be cached and restoring it in a disconnected state. If this policy ]is [removed: set to Enabled or left unset, WebSockets are disconnected when a page enters back/forward cache. If this policy ][added: deprecated. Its usage ]is [removed: set to Disabled, WebSockets will not be disconnected when a page enters back/forward cache. Since back/forward cache does not support active WebSockets, this means pages with active WebSockets will not be cached. This policy is intended to be temporary and will be removed in the future.][added: discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Setting the ][added: This ]policy [removed: to True or leaving it unset means users can control autofill suggestions for credit cards in the UI. Setting the policy to False means autofill never suggests or fills credit card information, nor will it save additional credit card information that users might submit while browsing the web.][added: is deprecated. Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Setting the ][added: This ]policy [removed: to True or leaving it unset means users can control autofill suggestions for credit cards in the UI. Setting the policy to False means autofill never suggests or fills credit card information, nor will it save additional credit card information that users might submit while browsing the web.][added: is deprecated. Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: The Accept-Language HTTP request header and the JavaScript navigator.languages getter are planned for reduction for privacy reasons. To facilitate testing and ensure compatibility, this ][added: This ]policy [removed: allows you to enable or disable the Accept-Language Reduction feature. If this policy ]is [removed: set to enabled or left unset, Accept-Language Reduction will be applied through field trials. If this policy ][added: removed. It ]is [removed: set to disabled, field trials will ]not [removed: be able to activate Accept-Language Reduction. For more information about ][added: compatible with ]this [removed: feature, please visit: https://github.com/explainers-by-googlers/reduce-accept-language. NOTE: Only newly-started renderer processes will reflect changes to this policy while the browser is running.][added: version of Brave. Read more at https://support.google.com/chrome/a/answer/7643500]

This policy [removed: controls the visibility of the middle slot announcement on the New Tab Page. If the policy ]is [removed: set to Enabled, the New Tab Page will show the middle slot announcement if it ][added: removed. It ]is [removed: available. If the policy is set to Disabled, the New Tab Page will ]not [removed: show the middle slot announcement even if it is available. ][added: compatible with this version of Brave. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Setting the ][added: This ]policy [removed: to Enabled turns on Brave's Safe Browsing Extended Reporting, which sends some system information and page content to Google servers to help detect dangerous apps and sites. Setting the policy to Disabled means reports are never sent. If you set ][added: is removed. It is not compatible with ]this [removed: policy, users can't change it. If not set, users can decide whether to send reports or not. See ][added: version of Brave. Read ]more [removed: about Safe Browsing ( https://developers.google.com/safe-browsing ).][added: at https://support.google.com/chrome/a/answer/7643500]