Changelog
What’s new
Every change you can see, newest first — the same notes we show inside the product.
Recent changes
September 2026
Signed-out links return you to sign in reliably
Opening a protected page after your sign-in had ended could briefly restart the dashboard for everyone. You are now taken back to sign in without interrupting anyone else using the service.
Deploy now confirms your live banner
The Deploy page could say it could not reach your banner even while the banner was working. It now recognises the published settings correctly, so you can see what visitors are receiving.
August 2026
A help centre, in plain English
Ten short guides covering the questions people actually ask: installing on WordPress or anywhere else, building and publishing a banner, why a tracker still fired, what your check results mean, how to prove a consent record, and what happens when you change or cancel a plan. Look for Help in the menu.
Download everything, and close your account yourself
You can now get one file with all of it — your sites, settings, team, invoices and consent records — without asking us. You do not need to be leaving to take a copy. Closing an account is also yours to do now, with 30 days to change your mind, and nothing is deleted in that time. Both are on the Account page.
We now tell you when a payment does not go through
If a card expires or a payment is declined, nothing used to say so inside ConsentCook — your banners kept running and you might not find out for weeks. You will now see a note on your home page and your billing page explaining what happened and how to fix it. Nothing stops while you sort it out.
See what consent costs across all your sites
Most cookie banner tools charge for each website you run, so the bill grows with your list. We charge once for the account. There is now a page showing what five sites would cost with us and with the others, with every price linked to their own page so you can check it — plus pages on moving over from another tool and on running client sites.
Your site now tells you when it is waiting for its first visitor
A site that was set up but had not yet recorded anyone's choice showed a dash where a number should be, which told you nothing. It now says it is live and waiting, and points at where your first signed record will appear — that record is the proof of what a visitor was shown and what they chose.
Clearer answers on refunds, fair use and what we have changed
Three new pages: how cancelling and refunds work (including a full refund within 30 days of your first payment), the short list of things you must not do with ConsentCook, and a public list of everything we have changed. We have also published the open-source software we build on.
Our security and subprocessor pages now match how we really run
Our public security page listed a few protections we had planned but not yet put in place, and our list of the companies who handle data on our behalf named some we do not use. Both now describe exactly how ConsentCook runs today — including where your data is held, how often we back it up and how far back we could recover — with the things we have not done yet clearly marked as not done.
Three new pages: support, accessibility and reporting a security problem
You can now read how to reach us and when we answer, what we have and have not tested for accessibility, and how to report a security problem safely. Support is the same on every plan, including the free one, and you can now write to us at support@consentcook.com as well as using the chat.
The status page now covers the banner on your website
Our status page told you whether the dashboard and our background jobs were working, but not the one thing your visitors actually see — the cookie banner on your own site. “Cookie banners on your website” is now listed there too, so if anything is wrong with delivering them you can see it without asking us.
Publishing now shows you changes to what gets blocked
When you chose to block a tracker and then went to publish, the review step said "No changes" — even though publishing would change which trackers are stopped on your site. Those changes are now listed by name before you publish, along with the on/off switch for automatic blocking, so you and anyone approving can see exactly what is about to change.
Google now hears the whole answer about advertising
Google splits permission for advertising into three separate answers, and your banner was only ever sending one of them. The other two stayed switched off — even for a visitor who pressed Accept all — which quietly held back remarketing and personalised ads on sites using Google Ads. All three are now sent, on every site, from the next time a page loads. You do not need to change anything or publish again.
The service status page no longer misses a short problem
The 30-day strip on our status page could draw a day green when something had in fact gone wrong that day, if the problem was brief and a healthy check happened to land just before it. Every change between working and not working is now written down, so a day with a problem shows as one.
Stronger checks on what can be written into your consent record
A consent record we accept now has to refer to a banner setup you actually published, and one request can carry at most a hundred records. Nothing changes for your visitors — the banner already works this way — and older records still go through, so a visitor whose browser had an out-of-date copy of your settings is not turned away. The Developers page also explains what a receipt's signature does and does not prove, and how to send consent from your own server if you need a record that stands up to being challenged.
Home now points at the site that needs you most
The “Finish setting up” list showed your sites in whatever order they happened to load, so the one it told you to deal with was picked more or less at random. It now puts the most exposed site first — one with no banner at all, then one where something runs before visitors agree, then one we could not reach — and the order stays put between visits.
The service status page now shows the last 30 days
The page told you whether things were working this second and nothing about the days before, so you had to take it on faith. It now shows a square for each of the last 30 days and says how many of them had a problem. Days from before we started keeping this record show faded rather than green — we would rather show a gap than claim a history we do not have.
Your cookie list now says what each cookie is for
The cookie list built from your site checks named every cookie but never said what any of them did, which is half of what a cookie policy is supposed to tell people. Where our check knows what a cookie is for, it now says so, on the table under Policies. Where nothing is known we leave it blank rather than guess — an invented description in a published policy is worse than a gap.
See which site is using your allowance, and clearer wording when you delete one
If you run more than one site, Plan & billing now breaks this period's consent events down site by site, busiest first, with a link straight to each one's reports — so a warning that you are near your limit tells you where to look. Deleting a site also describes what really happens: the banner stops right away, you can't put the site back yourself, and your consent receipts for it are kept, so the proof of what visitors chose is not lost.
Choose the dates your consent charts cover, in plain words
The charts on Reports always showed one fixed period and there was no way to change it. You can now pick any dates, or press Last 7 days, Last 30 days, Last 3 months or Last 12 months. The filters under the log also read properly now — “Where they were” offers United Kingdom and California instead of GB and US-CA, and “What they did” offers First choice and Consent withdrawn instead of the words our database uses. Your export still matches whatever you have filtered.
See it for yourself
The Free plan needs no card, and covers one site with signed receipts and every region pack.