WebProNews

Tag: Privacy Issues

  • NTIA Introduces Mobile App Code of Conduct For Privacy

    The U.S. National Telecommunications and Information Administration (NTIA) this week announced that its stakeholder partners for an app transparency process will soon begin testing a voluntary code of conduct for mobile app privacy. The code implores app developers to, “where practicable,” provide app users with short form notices about what data an app collects and who it will be shared with.

    The image above is one of several examples the NTIA released to show how apps following the code might display such notices.

    According to the code, notices should inform app users of data collection from the categories of biometrics; browser history; phone and text logs; contacts; financial information; health, medical, or therapy data; location data; and user files. The sharing notices should cover the categories of ad networks; carriers; consumer data resellers; data analytics providers; government entities; operating systems and platforms; other apps; and social networks.

    “NTIA is pleased that today a diverse group of stakeholders reached a seminal milestone in the efforts to enhance consumer privacy on mobile devices,” said Lawrence Strickling, the NTIA administrator. “We encourage all the companies that participated in the discussion to move forward to test the code with their consumers. I want to congratulate all of the participants, who through their commitment and dedication have demonstrated the promise and importance of the multi-stakeholder policy-making process.”

    Though Strickling’s statement shows the NTIA is proud to have provided a framework for disclosure in mobile apps, other privacy advocates are calling for stricter privacy measures. The American Civil Liberties Union (ACLU) this week called the NTIA’s code of conduct “modest,” and called on congress to pass “meaningful” consumer privacy protection legislation.

    “The American Civil Liberties Union supports this code as a modest but important step forward for consumer privacy,” said Christopher Calabrese, legislative counsel at the ACLU’s Washington Legislative Office. “It allows applications to compete on privacy and gives consumers a tool to pick the most privacy friendly applications.

    “The fact that it took a year to come to agreement on just this single measure, however, makes it clear that we need comprehensive privacy legislation in order to gain meaningful privacy protections for consumers. After all, we should be able to enjoy cool new technologies without giving up our privacy.”

  • A Google Plus Privacy Flaw Already?

    A Google Plus Privacy Flaw Already?

    That’s why it’s in beta format, right? Apparently, the sharing/contact issue that plagued Google Buzz is also apart of the Google Plus experience, at least according to reports. We can’t rely verify whether or not the issue exists or was corrected due to the invitation-only status Google Plus maintains.

    The privacy issue with Google Plus was discovered by Tim Bradshaw with FT Tech Hub, and while he says it’s not as severe as the Google Buzz issue that resulted in Google shutting the function off altogether, the resharing option stains Google’s approach of making their social platform one that respects privacy. The issue has to do with the resharing feature, which, once selected, shares with everyone in your Google Plus circle. That’s fine if it’s something you want to share, but what if it’s something the original sharer wanted to remain between the people they shared it with? Bradshaw has more:

    Say a close friend of mine posts a picture of her kids to her “friends” Circle. With the “share” option on every Google+ post, I can reshare this with absolutely anyone, from another Circle to which my friend does not belong, right through to making it completely public. The same loophole applies not just to photos but to any kind of post, as far as I can tell.

    If she’d known about this risk (and how would she?), my friend could have disabled resharing using the drop-down menu on the right-hand side of every post, but it doesn’t seem to be possible to do this before she’d already published it. Google+ also, for now, lacks any way to turn off resharing of all your posts from within its privacy settings.

    As for the last point, it’s reasonable to think that’s something Google could address quite easily, so if there’s any kind of outcry, they probably will. Furthermore, if someone wants something to remain private, or between friends only, why share it in what essentially becomes a public forum. Direct messages — or whatever Google calls Plus’ private mail service between members — work much better if you’re wanting to keep something relatively quiet.

    Sharing across networks is one of the appealing natures of social media platforms, or at least it is until someone actually sees the power of these networks and finds their content in places they’d never imagine. One could even argue the entire concept of social Internet use goes against the concept of privacy, so temper your expectations accordingly, but then again, warnings never seem to work out very well. People want reactive measures more than they preventive ones.

    According to Bradshaw’s report, Google has been informed of the loophole his post discusses and has responded, saying that’s what the invitation-only period is for, finding and correcting bugs like this one. Bradshaw finishes his report by discussing the fine line between privacy and sharing, while saying Google needs to balance the two. This is where he and I disagree for the simple fact that “user beware” and “personal responsibility” come into play.

    Is it Google’s job to teach members how to use Plus’ privacy settings or is the member, one who likely joined quite willingly, have a level of responsibility in knowing what will and won’t happen when they hit the share button?