Cookies in Containers
What does it do? It basically creates little information bubbles that don't expose data to the other. If you don't want amazon to follow you around on the net while you read the news, create a container for news reading and one for shopping on amazon. Everything that is put in container A does not have access to data stored in container B. Need a different login for a page because of work? No problem, open it in another container titled "work".
After I combined this with three other add ons, I had what I always wanted. A system that throws away most cookies after I leave the page that created them. It remembers cookies for specific pages, but does not leak information to those sites when I surf the web.
I created a shopping container that openes automatically when I surf to amazon.com, but amazon will not be able to track me when I surf on the web. Without the hassle of logging in to amazon each time I visit the site.
My browser will delete all data for 80% of the pages that I opened after I close the tab. Only a handful of pages are opened automatically in specific containers and keep their cookies.
My additional add ons are:
This add on makes it possible to switch the container for a page you have opened. This helps me when I excitedly opened the page in the wrong container.
This add on is configured to throw away every cookie. With the exception that it does not throw them away for specific containers.
If you throw away all cookies all the time, you will see lots and lots of cookie warnings. Luckily this add on will prevent them from showing up.