Frontend Library - Legal

These are the terms and conditions for using the Frontend Detection Library.

You must agree to these terms to use the library on your own site.

Third-party libraries included

Most of the detection provided by the Frontend Detection library is built by us. However there are a few inclusions of libraries/detection routines written by other parties.

This library includes Flash detection based on code from the "flashdetect" library, which is in turn based on a simplified version of SWFObject.

This library includes Java detection based on code written by Oracle's Java Embed Javascript library (deployJava.js)

This library is newly released. It has only been tested on Using this library on your website may have unintended consequences for you. We want to ensure that this library is as non-intrusive as possible, so if you find any problems with it, please let us know and we will do our best to fix it.

No direct linking

You may not directly link to the Javascript file (whatismybrowser.min.js) on our Content Distribution Network. You MUST download the file and store & serve it on your own web servers. If we detect that you have directly linked to our CDN on your website, your customers will be blocked from downloading the file and the detection will fail.

Some things to note and agree to:

Ad-Blocking detection

Adblock detection involves modifying your webpage's Document Object Model (it inserts a div with an id designed to cause adblocking software to hide it).

We have tried to make this as low-impact on your site as possible - the div should be "invisible" to normal users, and it shouldn't affect the display of your site. To this date, no one has reported any problems with it, but you should be aware that this is happening.

If you ever find any problems with this, let us know and we'll try to find a way to work around/mitigate the problem.

Third-Party Cookie support requests

In order to check if a user has allowed third party cookies, it's necessary to actually set a third-party cookie (and then check it's existence a few seconds later). To do this, the code will make two requests to one of our special domains: which is specially configured to set and then (on the subsequent request) check a cookie.

When these requests are made, the library will also include the full url of the page that is making the requests (unless your site sends HTTP headers which stops this), as well as the version number of the Frontend Library. Naturally these HTTP requests will also include the IP address of the client making the request and their user agent. This information will be stored. We use this information for diagnosing problems, monitoring and reporting as well as stopping malicious or abusive use. The user agents which are sent to the "set cookie" url may also be recorded and added to our User Agent Database (much the same way that user agents we see on the website are recorded and added to the database). We don't use it for any advertising or tracking purposes and (other than aggregate data) the logs are rotated every few weeks.

You'll probably need to update your Privacy Agreement/Terms & Conditions on your website to note these requests to our servers.