Cookies do indeed persist across browsing sessions by default. A site's "remember me" option only controls the logic that site uses when determining what expiration date to give cookies it sets, and perhaps if the cookies a user presents when making requests are valid. This is expected behavior.

Chrome does offer you some control over this locally. For example, you could get closer to the state I think you're interested in by choosing to "Keep data only until you quit your browser" from the "Cookies" section of chrome://settings/content, and choosing "Open the new tab page" from the "On Startup" section of chrome://settings/.

(It's not clear from the bug description, but if it's the case that Chrome is sending expired cookies up to the server on request, then that's a real bug that we should address. Leaving this open to confirm that point.)

I'll close this bug. If Chrome doesn't respect cookie's expiration, please file a new bug to us. 

> -- If user is made to use not his own computer by, potential social exploiter may cut out electricity and make user go away from computer. Then, later when exploiter turns on computer back, he can get access to private data and etc. Can be done at home for friends, or bussines parters, internet caffe shops, and so on.

Please this: https://www.chromium.org/Home/chromium-security/security-faq#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-

Thank you!

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot