Have you tried two browsers?
One browser for logins that doesn't auto delete data when closed.
My second browser deletes everything, except bookmarks, when I close it.
this post was submitted on 15 May 2025
26 points (88.2% liked)
Firefox
19638 readers
172 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 5 years ago
MODERATORS
Yes, I am considering using multiple portable instances of waterfox for this exact purpose. I think my final solution will be a mix of many different methods of containment and parrallel instances.
I auto delete all history after 28 days but I keep tabs open for sites like this that I'm logged into so those cookies aren't deleted because the history is never that old
i'm trying to understand your exact needs, but i'm honestly surprised cookie auto delete can't do it.
could you explain exactly what you're trying to accomplish? and the wall you hit with cookie auto delete to do it?
My guess is that op wants to delete all cookies except the ones that maintain login etc
cookie auto delete support white listing certain cookies for certain domains. Unless OP want a plugin that can automatically figure out what cookies are required to stay logged in for what domain which is impossible
Yes, and also on a per-container basis, because different containers have different logins to the same website As I described in the other post https://lemmy.ml/post/30131984/18621605
I think you are correct to say it is currently impossible.
Well according to chatgpt, because
Cookie AutoDelete can whitelist by domain, but not per-container.
Firefox Multi-Account Containers (MAC) don’t expose cookie APIs per container to extensions — this is a Mozilla limitation.
Session cookies (those not marked as persistent) are deleted on shutdown unless the domain is explicitly allowed to "stay logged in" (via about:preferences#privacy > Cookies & Site Data > Exceptions). But not on a per-container nor per-cookie basis, it is all or nothing. Whitelisted websites keep ALL their cookies
Lastly, there does not exist a repository of cookie rules for user to share the session cookie names on a per-website basis
In other words, there does not exist a "sponsorblock-like" equivalent but tracking and identifying in a crowdsources way, the session cookies
Imagine website example.com
example.com, has a overly tedious login process, with a separate pageload for the username/email and then for the password, and then the second factor and then a captcha.
Worse, I have a different example.com account for their service A, their service B and their service C
Currently, every time I restart my browser, I have to go into each account container, load example.com, login into each of the containers
Every, single, browser restart
I don't know what the session cookies for example.com are named or if they change
I cannot really avoid using example.com, but I also don't like them, they are a fundamental part of my workflow, they have no real competitors as they have all driven them out of business thanks to their growth hacking blitzscaling strategy.
I want to, as far as possible, delete all their cookies on an ongoing basis, except for the session cookies, not even just after browser restart but after a period of inactivity as well.
Cookie AutoDelete hasn't been updated for 2+ years and, in my experience, is buggy in combination with containers.
Also, while it did delete cookies, it did not delete certain data in the user's profile folder, still exposing all visited sites (while using Firefox's own history tools does delete this data normally.)
They really missed an opportunity to call the containers Jars
Hi, I try to have something a bit like you.
I use temporary-containers with the firefox multi-account-containers and it's working pretty well!
And of course I delete cookies when a container is close.
Hope that’s help :)
And this allows you to keep the session cookies only, only in the specified containers, even after restarting the browser ? If so can you explain how you keep the session cookies and how did you create per-container per-cookie whitelist to preserve only the session cookies or a single website ?
Hi, actually I don't think that's possible!
But I see that you have a lot of answers :)
It seems that cookie autodelete will do it, per cookie and per container, still in the trial phase but it looks like it's going to work !
What about the new profile feature being rolled out with 138, profile for each of sites different login.
I have 138.0.3, have not seen that in my logins
It's a slow role out, I believe it's supposed to be available to everyone by end of may. But I do believe it can be turned on in the about:config page. Not sure what the command is though
i use cookie autodelete and the containers for the websites i that i know are harvesting/selling my data.
it works well for me so it makes me wonder how it's tedious or buggy for you,
I second this. Can be set to deletes cookies on XYZ (any or all) domain after ABC seconds after tab close.
You need a password manager.
I have a password manager, it is still over 8 steps per login.
Do you want security or convenience? It seems like you can't have both in this situation.
Yes in theory they could be storing everything on the server if you have a session login In practice, anything they leave on my PC I will flush If that breaks some of their tracking ability, that's even better. I don't want to keep anything more than the actual session cookies, everything else goes in the trash after 20 minutes of inactivity
I just put up with entering 2FA multiple times a day.
I wish more sites would allow my Bitwarden to use SSO.
I see many services making SSO a premium feature
See https://sso.tax/
Thia tells me the cumbersome awkwardness of the login process is not an accident
I haven't seen it be a premium feature. I just don't see many offering it as an option.
The page I linked documents where SSO is in a higher price tier, often bundled with other stuff of course.
But that's how they make it a premium feature even though it's not a line item you can purchase separately
I'm using the free Bitwarden, and I have SSO set up anywhere that allows.
If it means for Bitwarden itself, I prefer to use my crazy complex master password to secure my vault.
Not sure if I fully follow what you want. But for my use case, I have something similar with cookie auto delete extension and container tabs.
The extension (not firefox) is set to auto delete everything by default. And then I can add a website-container pair to the extension's allow list and it just works
The only difference I can think of is that I don't bother with individual cookies, rather within the container, all the cookies from the particular website are allowed
Last I checked cookie auto delete I was not able to set say preserve cookies for example.com and only in the example container. Are you sure if you go in another container, those cookies will get deleted ?
Here is an example page
And I think for facebook the session cookies are
c_user
datr
In the settings for CAD, there's a checkbox to enable support for container tabs. Have you selected that? It's under extension options
Ah !! Yes !
I think this is it !!!
Now I just need to figure out the session cookie name for every website, but at least it is possible !!
Nice!
Personally, I allow list all the cookies since the session cookie already identifies me anyway. So I don't see much point in the hassle of going more granular at the cookie level