stojan gdpr4free Comply with the new EU rules on cookies since 25 May 2018 Avoid a fine of 20.000.000 € Allow the visitor to reject third-party tracking Get ready for even tougher ePrivacy legislation that awaits us in the field of cookies

  • Pixman

Monitored services

GTM

GTM

Google Analytics

Google Analytics

Leady

Leady

iFirmy

iFirmy

GTM

Facebook

MouseFlow

MouseFlow

DoubleClick

DoubleClick

Google Remarketing

Google Remarketing

Hotjar

Hotjar

Sklik

Sklik

About GDPR

On May 25, 2018, the new EU legal regulations, including work with cookies and "tracking" of visitors came into force. There is a new risk of a fine of up to € 20 million for non-compliance. Website owners, eshops, and web apps who use any tracking and analytics tools (like Google Analytics) must now allow a visitor to deny tracking. Nowadays most sites use notoriously known panels for informative use of cookies, but do not offer the option to block these services. The gdpr4free library helps block third-party tracking services until the visitor really agrees to use cookies. Only then will be the monitored services unblocked.

The gdpr4free Javascript library offers an effective solution combined with a cookie consent panel, such as a library https://cookieconsent.insites.com.

Gdrp4free works on the principle of actively monitoring embedded libraries in the source code of websites and their blocking if a site visitor refused cookies or disagreed with their use. The library also excludes statically-inserted libraries from the source code, which are also the monitored services.

Web site owners do not need to make expensive and hard edits to project source code to meet the toughest measures for the benefit of visitors.

In general, ePrivacy's tracking of web visits can be expected to be tightened in the near future. Therefore, the gdpr4free library is ideal for use where you are not sure whether you are complying the regulation or not.

Deployment:

Place the gdpr4free library as the first element immediately behind the opening <head> tag and initialize.

Basic use in two lines of code:

<html>
<head>
<!-- Must be placed as first after opening head tag -->
<script src="https://cdn.gdpr4free.com/gdpr4free.min.js"></script>
<script>gdprGuard.initialise();</script>
    ...
</head>

Possible configuration:

<html>
<head>
<!-- Must be placed as first after opening head tag -->
<script src="https://cdn.gdpr4free.com/gdpr4free.min.js"></script>
<script>
gdprGuard.initialise({
'cookieStatusName': 'cookieconsent_status', // cookie name where has been stored visitor allowance, default is "cookieconsent_status"
'cookieStatusValue': 'allow', // cookie value after cookies are confirmed (visitor agree), default is "allow" 
'excludeDomains': [
    'google-analytics.com' // array of domains, default empty array
],
'addDomains': [
    'domain-to-observe.com' // array of domains strings, default empty array
],
'onAcceptCallback': function() {}, // callback function triggered when cookie consent is confirmed, default is page reload  
});
</script>

If you use the CookieConsent library https://cookieconsent.insites.com, then the library is configured so that no other configuration is needed. If you are using a custom solution or other library, you just need to specify the cookie name parameters where you store the consent flag and a value that indicates positive visitor approval.

Add a new tracked service (domain)

As part of library configuration, you can optionally include additional domains in 'addDomains' to monitor and block. In this case, it's important that you specify the domain that service provider uses in your tracking code that you put on websites. If you specify a domain without the initial "https: // www.", the library will monitor all domains, subdomains and the domain itself, both https://domain.com, https://www.domain.com, and http: /domain.com as well as https://xyz.domain.com. If you specify the domain in the form of www.domain.com, only form with www will be tracked.

How do I find out what domain of service they are working with?

<!-- In this case, the service communicates with the domain: googletagmanager.com -->
<!-- Find out this from the SRC attribute of the script tag below -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-24676653-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-24676653-1');
</script>

Eliminate some default blocked services using the excludeDomain configuration. It works just as much as adding the monitored services, but with the opposite effect. Such domains will disable tracking of default integrated domains to block, see list above.

An example of a complex use with cookieconsent.insites.com

<html>
<head>
<!-- Must be placed as first after opening head tag -->
<script src="https://cdn.gdpr4free.com/gdpr4free.min.js"></script>
<script src="//cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.js"></script>
<script>	
// initialise GDPRGuard simplest way
gdprGuard.initialise();
// cookieconsent panel configuration
window.addEventListener("load", function(){
window.cookieconsent.initialise({
"type": "opt-in",
"content": {
    "message": "We use cookies to ensure you get the best performance of our website and for basic visitor rate analytics.",
    "dismiss": "Deny",
    "allow": "Agree",
    "link": "More information"
}})});			
</script>
<link rel="stylesheet" type="text/css" href="//cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.css" />
...