Recherche avancée

Sur d’autres sites (11800)

• How to make Matomo GDPR compliant in 12 steps

  3 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. 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.

  The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

  The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

  We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

  The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

  As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

  If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

  1 – Awareness

  Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

  2 – Information you hold

  List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

  3 – Communicating privacy information

  a – Add a privacy notice

  Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

  b – Add Matomo to your privacy policy page

  Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

  4 – Individuals’ rights

  Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

  5 – Subject access requests

  Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

  6 – Lawful basis for processing personal data

  There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

  7 – Consent

  Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
  We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

  8 – Children

  If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

  9 – Data breaches

  As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

  10 – Data Protection by Design and Data Protection Impact Assessments

  Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

  11 – Data Protection Officers

  If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

  12 – International

  Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
  Note : our Matomo cloud infrastructure is based in France.

  That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

  The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.

• avcodec : add emuedge_linesize_type

  4 septembre 2013, par Michael Niedermayer

  avcodec : add emuedge_linesize_type
  Currently all uses of the emu edge code as well as the code itself
  
  assume int linesize
  
  changing some but not changing all would introduce a security issue
  
  once all use this typedef a simple search and replace can be
  
  done to switch them all to ptrdiff_t
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/mpegvideo_motion.c
  • [DH] libavcodec/videodsp.h
  • [DH] libavcodec/videodsp_template.c
  • [DH] libavcodec/x86/videodsp_init.c

• Find out what device to use for capturing with ffmpeg ?

  14 septembre 2013, par wvxvw

  I'm trying to broadcast my screen and I cannot capture audio. There's one complication however. I don't have pulseaudio, and it simply doesn't work on my system, so installing it is out of question. Below is the command I'm trying :

  ffmpeg -f alsa -i ??? -f x11grab -s 1920x1200 -r 15 -i :0.0 \
  
      -acodec pcm_s16le -vcodec libx264 \
  
      -preset fast -pix_fmt yuv420p -s 1280x800 -threads 0 -f flv "$URL"

  Here's the list of my audio devices :

  $ aplay -L
  
  null
  
      Discard all samples (playback) or generate zero samples (capture)
  
  default:CARD=PCH
  
      HDA Intel PCH, ALC269VB Analog
  
      Default Audio Device
  
  sysdefault:CARD=PCH
  
      HDA Intel PCH, ALC269VB Analog
  
      Default Audio Device
  
  front:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      Front speakers
  
  surround40:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      4.0 Surround output to Front and Rear speakers
  
  surround41:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      4.1 Surround output to Front, Rear and Subwoofer speakers
  
  surround50:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      5.0 Surround output to Front, Center and Rear speakers
  
  surround51:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  
  surround71:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Analog
  
      7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  
  iec958:CARD=PCH,DEV=0
  
      HDA Intel PCH, ALC269VB Digital
  
      IEC958 (S/PDIF) Digital Audio Output
  
  hdmi:CARD=NVidia,DEV=0
  
      HDA NVidia, HDMI 0
  
      HDMI Audio Output
  
  hdmi:CARD=NVidia,DEV=1
  
      HDA NVidia, HDMI 0
  
      HDMI Audio Output
  
  hdmi:CARD=NVidia,DEV=2
  
      HDA NVidia, HDMI 0
  
      HDMI Audio Output
  
  hdmi:CARD=NVidia,DEV=3
  
      HDA NVidia, HDMI 0
  
      HDMI Audio Output

  I know that ??? should be something like hw:X,Y, but maybe it can be something else. I can't find the corresponding entry in the man page.

  As an aside, it would be great if you can suggest another audio codec. I can't find what are the options, and this particular one isn't compatible with FLV because of too high bitrate.

  PS. This is the error I'm getting :

  Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input