Hey Marc!

This is a good question and I also needed to do some digging to find an answer, as this is beyond my technical knowledge. ;)

What I have found is that this is not simply a switch in the configuration for us, this would have to be build by a developer in order to work properly:

Currently, this modal loads in after the page has been loaded, furthermore it is using some special library to load the custom checkboxes. This apparently makes connecting any other script to change the behaviour difficult. In consequence, the effort to get something like this done in this default modal would probably be quite complicated and inefficient, also as we would need to maintain this after the change.

So ultimately, we would not recommend to use this default modal for such a change due to complexity, it might be a better solution to use a different tool for the cookie modal then.

We could handle the implementation of a different tooling to support this use case, but this would go beyond what our support can handle (e.g. simple mapping of a new cookie modal) - it would not be free of charge and a professional service that we offer.

Thanks for the detailed reply @Julian 

I’m the same - Cookies and how they work are moreoreless the exact point where my technical knowledge wavers and I start to defer to Those Who Know…. 

But the main thing I understand that if we wanted to make a change, we’d have to take the Cookies options out of Insided’s hands and implement our own.