The Cookies UI (which is really the Local Browsing Data) is located within the chrome settings, in the Content Settings, in the Cookies permissions. This is tradition, but let's consider where it should live. 

Here are some ideas on why Local Browsing Data should be moved out of Settings:

- Combining (conflating) Local Browsing Data with Cookie Permissions adds waiting time for the user to view/edit the Cookies permissions

- The Cookies permissions is a setting while the Local Browsing Data is loaded is not a setting. Let's avoid conflating them together.

- Referring to the Local Browsing Data as Cookies (or storing them under cookies permissions) has caused confusion (even for Chrome SWEs, so how would users navigate the subtle, yet important differences).

I may make sense to associate Local Browsing Data with the Clear Browsing Data UI. Local Browsing Data could be a peer with chrome://settings, chrome://extensions, chrome://downloads, etc. rather than a sub-item of chrome://settings.