Recherche avancée

Sur d’autres sites (15008)

• How should I write my privacy notice for Matomo Analytics under GDPR ?

  24 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to show you an example of a privacy notice for Matomo under GDPR. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

  A basic rule of thumb is that if you are not processing personal data, then you do not need to show any privacy notice. But if you are doing so, such as processing full IP addresses, then a privacy notice is required at the time of the data collection. Please note that personal data may also be hidden, for example, in page titles or page URLs.

  In this blog post, we will define what a privacy notice is according to GDPR and how to write it if you are using Matomo and you are processing personal data.

  What is a privacy notice under GDPR ?

  One of the most important rights that a data subject has under GDPR, is the right to be informed about the collection and use of their personal data.

  Here is what ICO is saying about the privacy notice :

  “You must provide individuals with information including : your purposes for processing their personal data, your retention periods for that personal data, and who it will be shared with. We call this ‘privacy information’.”

  “When you collect personal data from the individual it relates to, you must provide them with privacy information at the time you obtain their data.”

  Note that a privacy notice is different from a privacy policy.

  The privacy notice has to include :

  • the reasons why you are processing the personal data
  • for how long
  • who the different parties you are going to share them with are

  So whatever lawful basis you are using (explicit consent or legitimate interest), you need to have a privacy notice if you collect personal data.

  What does this privacy notice look like ?

  ICO is providing best practices in order to display the information :

  • a layered approach
  • dashboards
  • just-in-time notices
  • icons
  • mobile and smart device functionalities

  Once more, it really depends on the data you are processing with Matomo. If you wish to track personal data on the entire website, you will probably have an upper or footer privacy notice such as :

  

  If you wish to process specific data, you could also insert just-in-time notices such as :

  

  What is the information you need to disclose to the final user ?

  To us, there are two things to distinguish between the privacy notice and the privacy policy.

  According to ICO, the privacy notice needs to include the 3 following elements :

  • the reasons why you are processing the personal data
  • for how long
  • who are the different parties you are going to share them with

  But you also need to inform them about :

  • The name and contact details of your organisation.
  • The name and contact details of your representative (if applicable).
  • The contact details of your data protection officer (if applicable).
  • The purposes of the processing.
  • The lawful basis for the processing.
  • The legitimate interests for the processing (if applicable).
  • The categories of personal data obtained (if the personal data is not obtained from the individual it relates to).
  • The recipients or categories of recipients of the personal data.
  • The details of transfers of the personal data to any third countries or international organisations (if applicable).
  • The retention periods for the personal data.
  • The rights available to individuals in respect of the processing.
  • The right to withdraw consent (if applicable).
  • The right to lodge a complaint with a supervisory authority.
  • The source of the personal data (if the personal data is not obtained from the individual it relates to).
  • The details of whether individuals are under a statutory or contractual obligation to provide the personal data (if applicable, and if the personal data is collected from the individual it relates to).
  • The details of the existence of automated decision-making, including profiling (if applicable).

  Pretty long, don’t you think ? In order to reduce it, you can either adopt a layered approach where your “pop-up” window will act as a drop down menu. Or from what we understood, page 5 of this document provided by ICO, a privacy notice can link to a more detailed document, such as a privacy policy page.

  Examples

  Let’s take the example of a website which tracks the non-anonymised full IP address, and using User ID functionality to keep track of logged-in users. Under GDPR, the owner of the website will have to choose either to process personal data based on “Legitimate interests” or on “Consent”. Here is how it will look like :

  Example of a privacy notice under GDPR Legitimate interests

  This site uses Matomo to analyze traffic and help us to improve your user experience.

  We process your email address and IP address and cookies are stored on your browser for 13 months. This data is only processed by us and our web hosting platform. Please read our Privacy Policy to learn more.

  Example of a privacy notice under GDPR Consent

  This site uses Matomo to analyze traffic and help us to improve your user experience.

  We process your email address and IP address and cookies are stored on your browser for 13 months. This data is only processed by us and our web hosting platform.

  [Accept] or [Opt-out]

  Please read our Privacy Policy to learn more.

  Once that information is provided to the user, you can then link it to your privacy policy where you will provide more details about it. Soon we will issue a blog post dealing with how to write a privacy policy page for Matomo.

  The post How should I write my privacy notice for Matomo Analytics under GDPR ? appeared first on Analytics Platform - Matomo.

• Evolution #2470 : Publier le site (non public par défaut)

  4 novembre 2013, par Suske -

  On a quand même déjà la phase de "Publication en ligne" sur la plupart des objets, qui indique bien la mise en ligne il me semble. Le fait qu’on peut ensuite être "repéré" par les referers... Ben c’est plutôt un bon souvenir dans ma tête ;-) Et puis par ailleurs si je suis un referer et que je tombe sur un "En travaux", c’est pas cool.

  Donc pour moi :
  - on a la démarche de "Publier en ligne" qui est explicite
  - on a le compagnon qui précise les choses
  - on a le plugin en travaux disponible

  S’il y a quelque chose à faire ce serait de proposer le plugin via le compagnon mais à mon sens ce n’est pas utile : il y a un côté "pris sur le fait", certes, mais je crois que l’utilisateur lambda est conscient qu’un site web est public même s’il ne s’y attend pas.

• FFMPEG installation & configuration with xampp on fedora

  10 octobre 2013, par UMI

  I have running Fedora 8, where I have installed XAMPP-Linux. First I installed latest version with Xampp-Linux-1.8.3 including PHP 5.5 from "http://www.apachefriends.org/en/xampp-linux.html".

  After setting up everything, tried to install "FFMPEG" from "http://www.nixgurus.com/fedora/installing-ffmpeg-using-yum-on-centos-redhat-fedora/". This is the only guide which gets completed with successful installation and configuration, otherwise all other tried tutorials got leave me middle of nowhere.

  Note : While installing FFMPEG following above provided URL, "phpize" did not work to me so I had to install php-devel by running "yum install php-devel" command. I always got different "Zend Module" and "Zend Extension API" versions.

  When I installed ffmpeg and put extension in "php.ini" with correct path, it never appeared in phpinfo().

  Then after searching, I got a hint that installed "FFMPEG" will not be compatible to the installed PHP version. So I removed complete pack of XAMMP-LINUX and installed old one with Xampp-Linux-1.8.2 including PHP 5.4. But it result were same.

  Then, I decided to use more older version and it was Xampp-Linux-1.8.1 including PHP 5.4. Now currently I have this version but having version results are totally changed that after installation of FFMPEG when I put ffmpeg.so with its correct path in PHP.INI (definitely restart the server on every change) server behaves strange way that PHP files get downloaded by browsers and when I comment same line and restart web server everything works well.

  Just to let you know that, even I have given path "extension=/usr/lib/php/modules/ffmpeg.so" which did not work and even moved files to default extension path "/opt/lampp/lib/php/extensions/no-debug-non-zts-20100525" as well but in vain.

  Looking forward to your help please.