Correct configuration of "Fines Protector".

Modified on Fri, 4 Aug, 2023 at 5:51 PM

To have Fines Protector you will need a Plus or higher tier. Also, some configurations should be set to maintain you covered.


What aspects should I consider to comply correctly with Fine Protector?


As we have explained in our article "Fines Protector", this is a feature we have implemented to cover our clients in case they receive fines. In this way, we achieve not only the user's peace of mind within our site but also that of our users.


Like any "insurance service", in order to cover a possible fine, we must ensure that our users' options within our platform are configured in the way we recommend. If we verify that these configurations were in place, then the "Fine Protector" will be valid. This is because based on all the information about the different regulations around the world that we possess and our constant research to stay updated on them, we can suggest how our users would be fully compliant.




How do we monitor that the configurations are in place?


All the information about the changes that users make in the settings of our platform is stored in a database where we take into account which configuration has been chosen, the date, and even the time. This allows us to have accurate control of the configurations for each user.




What specific configurations should I consider to be covered by Fine Protector?


As mentioned earlier, to cover a possible fine, we need to ensure that the fault lies with us and not with the user. Therefore, we will monitor the following configurations:


  • The user must have the Fines Protector service activated.


  • The categorization of cookies must be correctly declared. If a marketing cookie is classified as necessary, the user would be breaking transparency rules, and the fine would not be covered. Also, all cookies must be classified.


  • Block Cookies until consent: In advance settings, you have set up by default to block cookies until consent. This is only for those banners that required an opt-in such as the GDPR and Global banner. This does not affect the CCPA banner where opt-in is not needed, you just need to give the option to opt out (or in other words "don't sell my data option"). If Block cookies until consent is turned off we are not able to cover fines in Europe and in the regions where the GDPR banner and the global banner are displayed, as it does not comply with those regulations and standards.


  • The Banner Configuration by Region must be selected according to the default configuration of illow. If, by the user's decision, a banner is displayed in a region that does not correspond to its regulation, the Fines Protector cannot cover fines in those specific regions. You can set back illow's configuration by clicking the "Back to illow settings" button).



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article