Feature requests

For agencies and developers managing many websites, it would be extremely valuable if all Cookie Scanner settings were available through the API. Today, these settings can only be configured manually in the dashboard, making it difficult to fully automate banner provisioning and keep configurations consistent across multiple websites. The API should expose all Cookie Scanner settings Start Scan Enable automatic monthly cookie scan Scan subdomains Receive scan results by email Reset user consents if new cookies were found Always scan from the same IP address Website is under password protection Include URLs Exclude URLs Scan page limit

The Finnish text "päästäksemme käsiksi laitteesi tietoihin" in the standard IAB TCF 2.3 banner can be understood as if we get access to all files on the user's device, which is scary. It would be good to clarify this It's more about accessing data that we have stored on the device and information about the device.

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.

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.

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.

When adding descriptions or assigning categories to local/session storage items, running another scan resets the descriptions and reassigns the categories to "strictly necessary". As a result, any modifications I made are lost, and I have to assign everything again. Would it be possible to implement the same behavior as with the cookie scan, where custom descriptions and category assignments are preserved after subsequent scans?

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.

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.

Site https://banab-moebel.at/ We use the CMP CookieScript template for GTM. The default consent settings set the security_storage parameter to granted , but after the CookieScriptConsentUpdated [strict] event, the template changes it to denied . We need the security_storage parameter to always remain in the granted state. Is there a configuration option that prevents the value of security_storage from changing?

GDPR give users the right to be forgotten. Please add a function on cookie-script.com website, where end-users can ask to have their data deleted based on : Webiste Ip-address Consent key And a guide to find your consent key in the cookie-script cookie.