Hi Rob, On Friday, 2011-08-12 16:42:20 -0400, Rob Weir wrote:
> > The big difference is that with Piwik the data collected stays inhouse > > at Apache, whereas with Google it goes to Google that does whatever you > > don't know. This again implies that at Apache measures must be taken to > > protect the privacy of collected data. The German "Landeszentrum für > > Datenschutz Schleswig-Holstein" (center of data protection) has a few > > documents about tracking [1], unfortunately only in German, why Google > > Analytics doesn't comply with the German data protection law [2] and how > > Piwik can be configured to be used in compliance with the law [3]. > > > > Does this law matter if the servers are hosted in the US, not in > Germany? (I'm assuming that the Apache servers are in the US). No, but given that German data protection law is probably one of the more strict, setting up an environment that fulfills those requirements seemst to be a good approach to me. > Storing the data ourselves is a double-edged sword. If we store it, > then we are responsible for any problems with that data. Yes. And configuring Piwik the way described there it does not store personally identifiable data. > Google states what they can do with the data, but it is rather broad, > as you know. Yes, but we shouldn't discuss that here. All I said was there is an alternative that doesn't store personally identifiable data and also doesn't give it away to someone else to process. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
pgpJPW87xe0oi.pgp
Description: PGP signature
