Recherche avancée

Sur d’autres sites (8576)

• Google Analytics Now Illegal in Austria ; Other EU Member States Expected to Follow

  18 janvier 2022, par Erin — Privacy

  Breaking news : The Austrian Data Protection Authority (“Datenschutzbehörde” or “DSB” or “DPA”) has ruled that Austrian website providers using Google Analytics are in violation of the GDPR. 

  This ruling stems from a decision made in 2020 by the Court of Justice of the European Union (CJEU) that stated that cloud services hosted in the US are incapable of complying with the GDPR and EU privacy laws. The decision was made because of the US surveillance laws requiring US providers (like Google or Facebook) to provide personal data to US authorities. 

  The 2020 ruling, known as “Schrems II”, marked the ending of the Privacy Shield, a framework that allowed for EU data to be transferred to US companies that became certified. 

  The tech industry was sent into a frenzy following this decision, but many US and EU companies decided to ignore the case. The choice to ignore is what landed one Austrian business in the DPA’s line of fire, damaging the brand’s reputation and possibly resulting in a hefty fine of up to €20 million or 4% of the organisation’s global turnover. 

  About the Austrian DPA’s Model Case 

  In this specific case, noyb (the European Center for Digital Rights) found that IP addresses (which are classified as personal data by the GDPR) and other identifiers were sent to the US in cookie data as a result of the organisation using Google Analytics. 

  This model case led to the DPA’s decision to rule that Austrian website providers using Google Analytics are in violation of GDPR. It is believed that other EU Member States will soon follow in this decision as well.

  "We expect similar decisions to now drop gradually in most EU member states. We have filed 101 complaints in almost all Member States and the authorities coordinated the response. A similar decision was also issued by the European Data Protection Supervisor last week."

  What does this mean if you are using Google Analytics ?

  If there is one thing to learn from this case, it is that ignoring these court rulings and continuing to use Google Analytics is not a viable option. 

  If you are operating a website in Austria, or your website services Austrian citizens, you should remove Google Analytics from your website immediately. 

  For businesses in other EU Member States, it is also highly recommended that you take action before noyb and local data protection authorities start targeting more businesses. 

  "Instead of actually adapting services to be GDPR compliant, US companies have tried to simply add some text to their privacy policies and ignore the Court of Justice. Many EU companies have followed the lead instead of switching to legal options."

  Removing Google Analytics from your site doesn’t mean that you need to give up website analytics altogether though. There are a variety of Google Analytics alternatives available today. Matomo in particular is a powerful open-source web analytics platform that gives you 100% data ownership and GDPR compliance. 

  

  Matomo is one of the best Google Analytics alternatives offering privacy by design on our Cloud, On-Premise and Matomo for WordPress. So you can get the insights you need while remaining compliant. As the GDPR continues to evolve, you can rest assured that Matomo will be at the forefront of these changes. 

  In addition, all Google Analytics data can be imported into Matomo so no historical data is lost. To make your migration as seamless as possible, we’ve put together a guide to migrating from Google Analytics to Matomo. 

  Ready to begin your journey to GDPR compliance ? Check out our live demo and start your 21-day free trial now – no credit card required.

  If you are interested in learning more about GDPR compliance and Matomo, check out our GDPR resources below :    

  • GDPR Manager user guide
  • How to fill in the information asset registration when using Matomo
  • How to make Matomo GDPR compliant in 12 easy steps
  • How to not process any personal data with Matomo and what it means for you
  • PII, personal data and GDPR. Discover what this means for your privacy
  • How should I write my privacy notice for Matomo Analytics under GDPR
  • Lawful basis for processing personal data under GDPR with Matomo
  • How to complete your privacy policy with Matomo Analytics under GDPR
  • GDPR compliance for Premium Features
  • How to get your Matomo plugin ready for GDPR
  • Subprocessors on Matomo Cloud (subprocessors not applicable to On-Premise)
  • Privacy in Matomo

  What does this mean if you are using Matomo ? 

  Our users can rest assured that Matomo remains in compliance with GDPR as all data is stored in the EU (Matomo Cloud) or in any country of your choice (Matomo On-Premise). With Matomo you’re able to continue analysing your website and not worry about GDPR.

  Final thoughts

  For EU businesses operating websites, now is the time to act. While Google pushes out false narratives to try and convince users that it is safe to continue using Google Analytics, it’s clear from these court rulings that the data protection authorities across the EU disagree with Google’s narrative.

  The fines, reputational damage and stresses mounting from using Google Analytics are imminent. Find an alternative to Google Analytics as this problem is not going away. 

  Getting started with Matomo is easy. Make the switch today and start your free 21-day trial – no credit card required. 

