This is a guest blog from InTENSO, makes of Angry Cookies for Jira.

Do you know what the “cookie directive” is?

The “cookie directive,” also known as Directive 2009/136/EC, defines consent requirements for cookies across the European Union (EU). Specifically, paragraph 26 says:

“Member states shall ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia, about the purposes of the processing. This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service.”

In simple language: Before somebody can store or retrieve any information from a computer, the user must give informed consent to do so.

What does this mean in practice?

Every day you see website pop-ups like, “We use cookies on this website …”. Even non-technical users can typically grasp the concept of cookies: pieces of data, normally stored in text files, that websites place on visitors’ computers to store a range of information, usually specific to that visitor. Cookies allow you to log in on one page, then move around to other pages and stay logged in. They allow you to set preferences for the display of a page, and for these to be remembered the next time you return to it. At first glance they are very useful, but it’s important to realize that they store your private information.

What does this have to do with Jira?

If you host Jira yourself, and it is publicly available to customers, the Directive applies also to you. The Directive affects the laws of each EU member state differently, but if you don’t want to break the law in your country, you should inform your Jira users about the cookies appropriately – and Angry Cookies helps you do that.

What is Angry Cookies?

Angry Cookies is a Jira plugin that helps apply the cookies regulation in most EU countries. The Jira administrator can configure text about the cookie policy that your company’s legal department creates, and the plugin will provide a banner to get consent from users, with a link to your company’s privacy policy. To get you started, we’ve included built-in sample text for you to use if you do not have an in-house legal team. This solution lets you write text in your language to protect your company from financial penalties from violating national laws on private data collection. What’s more, the plugin is available to anyone for a nominal price – only $50 for most Jira instances.

Angry Cookies displays a simple banner at the top of your Jira instance.

How does it work?

When a user accesses your application for the first time, he or she will see a message banner at the top of the page. After reading and accepting the warning about cookies, the message banner will disappear. For anonymous (not-logged-in) users, the message banner may reappear if Jira cookies expire, or the user clears the browser’s cache. For logged-in users, the choice will be remembered, so they only need to accept the cookies policy once.

Get started

Angry Cookies: Solving the EU’s “cooki...