Language Selection

English French German Italian Portuguese Spanish

Creating stronger privacy controls inside Google

Filed under
Google

We’ve spent the past several months looking at how to strengthen our internal privacy and security practices, as well as talking to external regulators globally about possible improvements to our policies. Here’s a summary of the changes we’re now making.

* First, people: we have appointed Alma Whitten as our director of privacy across both engineering and product management. Her focus will be to ensure that we build effective privacy controls into our products and internal practices. Alma is an internationally recognized expert in the computer science field of privacy and security. She has been our engineering lead on privacy for the last two years, and we will significantly increase the number of engineers and product managers working with her in this new role.

* Second, training: All our employees already receive orientation training on Google’s privacy principles and are required to sign Google’s Code of Conduct, which includes sections on privacy and the protection of user data. However, to ensure we do an even better job, we’re enhancing our core training for engineers and other important groups (such as product management and legal) with a particular focus on the responsible collection, use and handling of data. In addition, starting in December, all our employees will also be required to undertake a new information security awareness program, which will include clear guidance on both security and privacy.

* Third, compliance:




Google knows everything!

Google knows everything!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

Servers/Networks

  • Of Pies and Platforms: Platform-as-a-Service vs. Containers-as-a-Service
    I’m often asked about the difference between using a platform as a service (PaaS) vs. a containers-as-a-service (CaaS) approach to developing cloud applications. When does it makes sense to choose one or the other? One way to describe the difference and how it affects your development time and resources is to look at it like the process of baking a pie.
  • Understanding OpenStack's Success
    At the time I got into the data storage industry, I was working with and developing RAID and JBOD (Just a Bunch Of Disks) controllers for 2 Gbit Fibre Channel Storage Area Networks (SAN). This was a time before "The Cloud". Things were different—so were our users. There was comfort in buying from a single source or single vendor. In an ideal world, it should all work together, harmoniously, right? And when things go awry, that single vendor should be able to solve every problem within that entire deployment.
  • KEYNOTE Mesos + DCOS, Not Mesos versus DCOS

SF’s Elections Commission asks mayor to put $4M toward open source voting system

While the Elections Commission may be among the least followed city bodies, the seven members are playing a critical role in determining whether San Francisco will begin to use an open-source voting system. For years, open-source voting advocates have called on San Francisco officials to part ways with traditional voting machine companies. Open-source voting is widely considered the best defense to voter fraud with the added benefits of cost savings and flexibility. Much to chagrin of these advocates, The City has continued to sign contracts with nonopen-source voting companies. While no open-source voting system has been deployed elsewhere, other jurisdictions are currently working on it, such as Travis County, Texas. After The City allocated $300,000 in the current fiscal year to move San Francisco toward an open-source voting system, the effort has gotten off to a slower-than-expected start. Advocates worry if funding isn’t committed to building out such a system, the effort will face further delays. Read more [Ed: Microsoft a threat]

KaOS 2017.02

KaOS is proud to announce the availability of the February release of a new stable ISO. The policy is, once a first pacman -Syu becomes a major update, it is time for a new ISO so new users are not faced with a difficult first update. With the exceptional large amounts of updates the last four to five weeks a new ISO is needed a bit sooner than usual. As always with this rolling distribution, you will find the very latest packages for the Plasma Desktop, this includes Frameworks 5.31.0, Plasma 5.9.2, KDE Applications 16.12.2 & not yet released ports of KDE Applications. All built on Qt 5.8.0. Read more