A cleaner web experience with Self-Destructing Cookies

Self-Destructing Cookies is a cool little plugin I found yesterday that deletes cookies as soon as you’re done with them. Apps like CCleaner are great, but you need to run them on a schedule, so cookies will linger until the task is run. Self-Destructing Cookies runs as soon as the browser tab is closed and deletes all the cookies associated with that tab. This means all those useless cookies will be deleted right after you leave the site, not several days later.

Why would you care? Have you seen the number of cookies that get downloaded from a site these days? It’s both shocking and distressing. I’m not going to sit here in a tin foil hat, but sites are serving up more than just ads. All sorts of "beacons" get written down and whether or not they track your movements, they’re utterly useless, especially after you leave. Of course, none of those get deleted, so they sit there collecting data and who knows what else.

I want to keep cookies related to Amazon and Steam, because I shop there and it’s easier to log in. But if I look up something about the weather or check the price of an appliance, I shouldn’t have 10-15 extra cookies on my machine making note of what I just looked up.

When you first install Self-Destructing Cookies, it will clear out your entire cookie cache. To me that was a good thing, but there is an Undelete function so you can retrieve cookies for sites you want to keep – Amazon for example. From there, you can whitelist whatever cookies you want to keep and they won’t be destroyed – Steam for example. Everything else will get swept away as soon as you close the tab for the site.

Keep in mind, this doesn’t clear out the web cache, forms or anything else, that’s a job for CCleaner. But Self-Destructing Cookies is brilliant. It removes all those cookies that you have no use for and would just delete when you left the site if you took the time to do it manually. I have this installed at both work and home and if you leave the notifications on for a few minutes, you’ll be stunned by all the cookies you collect.

Self-Destructing Cookies automatically removes cookies when they are no longer used by open browser tabs. With the cookies, lingering sessions, as well as information used to spy on you, will be expunged. Websites will only be permitted to identify you while you actually use them and can not stalk you across the entire web. This is the closest you will get to cookieless browsing without breaking every second site or tedious micromanaging.

Self-Destructing Cookies from Mozilla

Other articles of interest:

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Comments
  • Enter dates into a date picker for Chrome and Firefox (1)
    • Prasanna: Hello, How to enter a previous month FIRST day and LAST day from the system date. Thanks Prasanna
  • How To Disable the Quicken Registration Prompt (31)
    • Juani: Hi, I have a registered Quicken 2016 and now my files are being held hostage by Intuit, cannot log in with my ID unless I upgrade therefore buy a subscription, I need to access my files, please HELP. Thanks
    • David: A BIG Thank you! I regularly reinstall Windows OS’s using different hardware configs. In short, Quicken 2011 (it’s March of 2020 as I write this) has been a program I’ve been very happy with and continue to use....
    • Karen L: Today I rang Reckon Australia again, got a different guy and he talked me through the process of getting me a new product key to enter since I already had the licence and it had been extended. Reckon have only extended it by 1...
    • Karen L: I have Australian Quicken 2008 on Windows 8.1. It keeps asking me to renew my licence which Reckon did for me however the activation won’t work. I tried this to disable the registration prompt however it did not stop the...
  • Building Relationships with Developers (1)
    • Carlos Herrera: Ah yes. I have a team of software developers and it is genuinely so hard to keep them in the loop during projects. Though the more we work the better the communication becomes and we go from a trail and error process to a...
  • Integrating DevonAgent Pro with Alfred (1)
    • J. Garr: Beautiful, sweet, and simple. I love it; thanks for posting this solution.
  • Round and Round with the For..Next in Katalon Studio (1)
    • Sweet Ophaline Labador: Hello can you help me how to loop this scenario. Checking the elements is just the same. I want to check that the following function is available in www.siacargo.com: Track Shipment – clicking on this can...
  • Parsing Strings in Katalon – Split, Substring and Readlines (6)
    • Don Pedro: String tempText=”Date Month January. Revenue $1,355,721.00″ println(tempText.split(“ \$”)[1]) You need to escape the $ with \$ The [1] on the split captures characters on the right of the split [0]...
    • Prasad: Hi, I need to get the substring from the below string ‘Date Month January. Revenue $1,355,721.00’ I want to extract text after $ value. Please help Thank you
  • Working with Dates and Date Formatting in Katalon Studio (15)
    • Sangeethaa: How to get previous day’s date(Yesterday’s date)? Actually I was using today.previous() before,it was working fine till today morning.Now its not retrieving right date. Can anyone please guide me on this.
    • Don Pedro: That could be a little tricky. First, is the text/format always going to be the same? You will need to do some parsing. Separate the first but of text at 2019. After that, split the text again to get rid of Central Standard...
    • Don Pedro: It should be of the same Date type as today. You could then do some calendar trickery with Calendar /*Calendar c = Calendar.getInstance(); //c.set(Calendar.MONTH, 1) //Set the month, 0=January, 11=December println...
  • Output status messages and test information by writing to the Log File Viewer in Katalon Studio (6)
    • Saranya: Good One. Could you plz share link to access all your katalon related blogs. ThankQ
    • Rodrigo Calabretta: I’m using the KeywordUtil.markFailed or KeywordUtil.markError and my test stops is being shown as Error and If I use in the @afterTestCase the testCaseContext.getTestCaseSta tus() to show the status test case...