I need to remove cookies for a specific website from every computer in my organization, preferably for Microsoft Edge, Google Chrome, and Firefox. Clearing all cookies would also be acceptable if targeting one site is too difficult.
I tried creating a script with an AI coding assistant, but it suggested installing sqlite3 to edit the Chrome and Edge cookie databases, which does not seem practical in our environment. Only about half of the computers are domain-joined, so deploying a Group Policy is not an option for everyone. However, I can distribute and run a script through our monitoring software.
What would be the safest and most reliable way to handle this?
4 Answers
First check whether the problem is actually cached content. A hard refresh such as Ctrl+Shift+R may fix it without touching cookies. If cookies really must be cleared, an email with simple, picture-based instructions may be less risky than modifying browser databases on every machine—especially if many users leave their browsers open or only lock their computers.
If this is a one-time incident, the lowest-risk option is probably a short instruction sheet with screenshots and a desktop shortcut or support script for the users who need help. If it is an ongoing requirement, deploy browser policies through whatever device-management or monitoring system you have, test on a small group first, and target only the affected site's cookies if the browsers support that policy. Clearing everything should be the fallback because it will remove saved sessions and preferences.
For Chrome and Edge, look at the browsers' administrative policies rather than trying to edit the SQLite cookie files directly. Both support registry-based policies that can clear browsing data, including cookies, when the browser exits. This avoids installing sqlite3 and is easier to deploy through your monitoring tool. Test it carefully first, because users who leave the browser running will not have the data cleared until it actually closes, and clearing all cookies can sign people out of many sites.
The browser policy approach sounds promising. The main limitation is that some employees simply lock the workstation and leave the browser open, so the cleanup would not happen until they eventually close it.
A script can remove browser profile data, but it needs to run while the browsers are closed. It would also need to account for every user profile on the machine, not just the currently logged-in user, and Firefox stores its data differently from Chromium-based browsers. I would avoid deleting database files while they are in use, since that can corrupt profiles. If you control the browser configuration, an exit-time policy or scheduled cleanup after browser closure is safer than directly manipulating the databases.
That was my first thought too, but the request came from management and many of our users are not very comfortable following technical instructions. They often just lock the computer and leave, so getting them to close and reopen the browser may not be reliable.