Hsid sub cookie for google.com needs to be deleted

[snowbound]

In the past Gmail allowed one to uncheck a remember me box so that cookies were current session only. Google changed that a couple of years ago. I have found that there is a hsid subcookie for google,com that if one sets it to a session only cookie or deletes that cookie on browser exit/restart then the user is forcibly logged out of the account. It has to be only this cookie that is deleted because with Gmail there are also 2FA cookies that are stored elsewhere so that doing a mass deletion causes 2FA to have to be reentered every time.

I have tried the following

but nothing happens. I am still logged in. What am I missing?

[kennethtran93]

Please ensure you have read the documentation, especially this portion which you were looking for: https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/wiki/Documentation#greylisting

we handle specific cookies a bit differently here. Only the domain goes under the domain expressions.

First you'll need *.google.com under a whitelist, uncheck Keep All Cookies and check all the cookies you want to keep but the hsid cookie.
Then you'll need a *.google.com under a greylist, uncheck Keep All Cookies until restart and only check the hsid cookie and/or any other cookies you want removed at browser startup.

[snowbound]

I have Enable Greylist Cleanup on Browser restart enabled and Enable Auto Cleanup. I had only the first one enabled and it did not do anything. I have

Yet it is touching other domains I do not want it to touch cookies for. I only want the extension to perform the clean up in the above and nothing more.

grammarly.com (gnar_containerId, grauth, csrf-token, experiment_groups, rtMf5RGKqL, yuhoaood48): Clean because of startup cleanup and grammarly.com is not in the White or Grey lists
github.com (_octo, logged_in): Clean because of startup cleanup and github.com is not in the White or Grey lists
google.com (SID, __Secure-3PSID, HSID, SSID, APISID, SAPISID, __Secure-3PAPISID, SIDCC, __Secure-3PSIDCC): Partial clean because of matched *.google.com in the Whitelist
accounts.google.com (LSID): Partial clean because of matched *.google.com in the Whitelist
youtube.com (SID, __Secure-3PSID, HSID, SSID, APISID, SAPISID, __Secure-3PAPISID): Clean because of startup cleanup and youtube.com is not in the White or Grey lists
google.ca (SID, __Secure-3PSID, HSID, SSID, APISID, SAPISID, __Secure-3PAPISID, NID): Clean because of startup cleanup and google.ca is not in the White or Grey lists
raindrop.io (__cfduid): Clean because of startup cleanup and raindrop.io is not in the White or Grey lists
bitwarden.com (__cfduid): Clean because of startup cleanup and bitwarden.com is not in the White or Grey lists
api.raindrop.io (AWSALB, AWSALBCORS): Clean because of startup cleanup and api.raindrop.io is not in the White or Grey lists

[kennethtran93]

We do not have specific domain cleanups at this time. That is a work in progress.

Your partial clean has taken effect, thus the cookies listed are the only ones cleaned in the partial cleanup.

At this time it is only:
Whitelist: keep all except unselected (unselected removed on close of last tab with domain).
Greylist: keep until restart except unselected (unselected removed on close of last tab with domain).

I should add that the _DEFAULT items are templates and will only be used when creating new expressions. You would need to add other domains to the whitelist to keep data on those sites.

[snowbound]

Ok thanks for the help today. Seems that the only way I could only have Gmail being the only domain affected is to whitelist each and every other domain that Brave, in this case, uses in extensions or visits and that is too arduous of a task.

[kennethtran93]

You can also try using regular expressions to capture all but one domain, as long as the browser's version is the latest one, or has been released in the last 1-2 years. Here's one that will capture all but those ending in google.com: /(?<!google\.com)$/. Try putting that into the whitelist. Then you can have a separate whitelist for google.com, except check all but the cookie you want to delete. As long as you still have at least one google.com tab open until browser restart, that cookie you kept unchecked should not be removed until then.

[snowbound]

Thanks that seems to have done the trick. Further testing is required on my part on which ones of the cookie names actually have to be deleted on browser restart to produce the desired effect.

[kennethtran93]

Repasting as partial solution:

You can also try using regular expressions to capture all but one domain, as long as the browser's version is the latest one, or has been released in the last 1-2 years. Here's one that will capture all but those ending in google.com: /(?<!google.com)$/. Try putting that into the whitelist. Then you can have a separate whitelist for google.com, except check all but the cookie you want to delete. As long as you still have at least one google.com tab open until browser restart, that cookie you kept unchecked should not be removed until then.

[snowbound]

Working fine and as I wanted it to. Appreciate all the help with the issue.