Managing cookies in your browserMost browsers allow you to control how cookies get used as you’re browsing.Some browsers automatically limit or delete cookies. Also, in some browsers, you can set up rules to manage cookies on a site-by-site basis, allowing you to permit cookies only from sites that you trust.In Google Chrome, the Settings contain an option to Clear Browsing Data. You can use this option to delete cookies and other browsing data. See our instructions for managing cookies in Chrome.Google Chrome also supports private browsing with its Incognito mode. You can browse in Incognito mode when you don’t want your site visits or downloads to remain in your browsing and download histories. Once you close all your Incognito browsing windows, Chrome won’t save your browsing history, cookies, and other data.Losing the information stored in cookies may make sites less functional but shouldn’t prevent them from working.

How do I change my cookie settings? Most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Control aims to prevent cookies from being placed on a user's computer until they have given their explicit consent via an affirmative act.

<!--IUB-COOKIE-BLOCK-START-->

Blocking cookies before consent. In compliance with the general principles of privacy legislation, which prevent processing before consent, the cookie law does not allow the installation of cookies before obtaining user consent. In practice, this means that you may have to employ a form of script blocking prior to user consent.

Prior to informed and explicit consent, no cookies – except for exempt cookies – can be installed.

Implementing prior blocking and asynchronous re-activation Our prior blocking option prevents the installation of non-exempt cookies before user consent is obtained (as required by EU law) and asynchronously activates (without reloading the page) the scripts after the user consents.To use, you must first enable this feature: simply select the “Prior blocking and asynchronous re-activation” checkbox above before copy and pasting the code snippet into the HEAD as mentioned in the preceding paragraph.

Google Tag Manager allows you to avoid tagging scripts as described below, although this is limited to a certain category of scripts – scripts that are not positional/do not define a position. It, therefore, does not handle embed scripts such as those related to advertising banners, youtube video widgets, facebook like buttons etc.

The user's computer stores and transmits cookies. Therefore, you as a user also have full control over the use of cookies. You can deactivate or restrict the transmission of cookies by changing the settings in your browser. Cookies that have already been saved can be erased at any time. This can also be done automatically. Please consult the documentation of your browser. Links to the cookie management documentations of some popular browsers:

Practical examples Below are examples of commonly used scripts and guidance on how to modify them as to comply with cookie law.

To do this, you’ll apply the class _iub_cs_activate to the SCRIPT tags. Finally we change the type attribute from text/javascript to text/plain.

The fastest way to preventively block the scripts that require prior consent is to install a module on your own server that we have developed for Apache, IIS and NGNIX. After the initial configuration, the module will autonomously block all the resources that are subject to prior consent, on all sites on that server that are using the Cookie Solution.

Please consider that using this method means that you do not directly block the vendor scripts yourself, therefore, the success of this method depends heavily on the individual vendors’ adherence to regulation.

This method has the advantage of being quite fast but with the limit of working only for scripts that don’t require a specific position. Google Tag Manager is therefore not effective for all scripts that display a specific element in a specific position of the page (such as the Facebook Like button).

this website claims the cookie stuff will be a responsibility of the browser, not the website, which would make live easier for web devs.

Our WordPress plugin automatically blocks scripts that are generated on the server side (therefore returned by PHP by WordPress). Scripts that are inserted into the page via JavaScript after the loading process of that page are not and cannot be blocked automatically.

In practice, this means that you may have to employ a form of script blocking prior to user consent.

provide users with information regarding how to update their browser settings. Many sites provide detailed information for most browsers. You could either link to one of these sites, or create a similar guide of your own. Your guide can either appear in a pop up after a user declines consent, or it can be part of your Privacy Policy, Cookie Information page, or its own separate page.

Is installing and configuring the plugin enough for compliance? Only if the only cookies your site uses are the Google Analytics ones. If other plugins set cookies, it is possible that you will need to write additional JavaScript.

If a user embeds a Facebook iframe, a blocking tool is needed that initially disables the iframe and or scripts

Cookies may not be detected by scanner if the related tag is triggered by actions such as form submission, scroll depth, timing delay, etc. These tags will need to be controlled by manual methods.

Cookies set by in-line scripting directly in the HTML is not supported by the auto-blocking functionality.