Use this before using chrome://settings/siteData
Not sure if this is still the case with current versions
One of the top comments in this thread suggests Chrome is a keylogger
https://thomascountz.com/2025/07/17/chromes-ssl-bypass-cheat...
This blog calls this a "cheat code". One could also call it a keylogger as that's what it feels like when using it; there's no display of the characters being typed
Using a local TLS forward proxy is a more effective way to control cookies than using Chrome settings. Of course, Google tries to make this more difficult with the requirement for the "cheat code" but typing into the keyloagger is not always necessary, not every site requires the "cheat code"