• Error decoding a simple audio file using FFmpeg library

  29 mars 2017, par satyres

  After successfuly compiling the latest version of FFmpeg library and generated .a library in Ubuntu I’ve been struggling now for more than a week to decode and play a simple mp3 file in Android without a success !
  I’ve followed this tutorial given by FFmpeg team in Github i’ve tried to use it in Android but no luck !
  here is the Native code.

  void Java_com_example_home_hellondk_MainActivity_audio_1decode_1example(JNIEnv * env, jobject obj, jstring file, jbyteArray array) {
  
      jboolean isfilenameCopy;
  
      const char * filename = ( * env) - > GetStringUTFChars(env, file, &
  
          isfilenameCopy);
  
      jclass cls = ( * env) - > GetObjectClass(env, obj);
  
      jmethodID play = ( * env) - > GetMethodID(env, cls, "playSound", "([BI)V");
  
      AVCodec * codec;
  
      AVCodecContext * c = NULL;
  
      int len;
  
      FILE * f, * outfile;
  
      uint8_t inbuf[AUDIO_INBUF_SIZE + AV_INPUT_BUFFER_PADDING_SIZE];
  
      AVPacket avpkt;
  
      AVFrame * decoded_frame = NULL;
  
  
  
      av_init_packet( & avpkt);
  
  
  
      printf("Decode audio file %s \n", filename);
  
      LOGE("Decode audio file %s\n", filename);
  
      /* find the MPEG audio decoder */
  
      codec = avcodec_find_decoder(AV_CODEC_ID_MP3);
  
      if (!codec) {
  
          fprintf(stderr, "Codec not found\n");
  
          LOGE("Codec not found\n");
  
          exit(1);
  
      }
  
  
  
      c = avcodec_alloc_context3(codec);
  
      if (!c) {
  
          fprintf(stderr, "Could not allocate audio codec context\n");
  
          LOGE("Could not allocate audio codec context\n");
  
          exit(1);
  
      }
  
  
  
      /* open it */
  
      if (avcodec_open2(c, codec, NULL) < 0) {
  
          fprintf(stderr, "Could not open codec\n");
  
          LOGE("Could not open codec\n");
  
          exit(1);
  
      }
  
  
  
      f = fopen(filename, "rb");
  
      if (!f) {
  
          fprintf(stderr, "Could not open %s\n", filename);
  
          LOGE("Could not open %s\n", filename);
  
          exit(1);
  
      }
  
  
  
  
  
      /* decode until eof */
  
      avpkt.data = inbuf;
  
      avpkt.size = fread(inbuf, 1, AUDIO_INBUF_SIZE, f);
  
  
  
      while (avpkt.size > 0) {
  
          int i, ch;
  
          int got_frame = 0;
  
  
  
          if (!decoded_frame) {
  
              if (!(decoded_frame = av_frame_alloc())) {
  
                  fprintf(stderr, "Could not allocate audio frame\n");
  
                  LOGE("Could not allocate audio frame\n");
  
                  exit(1);
  
              }
  
          }
  
  
  
          len = avcodec_decode_audio4(c, decoded_frame, & got_frame, & avpkt);
  
          if (len < 0) {
  
              fprintf(stderr, "Error while decoding\n");
  
              LOGE("Error while decoding\n");
  
              exit(1);
  
          }
  
          if (got_frame) {
  
              /* if a frame has been decoded, output it */
  
              int data_size = av_get_bytes_per_sample(c - > sample_fmt);
  
              if (data_size < 0) {
  
                  /* This should not occur, checking just for paranoia */
  
                  fprintf(stderr, "Failed to calculate data size\n");
  
                  LOGE("Failed to calculate data size\n");
  
                  exit(1);
  
              }
  
              if (data_size > 0) {
  
  
  
                  jbyte * bytes = ( * env) - > GetByteArrayElements(env, array, NULL);
  
                  memcpy(bytes, decoded_frame, got_frame); //
  
                  ( * env) - > ReleaseByteArrayElements(env, array, bytes, 0);
  
                  ( * env) - > CallVoidMethod(env, obj, play, array, got_frame);
  
                  LOGE("DECODING ERROR5");
  
              }
  
          }
  
          avpkt.size -= len;
  
          avpkt.data += len;
  
          avpkt.dts =
  
              avpkt.pts = AV_NOPTS_VALUE;
  
          if (avpkt.size < AUDIO_REFILL_THRESH) {
  
              /* Refill the input buffer, to avoid trying to decode
  
               * incomplete frames. Instead of this, one could also use
  
               * a parser, or use a proper container format through
  
               * libavformat. */
  
              memmove(inbuf, avpkt.data, avpkt.size);
  
              avpkt.data = inbuf;
  
              len = fread(avpkt.data + avpkt.size, 1,
  
                  AUDIO_INBUF_SIZE - avpkt.size, f);
  
              if (len > 0)
  
                  avpkt.size += len;
  
          }
  
      }
  
  
  
  
  
      fclose(f);
  
  
  
      avcodec_free_context( & c);
  
      av_frame_free( & decoded_frame);
  
  
  
  }

  The Java code :

  package com.example.home.hellondk;
  
  
  
  import android.media.AudioFormat;
  
  import android.media.AudioManager;
  
  import android.media.AudioTrack;
  
  import android.media.MediaPlayer;
  
  import android.support.v7.app.AppCompatActivity;
  
  import android.os.Bundle;
  
  import android.util.Log;
  
  
  
  import java.io.File;
  
  import java.io.FileNotFoundException;
  
  import java.io.FileOutputStream;
  
  import java.io.IOException;
  
  
  
  public class MainActivity extends AppCompatActivity {
  
      static {
  
          System.loadLibrary("MyLibraryPlayer");
  
      }
  
      public native void createEngine();
  
  
  
      public native void audio_decode_example(String outfilename, byte[] array);
  
  
  
  
  
  
  
      private AudioTrack track;
  
      private FileOutputStream os;
  
  
  
      @Override
  
      protected void onCreate(Bundle savedInstanceState) {
  
          super.onCreate(savedInstanceState);
  
          setContentView(R.layout.activity_main);
  
          createEngine();
  
  
  
   /*        MediaPlayer mp = new MediaPlayer();
  
          mp.start();*/
  
  
  
          int bufSize = AudioTrack.getMinBufferSize(32000,
  
                  AudioFormat.CHANNEL_CONFIGURATION_STEREO,
  
                  AudioFormat.ENCODING_PCM_16BIT);
  
  
  
          track = new AudioTrack(AudioManager.STREAM_MUSIC,
  
                  32000,
  
                  AudioFormat.CHANNEL_CONFIGURATION_STEREO,
  
                  AudioFormat.ENCODING_PCM_16BIT,
  
                  bufSize,
  
                  AudioTrack.MODE_STREAM);
  
  
  
          byte[] bytes = new byte[bufSize];
  
  
  
          try {
  
              os = new FileOutputStream("/storage/emulated/0/Cloud Radio/a.out", false);
  
          } catch (FileNotFoundException e) {
  
              // TODO Auto-generated catch block
  
              e.printStackTrace();
  
          }
  
     audio_decode_example("/storage/emulated/0/Cloud Radio/test.mp3", bytes);
  
  
  
      }
  
  
  
      void playSound(byte[] buf, int size) {
  
          //android.util.Log.v("ROHAUPT", "RAH Playing");
  
          if (track.getPlayState() != AudioTrack.PLAYSTATE_PLAYING)
  
              track.play();
  
          track.write(buf, 0, size);
  
  
  
          try {
  
              os.write(buf, 0, size);
  
          } catch (IOException e) {
  
              // TODO Auto-generated catch block
  
              e.printStackTrace();
  
          }
  
      }
  
  }

  I always got this error : Error while decoding .
  i’ve tried to change the decoder "AV_CODEC_ID_MP3" no sucess !
  Thank you so much for your help.
  Kind regards

• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.