Feature requests

I can't believe this does not already exists. Tying a paid account to one individual, and suggesting sharing the login as a workaround, is a bad practice for a serious saas service. My feature request is that CookiesScript implements some type of organization or team feature so that an account can have multiple users, preferably in combination with roles such as owner, admin, viewer, billing admin.

Hi, We're configuring geo-targeting for our banner and hit a gap in the region list. Our requirement is to disable the banner for: US — except California Canada — except Quebec The first one works: in the Install → Custom geo-targeting selector, USA expands into individual states, so we can select every state except California. The second one we can't do: Canada appears as a flat country entry with no expandable sub-regions, so there is no way to exclude Quebec. Only EU and USA offer a sub-region breakdown. This matters because Quebec's Law 25 has its own consent requirements, distinct from the rest of Canada — the same reason California (CCPA/CPRA) is broken out from the rest of the US. Questions: Is province-level targeting for Canada planned, or available through some other mechanism we've missed? If not, is there a supported workaround to show the banner only in Quebec while disabling it in the rest of Canada? Are sub-regions planned for any other countries (e.g. Brazil, UK nations)? Thanks.

Admin dashboard availability for large accounts. We have a large account and wish to grow it even more however, sharing banners to share the workload to other admins is not feasible or scalable under the current conditions . We have 80+ banners now and wish to grow to over 200. Sharing 200 banners with multiple users would be extremely tedious and these users would not have the same level of edit access as the original admin. We need to be able to share the work load have vacation/holiday coverage. We also want to create banner templates that can be copied from all of these admin users to create new banners.

CookieScript stores log files about consents (evidence of consent) for 24 months. Based on majority of global laws and local EU Member State laws the companies are required to store consent for as long as it is not withdrawn and later for 5 years (average claim survival period set in laws). AS A RESULT, dear CookieScript, please kindly ensure the retention of evidence of consent for the periods set above.

Hi, as per our US local counsel, the new CCPA regulations (effective 1.1.26) require that the cookie banner will present a visual confirmation for honoring the GPC opt-out signal. This is something that we must have implemented ASAP in order to continue working with US audiences.

When enabling IAB TCF, the banner texts are replaced by standard texts. It would be great if you could add some additional text below it, to inform about other use cases.

Currently, the “Apply to all websites with this item” feature only affects items that already exist at the time the action is performed. Newly discovered matches added later do not inherit the applied configuration, resulting in inconsistent behavior and additional manual maintenance. Expected behavior: The applied configuration should persist as a rule for this item and automatically apply to both: existing matches future matches discovered later This would make the feature behavior more intuitive and ensure consistency over time.

Noticed 2 accessibility issues with the banner: Hyperlinks should have “text-decoration: underline” so they’re not distinguished by color alone. This applies to at least the privacy policy link on both the default and expanded banner states. It may also apply to other links not part of my configuration. Activating the high-contrast mode applies to some components but not others. This looks to be because of the ability to customize the accent color. We can of course just choose colors that sufficiently contrast, but it’d be nice for this system to behave consistently across all components so users don’t get confused accidentally, and minimize the manual work needed to make each banner contrast-compliant. Would it be possible to address these, #1 in particular?

Every browser bring the defaults light/dark mode system toggle. Bring it to cookie banners so it follows our design rules. Also permit to edit both styling while enabling this auto switch.

It should be possible to assign additional domains to an existing cookie banner that can be used for testing and staging environments. I realize that the problem can be solved if the test and staging domains run as subdomains under the main domain of the production banner. But it should also be possible to attach other top-level domains for use in test context. Cookie Script can simply put an “only for testing” overlay over the banner so that it is not misused to apply the same banner to multiple sites.