Recherche avancée

Sur d’autres sites (12833)

• 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.

• Building FFmpeg for Android

  13 juin 2013, par varevarao

  I've spent almost a week on this now, trying to get FFmpeg "Angel"/"Happiness" to build for Android.
  I've tried build scripts from all over the internet to no avail. I got closest was using this. As the author himself says the script doesn't work for newer versions of FFmpeg due to this bug, which has been dismissed on that ticket saying "I found a Makefile that does it." This was dis-heartening, being the only post on all of the vast Google world that was anywhere close to my problem.
  So, question time :

  Is there a way to get around the above bug ? I'm trying to use the newest ffmpeg API, and "Love" is just giving me "undefined reference" errors while trying to use av_encode_video2(), and av_free_frame(). The code I was working on the lines of is at the ffmpeg git repo, under /doc/examples/decoding_encoding.c (the function starting on line 338).

  Update : So they've done away with codec_names.sh in "Angel". Sorry didn't notice that before, but the problem persists in a different avatar now. With every build attempt the compiler throws a certain

  start ndk-building...
  
  /home/<user>/android-ndk/build/core/build-binary.mk:41: *** target file `clean&#39; has both : and :: entries.  Stop.
  
  </user>

  Say whatnow !?

• ffmpeg error while converting to mp4 Error while opening encoder for output stream #0.0

  20 mars 2016, par Josh

  I am trying to convert various file types to mp4 to be displayed using ffmpeg, but i keep getting the error :

  Error while opening encoder for output stream #0.0 - maybe incorrect parameters such as bit_rate, rate, width or height

  Another piece that looks important is :

  [libx264 @ 0x93caef0] broken ffmpeg default settings detected

  [libx264 @ 0x93caef0] use an encoding preset (e.g. -vpre medium)

  [libx264 @ 0x93caef0] preset usage : -vpre -vpre

  [libx264 @ 0x93caef0] speed presets are listed in x264 —help

  [libx264 @ 0x93caef0] profile is optional ; x264 defaults to high

  The latest code I am running is :

  ffmpeg -i source -s 320x240 -r 30000/1001 -b 200k -bt 240k -vcodec libx264 -coder 0 -bf 0 -refs 1 -flags2 -wpred-dct8x8 -level 30 -maxrate 10M -bufsize 10M -acodec libfaac -ac 2 -ar 48000 -ab 192k destination

  I have seen a few other people with this issue, but their fixes didn’t work for some reason.

  In case it matters : ultimately this will be used in php, though I am trying to get it working first via putty

  EDIT: : Here is the full thing as requested(using a wmv, have tested wmv and flv) :

       ~ >> ffmpeg -i path.wmv -s 320x240 -r 30000/1001 -b 200k -r 29.97 -bt 240k -vcodec libx264 -coder 0 -bf 0 -refs 1 -flags2 -wpred-dct8x8 -level 30 -maxrate 10M -bufsize 10M -acodec libfaac -ac 2 -ar 48000 -ab 192k path.mp4
  
  FFmpeg version SVN-r26076, Copyright (c) 2000-2011 the FFmpeg developers
  
    built on Aug 28 2012 17:55:47 with gcc 4.1.2 20080704 (Red Hat 4.1.2-52)
  
    configuration: --enable-version3 --enable-gpl --enable-nonfree --enable-shared --enable-postproc --enable-avfilter --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --disable-ffplay --disable-indevs --disable-outdevs --disable-demuxer=v4l --disable-demuxer=v4l2 --disable-mmx
  
    libavutil     50.36. 0 / 50.36. 0
  
    libavcore      0.16. 1 /  0.16. 1
  
    libavcodec    52.108. 0 / 52.108. 0
  
    libavformat   52.93. 0 / 52.93. 0
  
    libavdevice   52. 2. 3 / 52. 2. 3
  
    libavfilter    1.74. 0 /  1.74. 0
  
    libswscale     0.12. 0 /  0.12. 0
  
    libpostproc   51. 2. 0 / 51. 2. 0
  
  
  
  Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000/1) -> 29.97 (30000/1001)
  
  Input #0, asf, from 'path.wmv':
  
    Metadata:
  
      SfOriginalFPS   : 299
  
      WMFSDKVersion   : 11.0.6001.7000
  
      WMFSDKNeeded    : 0.0.0.0000
  
      IsVBR           : 0
  
      title           : Wildlife in HD
  
      artist          :
  
      copyright       : © 2008 Microsoft Corporation
  
      comment         : Footage: Small World Productions, Inc; Tourism New Zealand | Producer: Gary F. Spradling | Music: Steve Ball
  
    Duration: 00:00:30.09, start: 8.000000, bitrate: 6977 kb/s
  
      Stream #0.0(eng): Audio: wmav2, 44100 Hz, 2 channels, s16, 192 kb/s
  
      Stream #0.1(eng): Video: vc1, yuv420p, 1280x720, 5942 kb/s, 29.97 tbr, 1k tbn, 1k tbc
  
  File 'path.mp4' already exists. Overwrite ? [y/N] y
  
  [buffer @ 0x9ce9eb0] w:1280 h:720 pixfmt:yuv420p
  
  [scale @ 0x9ce8f70] w:1280 h:720 fmt:yuv420p -> w:320 h:240 fmt:yuv420p flags:0x4
  
  [libx264 @ 0x9ce9ef0] broken ffmpeg default settings detected
  
  [libx264 @ 0x9ce9ef0] use an encoding preset (e.g. -vpre medium)
  
  [libx264 @ 0x9ce9ef0] preset usage: -vpre <speed> -vpre <profile>
  
  [libx264 @ 0x9ce9ef0] speed presets are listed in x264 --help
  
  [libx264 @ 0x9ce9ef0] profile is optional; x264 defaults to high
  
  Output #0, mp4, to 'path.mp4':
  
      Stream #0.0(eng): Video: libx264, yuv420p, 320x240, q=2-31, 200 kb/s, 90k tbn, 29.97 tbc
  
      Stream #0.1(eng): Audio: libfaac, 48000 Hz, 2 channels, s16, 192 kb/s
  
  Stream mapping:
  
    Stream #0.1 -> #0.0
  
    Stream #0.0 -> #0.1
  
  Error while opening encoder for output stream #0.0 - maybe incorrect parameters such as bit_rate, rate, width or height
  
  </profile></speed>

  Thanks for any help