The annoyance
I was dismissing cookie banners 10–15 times a week.
News sites, shopping sites, blogs. Different banners, same task. I already knew what I wanted to choose, yet every site asked me again.
It was a tiny interruption, but that repetition made me wonder: why am I making the same decision over and over?
The idea
My first thought was to hide the banners. Existing extensions already do that, but hiding a banner doesn't always submit a real consent choice.
I wanted something different:
Choose once. Apply that choice automatically everywhere.
So I built SetOnce, a Chrome extension that stores your cookie preference and applies it as sites load.
How it works
The web is less fragmented than it looks. Many sites use the same consent platforms, including OneTrust, Cookiebot, Didomi, and IAB TCF.
Instead of blindly finding and clicking buttons, SetOnce detects the platform and uses its consent functions to submit the user's choice.
Users can choose:
- Accept all
- Reject non-essential cookies
- Set their own mix of functional, analytics, and marketing cookies
For custom banners, the extension falls back to matching common actions such as “Accept All” and “Reject All.”
I also added a history log showing where SetOnce acted, what it chose, and when. What started as a small extra became important: automation is much easier to trust when you can see what it did.
The result
Setup takes a few seconds.
After that, SetOnce handles a decision I used to repeat 10–15 times each week.
It doesn't just hide the interruption. It submits the choice I would have made myself.
What’s next
The main gap is custom consent banners. Generic button matching works often, but unusual wording and embedded banners can still cause problems.
A stronger version would use a maintained library of site-specific rules, much like browser filter lists.
A small tool for a small annoyance. One less repeated decision to make.