The Cart Was Empty. The Coupon Extension Was Still Watching.
Photo by Photo by Julio Lopez on Unsplash on Unsplash
Cyber Monday 2026 lands on November 30, which means my inbox is already full of promises about one-click coupons and cashback. Before I let any of those browser extensions near a real checkout, I did a dry run on a clean Windows 11 profile. I installed five of the most advertised coupon and cashback extensions, browsed a handful of US retailers with a test cart, and then emptied the cart to see what stayed awake. This was not a lab-grade security audit. It was the kind of permission check a normal PC user can repeat in about 45 minutes.
The setup: one clean profile, five extensions, no saved cards
I used a spare Windows 11 laptop with a fresh Edge profile and a Chrome profile for comparison. No saved passwords, no payment cards, and no extensions except the one I was testing. I picked five categories you have probably seen in the stores: two coupon-code aggregators, two cashback tools, and one hybrid that promised coupons plus price history. I am calling them Extension A through E because extension behavior changes fast and one test should not become a permanent brand verdict.
For each install, I read the permission prompt, checked the extension's Details page, and watched the browser's network panel while I loaded product, cart, and checkout pages. I also checked whether the extension did anything after I emptied the cart and moved on to non-shopping sites.
The permission prompt is the real coupon
Almost every coupon extension asked for permission to read and change all my data on all websites. That is not a typo. It means the extension can see the page I am on, including product names, cart totals, and form fields. Some also asked to read browsing history or display notifications. Cashback tools often need broad access to know when I land on an eligible store. But broad access is still broad access.
One extension offered a narrower on-click mode. Another defaulted to all sites. The narrow one was less nosy, but it also missed automatic coupon tests until I clicked the toolbar icon. That is the trade-off: convenience versus how much of your browsing the extension can see.
What happened while the cart was full
All five woke up on retail product pages. Two injected a visible coupon bar; one only showed a badge. Four made requests to their own servers as pages loaded, even before I clicked anything. I could not prove exactly what was inside every request without reading the code, but the timing was clear: requests fired on product pages, cart pages, and checkout pages. The extensions were doing their job, and doing it across more of the session than I expected.
Extension C, the hybrid, was the most aggressive about prompting. It popped a we found codes window on a cart page where I had not asked for help. Extension D, a cashback tool, stayed quiet until I clicked, then requested all-sites access anyway. Extension E asked for notification permission, which I denied; it still worked, but nagged less.
The part that mattered: after the cart was empty
Emptying the cart was the most useful test. Two extensions went quiet on non-shopping sites, which is what you want. Three still ran on retailer pages after the cart was empty. One kept injecting a coupon bar on a product page I was only browsing. Another kept a cashback badge active and fired requests when I revisited the store homepage. The third stayed dormant until I clicked, then read the page again.
None of this proves a data breach. Coupon and cashback tools are built to recognize stores and check for deals, so some after-cart activity is expected. But expected is not the same as harmless. If an extension can read every page and keep checking in after you have left, it deserves a conscious decision, not a default yes.
A pre-shopping permission checklist for Windows 11
- Use a separate browser profile for shopping. In Edge or Chrome, create a profile with no saved passwords and no payment cards. It keeps coupon extensions away from your email and work tabs.
- Install only from the official browser store, then open the extension's Details page. Look at Site access and permissions before you start shopping.
- Prefer On click or specific sites when the extension offers it. If you only need coupons at two stores, do not hand over every site by default.
- Treat read and change all your data on all websites as the big one. It is normal for coupon tools to ask, but it is also why you should remove the extension when the sale is over.
- Deny notification permission unless you really want pop-ups. A coupon alert is not worth a permanent nag channel.
- Before checkout, toggle off extensions you do not need for that purchase. Use guest checkout when it is available, and type payment details manually rather than letting a broad extension watch an autofill event.
- After Cyber Monday, revisit the extensions page. Remove anything you installed for one weekend, and clear site data for the stores you browsed.
- Check permissions again after extension updates. A tool that asked for one store last month can widen its access later.
Removal is a two-step job
Uninstalling is step one. In Edge or Chrome, go to the extensions page, remove the coupon tool, and restart the browser. Step two is cleaning up the shopping session: clear cookies and site data for the retailers you used, and sign out of any cashback account you created. If the extension made you create an account, delete it or revoke the browser connection. The goal is not paranoia. It is making sure a temporary coupon helper does not become a permanent resident.
The bottom line
Coupon extensions can save real money, and I am not telling you to delete every one. I am telling you to read the permission prompt like it is part of the price. Use a shopping profile, choose on-click access when you can, and remove the extension when the cart is empty. The deals may be automatic. Your permission should not be.