Recherche avancée

Sur d’autres sites (7589)

• TCP connection refused with FFMPEG

  2 février 2017, par Samul

  OFFICIAL EDIT :

  I thank you so much for your help but I am still encountering problems.

  My ffserver.conf file is like this :

  # Port on which the server is listening. You must select a different
  
  # port from your standard HTTP web server if it is running on the same
  
  # computer.
  
  HTTPPort 8090
  
  
  
  # Address on which the server is bound. Only useful if you have
  
  # several network interfaces.
  
  HTTPBindAddress 0.0.0.0
  
  
  
  # Number of simultaneous HTTP connections that can be handled. It has
  
  # to be defined *before* the MaxClients parameter, since it defines the
  
  # MaxClients maximum limit.
  
  MaxHTTPConnections 2000
  
  
  
  # Number of simultaneous requests that can be handled. Since FFServer
  
  # is very fast, it is more likely that you will want to leave this high
  
  # and use MaxBandwidth, below.
  
  MaxClients 1000
  
  
  
  # This the maximum amount of kbit/sec that you are prepared to
  
  # consume when streaming to clients.
  
  MaxBandwidth 1000
  
  
  
  # Access log file (uses standard Apache log file format)
  
  # '-' is the standard output.
  
  CustomLog -
  
  
  
  ##################################################################
  
  # Definition of the live feeds. Each live feed contains one video
  
  # and/or audio sequence coming from an ffmpeg encoder or another
  
  # ffserver. This sequence may be encoded simultaneously with several
  
  # codecs at several resolutions.
  
  
  
  <feed>
  
  
  
  # You must use 'ffmpeg' to send a live feed to ffserver. In this
  
  # example, you can type:
  
  #
  
  # ffmpeg http://localhost:8090/feed1.ffm
  
  
  
  # ffserver can also do time shifting. It means that it can stream any
  
  # previously recorded live stream. The request should contain:
  
  # "http://xxxx?date=[YYYY-MM-DDT][[HH:]MM:]SS[.m...]".You must specify
  
  # a path where the feed is stored on disk. You also specify the
  
  # maximum size of the feed, where zero means unlimited. Default:
  
  # File=/tmp/feed_name.ffm FileMaxSize=5M
  
  File /tmp/feed1.ffm
  
  FileMaxSize 200K
  
  
  
  # You could specify
  
  # ReadOnlyFile /saved/specialvideo.ffm
  
  # This marks the file as readonly and it will not be deleted or updated.
  
  
  
  # Specify launch in order to start ffmpeg automatically.
  
  # First ffmpeg must be defined with an appropriate path if needed,
  
  # after that options can follow, but avoid adding the http:// field
  
  #Launch ffmpeg
  
  
  
  # Only allow connections from localhost to the feed.
  
  #ACL allow 127.0.0.1
  
  #ACL allow 189.34.0.158
  
  </feed>
  
  
  
  
  
  ##################################################################
  
  # Now you can define each stream which will be generated from the
  
  # original audio and video stream. Each format has a filename (here
  
  # 'test1.mpg'). FFServer will send this stream when answering a
  
  # request containing this filename.
  
  
  
  <stream>
  
  
  
  # coming from live feed 'feed1'
  
  Feed feed1.ffm
  
  
  
  # Format of the stream : you can choose among:
  
  # mpeg       : MPEG-1 multiplexed video and audio
  
  # mpegvideo  : only MPEG-1 video
  
  # mp2        : MPEG-2 audio (use AudioCodec to select layer 2 and 3 codec)
  
  # ogg        : Ogg format (Vorbis audio codec)
  
  # rm         : RealNetworks-compatible stream. Multiplexed audio and video.
  
  # ra         : RealNetworks-compatible stream. Audio only.
  
  # mpjpeg     : Multipart JPEG (works with Netscape without any plugin)
  
  # jpeg       : Generate a single JPEG image.
  
  # asf        : ASF compatible streaming (Windows Media Player format).
  
  # swf        : Macromedia Flash compatible stream
  
  # avi        : AVI format (MPEG-4 video, MPEG audio sound)
  
  Format mpeg
  
  
  
  # Bitrate for the audio stream. Codecs usually support only a few
  
  # different bitrates.
  
  AudioBitRate 32
  
  
  
  # Number of audio channels: 1 = mono, 2 = stereo
  
  AudioChannels 1
  
  
  
  # Sampling frequency for audio. When using low bitrates, you should
  
  # lower this frequency to 22050 or 11025. The supported frequencies
  
  # depend on the selected audio codec.
  
  AudioSampleRate 44100
  
  
  
  # Bitrate for the video stream
  
  VideoBitRate 64
  
  
  
  # Ratecontrol buffer size
  
  VideoBufferSize 40
  
  
  
  # Number of frames per second
  
  VideoFrameRate 3
  
  
  
  # Size of the video frame: WxH (default: 160x128)
  
  # The following abbreviations are defined: sqcif, qcif, cif, 4cif, qqvga,
  
  # qvga, vga, svga, xga, uxga, qxga, sxga, qsxga, hsxga, wvga, wxga, wsxga,
  
  # wuxga, woxga, wqsxga, wquxga, whsxga, whuxga, cga, ega, hd480, hd720,
  
  # hd1080
  
  VideoSize 160x128
  
  
  
  # Transmit only intra frames (useful for low bitrates, but kills frame rate).
  
  #VideoIntraOnly
  
  
  
  # If non-intra only, an intra frame is transmitted every VideoGopSize
  
  # frames. Video synchronization can only begin at an intra frame.
  
  VideoGopSize 12
  
  
  
  # More MPEG-4 parameters
  
  # VideoHighQuality
  
  # Video4MotionVector
  
  
  
  # Choose your codecs:
  
  #AudioCodec mp2
  
  #VideoCodec mpeg1video
  
  
  
  # Suppress audio
  
  #NoAudio
  
  
  
  # Suppress video
  
  #NoVideo
  
  
  
  #VideoQMin 3
  
  #VideoQMax 31
  
  
  
  # Set this to the number of seconds backwards in time to start. Note that
  
  # most players will buffer 5-10 seconds of video, and also you need to allow
  
  # for a keyframe to appear in the data stream.
  
  #Preroll 15
  
  
  
  # ACL:
  
  
  
  # You can allow ranges of addresses (or single addresses)
  
  #ACL ALLOW <first address="address"> <last address="address">
  
  
  
  # You can deny ranges of addresses (or single addresses)
  
  #ACL DENY <first address="address"> <last address="address">
  
  
  
  # You can repeat the ACL allow/deny as often as you like. It is on a per
  
  # stream basis. The first match defines the action. If there are no matches,
  
  # then the default is the inverse of the last ACL statement.
  
  #
  
  # Thus 'ACL allow localhost' only allows access from localhost.
  
  # 'ACL deny 1.0.0.0 1.255.255.255' would deny the whole of network 1 and
  
  # allow everybody else.
  
  
  
  </last></first></last></first></stream>
  
  
  
  
  
  ##################################################################
  
  # Example streams
  
  
  
  
  
  # Multipart JPEG
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format mpjpeg
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  #NoAudio
  
  #Strict -1
  
  #</stream>
  
  
  
  
  
  # Single JPEG
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format jpeg
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  ##VideoSize 352x240
  
  #NoAudio
  
  #Strict -1
  
  #</stream>
  
  
  
  
  
  # Flash
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format swf
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  # ASF compatible
  
  
  
  <stream>
  
  Feed feed1.ffm
  
  Format asf
  
  VideoFrameRate 15
  
  VideoSize 352x240
  
  VideoBitRate 256
  
  VideoBufferSize 40
  
  VideoGopSize 30
  
  AudioBitRate 64
  
  StartSendOnKey
  
  </stream>
  
  
  
  
  
  # MP3 audio
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format mp2
  
  #AudioCodec mp3
  
  #AudioBitRate 64
  
  #AudioChannels 1
  
  #AudioSampleRate 44100
  
  #NoVideo
  
  #</stream>
  
  
  
  
  
  # Ogg Vorbis audio
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Metadata title "Stream title"
  
  #AudioBitRate 64
  
  #AudioChannels 2
  
  #AudioSampleRate 44100
  
  #NoVideo
  
  #</stream>
  
  
  
  
  
  # Real with audio only at 32 kbits
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format rm
  
  #AudioBitRate 32
  
  #NoVideo
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  # Real with audio and video at 64 kbits
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format rm
  
  #AudioBitRate 32
  
  #VideoBitRate 128
  
  #VideoFrameRate 25
  
  #VideoGopSize 25
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # A stream coming from a file: you only need to set the input
  
  # filename and optionally a new format. Supported conversions:
  
  #    AVI -> ASF
  
  
  
  #<stream>
  
  #File "/usr/local/httpd/htdocs/tlive.rm"
  
  #NoAudio
  
  #</stream>
  
  
  
  #<stream>
  
  #File "/usr/local/httpd/htdocs/test.asf"
  
  #NoAudio
  
  #Metadata author "Me"
  
  #Metadata copyright "Super MegaCorp"
  
  #Metadata title "Test stream from disk"
  
  #Metadata comment "Test comment"
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # RTSP examples
  
  #
  
  # You can access this stream with the RTSP URL:
  
  #   rtsp://localhost:5454/test1-rtsp.mpg
  
  #
  
  # A non-standard RTSP redirector is also created. Its URL is:
  
  #   http://localhost:8090/test1-rtsp.rtsp
  
  
  
  #<stream>
  
  #Format rtp
  
  #File "/usr/local/httpd/htdocs/test1.mpg"
  
  #</stream>
  
  
  
  
  
  # Transcode an incoming live feed to another live feed,
  
  # using libx264 and video presets
  
  
  
  #<stream>
  
  #Format rtp
  
  #Feed feed1.ffm
  
  #VideoCodec libx264
  
  #VideoFrameRate 24
  
  #VideoBitRate 100
  
  #VideoSize 480x272
  
  #AVPresetVideo default
  
  #AVPresetVideo baseline
  
  #AVOptionVideo flags +global_header
  
  #
  
  #AudioCodec libfaac
  
  #AudioBitRate 32
  
  #AudioChannels 2
  
  #AudioSampleRate 22050
  
  #AVOptionAudio flags +global_header
  
  #</stream>
  
  
  
  ##################################################################
  
  # SDP/multicast examples
  
  #
  
  # If you want to send your stream in multicast, you must set the
  
  # multicast address with MulticastAddress. The port and the TTL can
  
  # also be set.
  
  #
  
  # An SDP file is automatically generated by ffserver by adding the
  
  # 'sdp' extension to the stream name (here
  
  # http://localhost:8090/test1-sdp.sdp). You should usually give this
  
  # file to your player to play the stream.
  
  #
  
  # The 'NoLoop' option can be used to avoid looping when the stream is
  
  # terminated.
  
  
  
  #<stream>
  
  #Format rtp
  
  #File "/usr/local/httpd/htdocs/test1.mpg"
  
  #MulticastAddress 224.124.0.1
  
  #MulticastPort 5000
  
  #MulticastTTL 16
  
  #NoLoop
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # Special streams
  
  
  
  # Server status
  
  
  
  <stream>
  
  Format status
  
  
  
  # Only allow local people to get the status
  
  ACL allow localhost
  
  ACL allow 192.168.0.0 192.168.255.255
  
  
  
  #FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
  
  </stream>
  
  
  
  
  
  # Redirect index.html to the appropriate site
  
  
  
  <redirect>
  
  URL http://www.ffmpeg.org/
  
  </redirect>

  I started my server and executed :

  ffserver -d -f /usr/share/doc/ffmpeg-2.6.8/ffserver.conf

  No error message and everything looks fine.

  After that I execute this (in your answer, I think you forgot the port number) :

  ffmpeg -i "rtsp://200.180.90.95:554/onvif1" -r 25 -s 640x480 -c:v libx264 -flags +global_header -f flv "http://45.79.207.38:8090/feed1.ffm"

  Then I get this log :

    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [pcm_alaw @ 0x1a24360] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  Invalid UE golomb code
  
  [h264 @ 0x1a23580] cbp too large (3199971767) at 76 33
  
  [h264 @ 0x1a23580] error while decoding MB 76 33
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 933 DC, 933 AC, 933 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [h264 @ 0x1a23580] cbp too large (62) at 50 24
  
  [h264 @ 0x1a23580] error while decoding MB 50 24
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1679 DC, 1679 AC, 1679 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1965 DC, 1965 AC, 1965 MV errors in P frame
  
  [pcm_alaw @ 0x1a24360] RTP: missed 1 packets
  
      Last message repeated 1 times
  
  [h264 @ 0x1a23580] RTP: missed 3 packets
  
  [h264 @ 0x1a23580] mb_type 49 in P slice too large at 74 25
  
  [h264 @ 0x1a23580] error while decoding MB 74 25
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1575 DC, 1575 AC, 1575 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] P sub_mb_type 29 out of range at 30 26
  
  [h264 @ 0x1a23580] error while decoding MB 30 26
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1539 DC, 1539 AC, 1539 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [h264 @ 0x1a23580] out of range intra chroma pred mode at 72 29
  
  [h264 @ 0x1a23580] error while decoding MB 72 29
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1257 DC, 1257 AC, 1257 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 3 packets
  
  [h264 @ 0x1a23580] negative number of zero coeffs at 48 5
  
  [h264 @ 0x1a23580] error while decoding MB 48 5
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 3201 DC, 3201 AC, 3201 MV errors in P frame
  
  [pcm_alaw @ 0x1a24360] RTP: missed 1 packets
  
  [rtsp @ 0x1a20ee0] decoding for stream 0 failed
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, rtsp, from 'rtsp://200.180.90.95:554/onvif1':
  
    Metadata:
  
      title           : H.264 Video, RtspServer_0.0.0.2
  
    Duration: N/A, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: h264 (Baseline), yuv420p, 1280x720, 90k tbr, 90k tbn, 180k tbc
  
      Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
  
  [libx264 @ 0x1b728a0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
  
  [libx264 @ 0x1b728a0] profile High, level 3.0
  
  [libx264 @ 0x1b728a0] 264 - core 142 r2495 6a301b6 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  [flv @ 0x1a66300] FLV does not support sample rate 8000, choose from (44100, 22050, 11025)
  
  [flv @ 0x1a66300] Audio codec mp3 not compatible with flv
  
  Output #0, flv, to 'http://45.79.207.38:8090/feed1.ffm':
  
    Metadata:
  
      title           : H.264 Video, RtspServer_0.0.0.2
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 640x480, q=-1--1, 25 fps, 1k tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc56.26.100 libx264
  
      Stream #0:1: Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 8000 Hz, mono, s16p
  
      Metadata:
  
        encoder         : Lavc56.26.100 libmp3lame
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:1 (pcm_alaw (native) -> mp3 (libmp3lame))
  
  Could not write header for output file #0 (incorrect codec parameters ?): Function not implemented

  I am doing this in a clean install of CENTOS, no customization. Could you please helpe me ?

• Google Analytics 4 and GDPR : Everything You Need to Know

  17 mai 2022, par Erin

  Four years have passed since the European General Data Protection Regulation (GDPR, also known as DSGVO in German, and RGPD in French) took effect.

  That’s ample time to get compliant, especially for an organisation as big and innovative as Google. Or is it ? 

  If you are wondering how GDPR affects Google Analytics 4 and what the compliance status is at present, here’s the lowdown. 

  Is Google Analytics 4 GDPR Compliant ?

  No. As of mid-2022, Google Analytics 4 (GA4) isn’t fully GDPR compliant. Despite adding extra privacy-focused features, GA4 still has murky status with the European regulators. After the invalidation of the Privacy Shield framework in 2020, Google is yet to regulate EU-US data protection. At present, the company doesn’t sufficiently protect EU citizens’ and residents’ data against US surveillance laws. This is a direct breach of GDPR.

  Google Analytics and GDPR : a Complex Relationship 

  European regulators have scrutinised Google since GDPR came into effect in 2018.

  While the company took steps to prepare for GDPR provisions, it didn’t fully comply with important regulations around user data storage, transfer and security.

  The relationship between Google and EU regulators got more heated after the Court of Justice of the European Union (CJEU) invalidated the Privacy Shield — a leeway Google used for EU-US data transfers. After 2020, GDPR litigation against Google followed. 

  This post summarises the main milestones in this story and explains the consequences for Google Analytics users. 

  

  2018 : Google Analytics Meets GDPR 

  In 2018, the EU adopted the General Data Protection Regulation (GDPR) — a set of privacy and data security laws, covering all member states. Every business interacting with EU citizens and/or residents had to comply.

  GDPR harmonised data protection laws across member states and put down extra provisions for what constitutes sensitive personal information (or PII). Broadly, PII includes any data about the person’s :

  • Racial or ethnic origin 
  • Employment status 
  • Religious or political beliefs
  • State of health 
  • Genetic or biometric data 
  • Financial records (such as payment method data)
  • Address and phone numbers 

  Businesses were barred from collecting this information without explicit consent (and even with it in some cases). If collected, such sensitive information is also subject to strict requirements on how it should be stored, secured, transferred and used. 

  7 Main GDPR Principles Explained 

  Article 5 of the GDPR lays out seven main GDPR principles for personal data and privacy protection : 

  • Lawfulness, fairness and transparency — data must be obtained legally, collected with consent and in adherence to laws. 
  • Purpose limitation — all personal information must be collected for specified, explicit and legal purposes. 
  • Data minimisation — companies must collect only necessary and adequate data, aligned with the stated purpose. 
  • Accuracy — data accuracy must be ensured at all times. Companies must have mechanisms to erase or correct inaccurate data without delays. 
  • Storage limitation — data must be stored only for as long as the stated purpose suggests. Though there’s no upper time limit on data storage. 
  • Integrity and confidentiality (security) — companies must take measures to ensure secure data storage and prevent unlawful or unauthorised access to it. 
  • Accountability — companies must be able to demonstrate adherence to the above principles. 

  Google claimed to have taken steps to make all of their products GDPR compliant ahead of the deadline. But in practice, this wasn’t always the case.

  In March 2018, a group of publishers admonished Google for not providing them with enough tools for GDPR compliance :

  “[Y]ou refuse to provide publishers with any specific information about how you will collect, share and use the data. Placing the full burden of obtaining new consent on the publisher is untenable without providing the publisher with the specific information needed to provide sufficient transparency or to obtain the requisite specific, granular and informed consent under the GDPR.”

  The proposed Google Analytics GDPR consent form was hard to implement and lacked customisation options. In fact, Google “makes unilateral decisions” on how the collected data is stored and used. 

  Users had no way to learn about or control all intended uses of people’s data — which made compliance with the second clause impossible. 

  Unsurprisingly, Google was among the first companies to face a GDPR lawsuit (together with Facebook). 

  By 2019, French data regulator CNIL, successfully argued that Google wasn’t sufficiently disclosing its data collection across products — and hence in breach of GDPR. After a failed appeal, Google had to pay a €50 million fine and promise to do better. 

  2019 : Google Analytics 4 Announcement 

  Throughout 2019, Google rightfully attempted to resolve some of its GDPR shortcomings across all products, Google Universal Analytics (UA) included. 

  They added a more visible consent mechanism for online tracking and provided extra compliance tips for users to follow. In the background, Google also made tech changes to its data processing mechanism to get on the good side of regulations.

  Though Google addressed some of the issues, they missed others. A 2019 independent investigation found that Google real-time-bidding (RTB) ad auctions still used EU citizens’ and residents’ data without consent, thanks to a loophole called “Push Pages”. But they managed to quickly patch this up before the allegations had made it to court. 

  In November 2019, Google released a beta version of the new product version — Google Analytics 4, due to replace Universal Analytics. 

  GA4 came with a set of new privacy-focused features for ticking GDPR boxes such as :

  • Data deletion mechanism. Users can now request to surgically extract certain data from the Analytics servers via a new interface. 
  • Shorter data retention period. You can now shorten the default retention period to 2 months by default (instead of 14 months) or add a custom limit.  
  • IP Anonymisation. GA4 doesn’t log or store IP addresses by default. 

  Google Analytics also updated its data processing terms and made changes to its privacy policy. 

  Though Google made some progress, Google Analytics 4 still has many limitations — and isn’t GDPR compliant. 

  2020 : Privacy Shield Invalidation Ruling 

  As part of the 2018 GDPR preparations, Google named its Irish entity (Google Ireland Limited) as the “data controller” legally responsible for EEA and Swiss users’ information. 

  The company announcement says : 

  

  Initially, Google assumed that this legal change would help them ensure GDPR compliance as “legally speaking” a European entity was set in charge of European data. 

  Practically, however, EEA consumers’ data was still primarily transferred and processed in the US — where most Google data centres are located. Until 2020, such cross-border data transfers were considered legal thanks to the Privacy Shield framework. 

  But in July 2020, The EU Court of Justice ruled that this framework doesn’t provide adequate data protection to digitally transmitted data against US surveillance laws. Hence, companies like Google can no longer use it. The Swiss Federal Data Protection and Information Commissioner (FDPIC) reached the same conclusion in September 2020. 

  The invalidation of the Privacy Shield framework put Google in a tough position.

   Article 14. f of the GDPR explicitly states : 

  “The controller (the company) that intends to carry out a transfer of personal data to a recipient (Analytics solution) in a third country or an international organisation must provide its users with information on the place of processing and storage of its data”.

  Invalidation of the Privacy Shield framework prohibited Google from moving data to the US. At the same time, GDPR provisions mandated that they must disclose proper data location. 

  But Google Analytics (like many other products) had no a mechanism for : 

  • Guaranteeing intra-EU data storage 
  • Selecting a designated regional storage location 
  • Informing users about data storage location or data transfers outside of the EU 

  And these factors made Google Analytics in direct breach of GDPR — a territory, where they remain as of 2022.

  2020-2022 : Google GDPR Breaches and Fines 

  The 2020 ruling opened Google to GDPR lawsuits from country-specific data regulators.

  Google Analytics in particular was under a heavy cease-fire. 

  • Sweden first fined Google for violating GDPR for no not fulfilling its obligations to request data delisting in 2020. 
  • France rejected Google Analytics 4 IP address anonymisation function as a sufficient measure for protecting cross-border data transfers. Even with it, US intelligence services can still access user IPs and other PII. France declared Google Analytics illegal and pressed a €150 million fine. 
  • Austria also found Google Analytics GDPR non-compliant and proclaimed the service as “illegal”. The authority now seeks a fine too. 

  The Dutch Data Protection Authority and  Norwegian Data Protection Authority also found Google Analytics guilty of a GDPR breach and seek to limit Google Analytics usage. 

  New privacy controls in Google Analytics 4 do not resolve the underlying issue — unregulated, non-consensual EU-US data transfer. 

  Google Analytics GDPR non-compliance effectively opens any website tracking or analysing European visitors to legal persecution.

  In fact, this is already happening. noyb, a European privacy-focused NGO, has already filed over 100 lawsuits against European websites using Google Analytics.

  2022 : Privacy Shield 2.0. Negotiations

  Google isn’t the only US company affected by the Privacy Shield framework invalidation. The ruling puts thousands of digital companies at risk of non-compliance.

  To settle the matter, US and EU authorities started “peace talks” in spring 2022.

  European Commission President Ursula von der Leyen said that they are working with the Biden administration on the new agreement that will “enable predictable and trustworthy data flows between the EU and US, safeguarding the privacy and civil liberties.” 

  However, it’s just the beginning of a lengthy negotiation process. The matter is far from being settled and contentious issues remain as we discussed on Twitter (come say hi !).

  

  For one, the US isn’t eager to modify its surveillance laws and is mostly willing to make them “proportional” to those in place in the EU. These modifications may still not satisfy CJEU — which has the power to block the agreement vetting or invalidate it once again. 

  While these matters are getting hashed out, Google Analytics users, collecting data about EU citizens and/or residents, remain on slippery grounds. As long as they use GA4, they can be subject to GDPR-related lawsuits. 

  To Sum It Up 

  • Google Analytics 4 and Google Universal Analytics are not GDPR compliant because of Privacy Shield invalidation in 2020. 
  • French and Austrian data watchdogs named Google Analytics operations “illegal”. Swedish, Dutch and Norwegian authorities also claim it’s in breach of GDPR. 
  • Any website using GA for collecting data about European citizens and/or residents can be taken to court for GDPR violations (which is already happening). 
  • Privacy Shield 2.0 Framework discussions to regulate EU-US data transfers have only begun and may take years. Even if accepted, the new framework(s) may once again be invalidated by local data regulators as has already happened in the past. 

  Time to Get a GDPR Compliant Google Analytics Alternative 

  Retaining 100% data ownership is the optimal path to GDPR compliance.

  By selecting a transparent web analytics solution that offers 100% data ownership, you can rest assured that no “behind the scenes” data collection, processing or transfers take place. 

  Unlike Google Analytics 4, Matomo offers all of the features you need to be GDPR compliant : 

  • Full data anonymisation 
  • Single-purpose data usage 
  • Easy consent and an opt-out mechanism 
  • First-party cookies usage by default 
  • Simple access to collect data 
  • Fast data removals 
  • EU-based data storage for Matomo Cloud (or storage in the country of your choice with Matomo On-Premise)

  Learn about your audiences in a privacy-centred way and protect your business against unnecessary legal exposure. 

  Start your 21-day free trial (no credit card required) to see how fully GDPR-compliant website analytics works ! 

  21 day free trial. No credit card required.

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I hereby accept the terms and conditions and the data processing agreeement (DPA).

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  

  » Start improving your websites now

  

• Revision 29748 : Mise à jour de l’ensembles des fonctions ... on peut passer maintenant à ...

  8 juillet 2009, par kent1@… — Log

  Mise à jour de l’ensembles des fonctions ... on peut passer maintenant à l’encodage multiple