Google has announced a redesign in the next release of Chrome 97 interface for managing data stored on the browser side. In the "Settings > Privacy and Security > Site Settings > View permissions and data stored across files" section, the new interface "chrome://settings/content/all" will be applied by default. The most noticeable difference in the new interface is the focus on setting permissions and clearing all Cookies on the site at once, without the ability to view detailed information about individual Cookies and selectively delete Cookies.
In the opinion of Google, access to the management of individual cookies for a normal user who does not understand the intricacies of web development can lead to unpredictable violations of the operation of sites due to the inadvertent change of individual settings, as well as to the accidental disabling of cookie-activated privacy protection mechanisms. For those who need to manipulate individual Cookies, it is recommended to use the storage management section in the web developer tools (Applocation/Storage/Cookie), which is designed for professional web developers, but is not as clear and understandable for ordinary users as the old "chrome" interface. ://settings/siteData".
Additionally, we can note the identification of a problem with the publication of users of their browser profiles on GitHub. One of the security researchers noted that there are about 4 repositories on GitHub with the cookies.sqlite binary file containing the Cookie base from Firefox (for Chrome, you can also find similar files on GitHub, but the study focuses on Firefox). The cookie base file also contains session identifiers that allow access to the user's account on various sites. The motives for users to publish their browser profiles on GitHub are not entirely clear, it is likely that they use GitHub as a platform to migrate basic settings.
Source: opennet.ru