Feature requests

I would like to request an option to delay cookie deletion until a user has explicitly denied consent, instead of deleting cookies immediately on script load when no prior consent exists. The current behavior creates significant issues for both compliance and business performance, and is a major blocker for adopting cookie-script.com . Why this is important: 1) New installations perge all excisting cookies When implementing cookie-script.com on a site that previously had no CMP, all existing cookies are deleted on the first visit before the user has a chance to provide consent. This results in a full reset of tracking and loss of historical data. 2) CMP migrations reset tracking When migrating from another CMP, existing consent is not preserved, and all cookies are deleted on the first visit. This again causes a complete reset of tracking. 3) Unintentional deletion of long-lived cookies When the consent cookie expires (e.g., after 30 days), all other cookies are also deleted even those with longer lifetimes, such as Google Analytics cookies (up to 400 days). This leads to unnecessary data loss and degraded measurement quality. 4) Premature deletion reduces effectiveness Deleting cookies on script load may happen before some cookies are even set, reducing the effectiveness of the cleanup. Delaying deletion increases the likelihood that cookies are properly handled according to the user’s final choice. Proposed solution Only delete cookies after the user has explicitly denied consent If valid consent already exists, continue handling cookies as currently implemented Do not delete cookies on initial load when no consent decision has yet been made

The fact that cookiescript by default deletes cookies that the scanner did not pick up (which is a whole lot btw), is absoluty site breaking. A ton of ecom websites will lose alot of revenue because of this, since the cookie that gets set when a user adds a product to the cart, will get removed and empty the cart on a refresh. This is crazy imo

I'm in the USA, using ProtonVPN to test banner behavior in Canada. I noticed that the banner wasn't appearing when geotargeted to Canada. https://geo.cookie-script.com/s/c8aa5642fe138b596e0f3a2db9536a04.js?country=ca I removed geotargeting and saw the banner appear (using cdn.cookie-script.com ...) I added geotargeting back, adding EVERY country & region, and the banner appeared. I used binary search to narrow down to the country that was triggering the banner appearance. I found that CH (switzerland) causes the banner to appear. No other country triggers the banner for me while I'm on a Canada VPN. This COULD be a VPN issue, but iplocator.net identifies me as being in Canada while on VPN. So do Cloudflare headers. I'm positive that I was correctly updating the banner code in GTM, fully clearing cookies & cache, etc. I can reproduce the behavior easily and repeatedly. (also, note that it would be super helpful to have a method on CookieScript.Instance that returns where it "thinks" I am. e.g. adding it to CookieScript.instance.getGeoTargeting. Would have saved me some effort!)

I made an update to the Cookie-script Google Tag Manager template, where you can migrate consent from a previous CMP when swithing to cookie-script.com This I just to let you know, and for the Cookie-script team to be able to reach out if they would like a copy, so everyone can benefit from it. The logic is: If Cookie-script's cookie is not present Check if there is a consent cookie from the previous CMP Set a Cookie-script's cookie with consent from the previous CMP Cookie-scripts banner is not shown, and cookies are not deleted when migrating

We have some clients which would like to recieve the cookie scan report each month, but right now is not allowed.

Newly discovered cookies are currency beging deleted untill they are manually classified in the cookie list. This can break website functionality if the new cookies is necessary for the sites functionality

It could be really great if we could get an option to create a group or folder for a client and then place all their domains inside that. We have multiple clients which has alot of domains which could be great to use some kind of group/folder to place all inside them, where they are not sharing consent.

It would be extremely helpful if you could provide a dedicated test/development mode script, similar to what OneTrust offers. Currently, features such as “Remember consent for subdomains” are domain-dependent, which creates issues in local and staging environments. During development, we need the cookie banner to be fully enabled and functioning in order to properly test and build cookie-specific functionality. Many features on our site only become accessible after consent is given, so having the banner active and persisting consent correctly in non-production environments is essential for development and QA. At present, because consent cannot persist properly across local/staging domains, the banner continuously reloads and prevents us from testing cookie-dependent features. This directly impacts our development workflow. A development/test script — or an option to relax domain validation in non-production environments — would allow teams to properly test cookie-based functionality without affecting live configurations. This would significantly improve the developer experience and make staging and QA processes much smoother.