That's odd; it's working fine for me, and presumably is also for the few dozen other users.

My only wild guess is that they were pre-existing cookies; CookieMaster doesn't *delete* existing cookies, just prevents them being set in the first place (well, javscript-set cookies are deleted immediately after they're set, but it's close enough)

If it's not that, and you're available to help debug this further, please get in touch with me by e-mail: cookiemaster@stroppykitten.com, or by raising an issue on github: https://github.com/craigmiskell/cookiemaster/issues and we can delve deeper into what's going on.

Edit: Just released 1.0.2 that fixed a bug related to third party cookie handling, that *might* have been responsible for the behaviour you saw.