Looking through the Chromium source code, it looks like it may be related to this? https://blog.chromium.org/2020/02/samesite-cookie-changes-in-february.html h

Looking through the Chromium source code, it looks like it may be related to this? https://blog.chromium.org/2020/02/samesite-cookie-changes-in-february.html https://blog.chromium.org/2020/02/samesite-cookie-changes-in... The reason I say this: This test case appears to suggest that Google intentionally adds google owned domains to `managed_legacy_cookie_access_allowed_for_domains`: https://chromium.googlesource.com/chromium/src/+/b9c645c0b167a38b8f93b6c9e9f5a6a2f3e854ae/chrome/test/data/policy/policy_test_cases.json https://chromium.googlesource.com/chromium/src/+/b9c645c0b16... The Chrome source code shows that this settings adds CONTENT_SETTING_ALLOW to these "legacy" cookies (LEGACY_COOKIE_ACCESS): https://source.chromium.org/chromium/chromium/src/+/master:components/content_settings/core/browser/content_settings_policy_provider.cc;drc=73556cb05064dba1639e1154a66f76e885365eea;bpv=1;bpt=1;l=86 https://source.chromium.org/chromium/chromium/src/+/master:c... Elsewhere, it seems that `CONTENT_SETTING_ALLOW` causes cookies to be persisted even when you enable "Clear cookies and site data when you quit Chrome".