Good idea!

Since there are lot's of

• countries with different legal terms,
• different use-cases for piwiks tracking technology (in web, in intra net, in internal software etc)
• different opinions

we should users give always the choice to use piwik how they like and need it
-within full bandwidth from strictly privacy and anonymity to detailed tracking of personal data.
=> one idea could be to give special best practise advices for several different scenarios

to answer one of the questions "How can we encourage such 'good' behaviour?"
with a concrete idea:
we should give not only a black and a white solution but also the steps between this,
otherwise the black solution has to be chosen when a grey solution would be enough.
one place where this is easily visible is the "Do not track function setting" where simply a third 3.state needed
see #6147

@hpvd good points. a lot can be done in the area of Privacy! we will make a lot of progress with regards to privacy over the next year.

Here are important goals regarding Privacy:

• make Piwik adhere to the User Data Manifesto Adhere to the User Data Manifesto 2.0 #6197 (and join the GNU family at Piwik to become official GNU package #5276)
• make Piwik privacy default settings with best privacy options
  • Maybe 50% of users will never change default settings and therefore we have a chance deploy most analytics platform with full privacy built-in!
  • privacy features: IP anonimisation Enable IP anonymisation by default, let users disable anonymisation during Piwik installation #5052, Accept-language keep only one Do not store Accept-language full string, only store detected language #5365, prevent fingerprinting with daily random IP address hash seed When IP anonimisation is enabled, hash the IP address in a way that prevents long-term fingerprinting #5907,
• inform Piwik admin of any privacy legislation requirement in country Notify Piwik user if Privacy options are not configured according to local legislation #5350
• inform anyone of the current level of privacy features enabled in a Piwik server.
  • Publicly acknowledge the privacy features enabled in Piwik Explain in opt-out iframe what data privacy measures are in place in Piwik #2889 eg. in the Opt-out iframe
  • For example we could create a privacy Seal that could be displayed as a widget embed or image embed, that would be active only when full privacy is enabled in Piwik Create a Privacy Seal  #6173

what do you think?

interesting link from @diosmosis

Mozilla’s five Data Privacy Principles are:

NO SURPRISES
Use and share information in a way that is transparent and benefits the user.

USER CONTROL
Develop products and advocate for best practices that put users in control of their data and online experiences.

LIMITED DATA
Collect what we need, de-identify where we can and delete when no longer necessary.

SENSIBLE SETTINGS
Design for a thoughtful balance of safety and user experience.

DEFENSE IN DEPTH
Maintain multi-layered security controls and practices, many of which are publicly verifiable.

We've made some good progress in clarifying privacy in the last few months. This issue stays open to keep discussion alive, but i'm moving to Mid term milestone.

#6160 (comment)