We use the same CookieScript banner configuration across multiple environments (for example: PROD, staging, and development), with only one script per banner.

At the moment, when the "Remember consent for subdomains" option is enabled, consent works correctly only on the real target domain, but not on other environments such as localhost or non-production domains. In those cases, the consent cookie cannot be saved in a consistent way, so the pop-up keeps reappearing.

This creates inconsistent behavior between environments and makes proper development, QA, and testing difficult. Disabling the option is not a real solution, because it changes the intended production behavior rather than solving the underlying issue.

Expected behavior:

When using one banner script across multiple environments, consent handling should remain predictable and consistent in non-production environments as well, without forcing the pop-up to reappear endlessly.

Suggested improvement:

Please provide a built-in way to support multi-environment setups, for example, by allowing:

This would make CookieScript much more practical for teams that develop and test across several environments before deploying to production.