W3C home > Mailing lists > Public > public-privacy@w3.org > January to March 2012

Re: Privacy Design Guidelines by GSMA

From: Richard Barnes <richard.barnes@gmail.com>
Date: Mon, 26 Mar 2012 11:11:15 +0200
Message-ID: <CACB24MuRsM+xzu6PBrktnHtQnNeKsqjFFCaoa3ULH862wfBLWg@mail.gmail.com>
To: Karl Dubost <karld@opera.com>
Cc: "public-privacy (W3C mailing list)" <public-privacy@w3.org>
I'm a little puzzled here.  GSMA is an carrier association, not an app
developer association.  (And those are *very* *different*
communities.)  Did anyone actually talk to app developers about this?

On skimming, the content looks pretty non-controversial (at least for
this crowd), but I have serious doubts about a carrier-generated
document getting implemented by developers.  For example, the carriers
might be happy to say "don't collect personal information", since
their revenue streams don't depend on it; empirically, app developers
have a very different opinion.


On Mon, Mar 26, 2012 at 11:03 AM, Karl Dubost <karld@opera.com> wrote:
> The GSMA organization has published guidelines for people creating mobile applications.
> There is at the beginning some definitions about the terms in the guidelines.
>  Privacy: Privacy is a dynamic concept that can mean different things
>  to different people. For the purposes of these guidelines, privacy
>  is defined as the ability of individuals to know how their personal
>  information will be collected, shared and used, and to exercise
>  choice and control over its use.
>   http://www.gsma.com/documents/privacy-design-guidelines-for-mobile-application-development/20008
> Then follow a list of principles with for each of them
> * Guideline
> * Implementation
> * Use Case and Examples
> There is also a website http://www.gsma.com/mobile-and-privacy/
> --
> Karl Dubost - http://dev.opera.com/
> Developer Relations, Opera Software
Received on Monday, 26 March 2012 09:11:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:49:22 UTC