Recommended Posts

Data Harvesting at Google Not a Rogue Act, Report Finds

SAN FRANCISCO ? Google?s harvesting of e-mails, passwords and other sensitive personal information from unsuspecting households in the United States and around the world was neither a mistake nor the work of a rogue engineer, as the company long maintained, but a program that supervisors knew about, according to new details from the full text of a regulatory report.

The report, prepared by the Federal Communications Commission after a 17-month investigation of Google?s Street View project, was released, heavily redacted, two weeks ago. Although it found that Google had not violated any laws, the agency said Google had obstructed the inquiry and fined the company $25,000.

On Saturday, Google released a version of the report with only employees? names redacted.

The full version draws a portrait of a company where an engineer can easily embark on a project to gather personal e-mails and Web searches of potentially hundreds of millions of people as part of his or her unscheduled work time, and where privacy concerns are shrugged off.

The so-called payload data was secretly collected between 2007 and 2010 as part of Street View, a project to photograph streetscapes over much of the civilized world. When the program was being designed, the report says, it included the following ?to do? item: ?Discuss privacy considerations with Product Counsel.?

?That never occurred,? the report says.

Google says the data collection was legal. But when regulators asked to see what had been collected, Google refused, the report says, saying it might break privacy and wiretapping laws if it shared the material.

A Google spokeswoman said Saturday that the company had much stricter privacy controls than it used to, in part because of the Street View controversy. She expressed the hope that with the release of the full report, ?we can now put this matter behind us.?

Ever since information about the secret data collection first began to emerge two years ago, Google has portrayed it as the mistakes of an unauthorized engineer operating on his own and stressed that the data was never used in any Google product.

The report, quoting the engineer?s original proposal, gives a somewhat different impression. The data, the engineer wrote, would ?be analyzed offline for use in other initiatives.? Google says this was never done.

The report, which was first published in its unredacted form by The Los Angeles Times, also states that the engineer, who began the project as part of his ?20 percent? time that Google gives employees to do work on their own initiative, ?specifically told two engineers working on the project, including a senior manager, about collecting payload data.?

As early as 2007, the report says, Street View engineers had ?wide access? to the plan to collect payload data. Five engineers tested the Street View code, a sixth reviewed it line by line, and a seventh also worked on it, the report says.

Privacy advocates said the full report put Google in a bad light.

?Google?s rogue engineer scenario collapses in light of the fact that others were aware of the project and did not object,? said Marc Rotenberg, executive director of the Electronic Privacy Information Center. ?This is what happens in the absence of enforcement and the absence of regulation.?

The Street View program used special cars outfitted with cameras. Google first said it was just photographing streets and did not disclose that it was collecting Internet communications called payload data, transmitted over Wi-Fi networks, until May 2010, when it was confronted by German regulators.

Eventually, it was forced to reveal that the information it had collected could include the full text of e-mails, sites visited and other data.

Even if a user was not working on a computer at the moment the Street View car slowly passed, if the device was on and the network was unencrypted, all sorts of information about what the user had been doing could be scooped up, data experts say.

?So how did this happen? Quite simply, it was a mistake,? a Google executive wrote on a company blog in 2010. ?The project leaders did not want, and had no intention of using, payload data.?

But according to the report, the engineer suggested in his proposal that it was entirely intentional: ?We are logging user traffic along with sufficient data to precisely triangulate their position at a given time, along with information about what they were doing.?

Attending to paperwork did not seem to be a high priority, however. Managers of the Street View project told F.C.C. investigators that they never read the engineer?s proposal, called a design document. A senior manager of Street View said he ?preapproved? the document before it was written.

More than a dozen countries began investigations of Street View in 2010. In the United States, the Justice Department, the Federal Trade Commission, state attorneys general and the F.C.C. looked into the matter.

The engineer at the center of the project cited the Fifth Amendment protection against self-incrimination. Because F.C.C. investigators could not interview him, they said there were still unresolved questions about the case.

Source: The New York Times

Whatever happened to 'Don't be evil.'?

I don't think that the engineers realised the privacy implications with the raw dataset at the time. To them all they saw was a lump of raw data which they would have access to when they drive by anyway, without realising that there is sensitive information that is transmitted unencrypted (To a computer science engineer, their natural instinct is that all sensitive information would be encrypted if it truly was sensitive, even if this is not the reality in this imperfect world). To them it was just the data acquisition phase for them to work out which useful data they need later. They are right to have concerns about sharing it, because when they acquired it they did not see any malicious uses but when it was later realised that it could be used maliciously, they wanted to do the right thing which is to destroy it and not give it to interested parties who may have an interest in using it for malicious purposes. From the perspective of a computer engineer who can see how this could have easily happened when left to a bunch of engineers (I imagine that the idea went along the lines of "lets just run kismet and see what we can get for our maps" not "lets run kismet and see what private information we can steal so we can run some identity theft on the side"), I fail to see the evil.

I don't think that the engineers realised the privacy implications with the raw dataset at the time. To them all they saw was a lump of raw data which they would have access to when they drive by anyway, without realising that there is sensitive information that is transmitted unencrypted (To a computer science engineer, their natural instinct is that all sensitive information would be encrypted if it truly was sensitive, even if this is not the reality in this imperfect world). To them it was just the data acquisition phase for them to work out which useful data they need later. They are right to have concerns about sharing it, because when they acquired it they did not see any malicious uses but when it was later realised that it could be used maliciously, they wanted to do the right thing which is to destroy it and not give it to interested parties who may have an interest in using it for malicious purposes. From the perspective of a computer engineer who can see how this could have easily happened when left to a bunch of engineers (I imagine that the idea went along the lines of "lets just run kismet and see what we can get for our maps" not "lets run kismet and see what private information we can steal so we can run some identity theft on the side"), I fail to see the evil.

Just give up, no matter how rational and competent reason you have, even the correct one will matter, this is just more fodder for the set of morons that hate Google and everything they do, and we will of course be called fanboys for not hating

This topic is now closed to further replies.
  • Posts

    • NTLite 2026.06.11200 by Razvan Serea NTLite is a Windows configuration tool that allows you to modify your existing Windows install or an image yet to be deployed, remove Windows components, configure and integrate, speed up the Windows deployment process. Reduce Windows footprint on your RAM and storage drive memory. Remove components of your choice, guarded by compatibility safety mechanisms, which speed up finding that sweet spot. Windows Unattended feature support, providing many commonly used options on a single page for easy setup. Easily integrate a single or multiple drivers, update or language packages. Package integration features smart sorting, enabling you to seamlessly add packages for integration and the tool will apply them in the appropriate order, keeping hotfix compatibility in check. One of the important new features of NTLite (compared to its predecessors) is the ability to modify an already installed the operating system, by removing unnecessary components. Supports Windows 11, 10, 8.1 and 7, x86 and x64, live and image. Server editions of the same versions, excluding support for component removals and feature configuration. ARM64 image support in the alpha stage. Does not support Checked/Debug, Embedded, IoT editions, nor Vista or XP. NTLite 2026.06.11200 changelog: New Secure Boot Migration support: Verification, certificate staging, and boot-manager/sector update across the Image, Updates, Apply, and Create-ISO pages (2023 CA migration, optional 2011 revocation, Anti-rollback, Boot sector choice etc) Secure Boot Host Readiness: Live host Secure Boot migration monitor and Servicing-task control Option under Image page - C:\Windows row, or load the host as the target - Updates - Secure Boot Image: 'Sort mounted images first' option for the image list in Menu-Settings UI: Hover description card for Components and Unattended pages, selectable text and quick access to Compatibility options Command line: Relay commands into the already-running instance Enables controlling already running NTLite via ntlite.exe Use /NewInstance to launch an additional instance using CLI operations (premium) UI: 'New instance' option via main menu instead of a secondary ntlite.exe prompt Apply: Hide individual Apply-page notes with a per-note dismiss (X), critical excluded Settings: 'Unsigned RDP file launch warnings' tweak (RDP client), bypassing the April 2026 security-update prompt on RDP connections Upgrade Image: Live OS and deployed image editing now unlocked on free/test licenses, same licensing as images Image: 'Recompress' option in manual dialog Remove Editions to shrink the WIM in one session Image: SWM part size set inline on the Apply page and image dialogs, split-size popup retired Image: Relative 'Last change' dates; editions grouped by build time to reduce noise Image: 'Forget - Missing' on the Edit-cache menu to mass drop entries whose folder is gone Components: Root groups reorganized - user-facing groups first, system/critical last Components: Show filter options to view components by Template or App-type, since Apps are now merged into groups Presets: Delete confirmation now lists the multi-selected preset names UI: Design update propagated to the rest of the tool UI: Filter and search match words in any order and partially, better results filtering Components Unattended: Input-locale language derives from the user locale, with an independent keyboard picker, enables combinations previously unavailable Unattended: Input-locale now allows for a user value override Unattended: Localization OOBE WinPE now can be copied with the new WinPE Copy OOBE localization toggle, enter locale settings once for both stages Updates: Downloader greys and locks updates the image already carries (hotfix and MSIX) Updates: Resume interrupted update downloads Command line: Many upgrades, see /?, now prints help to the console or redirected output UI-Translation: Finnish language added, also thanks for Chinese Traditional (Matt), French (tistou77), Italian (clarensio), Russian (RDS), Swedish (1FF), Vietnamese (Vu Anh Vu) Fix Components: Containers removal breaking Apps deployment Components: Microsoft Account had leftovers when Easy Migrate is kept Image: Export to an existing WIM improvements, Append renamed to Merge Image: Improved 26H1 live removal support Image: No more 'X:\ not accessible' popup for certain drives during image scan Presets: Manual image refresh picks up presets added/removed outside the app Tweaks: Disabled visual-effect animations no longer return after first logon on a new profile Tweaks: Live Visual Effects toggles (animations, drag full windows, font smoothing) now apply correctly Download: NTLite 2026.06.11200 | 20.5 MB (Free, paid upgrade available) Link: NTLite Home Page | NTLite Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Ah. La Fontana De Incontinentia ! Bella ! Bella !
    • Hi everyone, I'm planning a small network upgrade and was wondering how others prepare their networks for future needs. Do you usually invest in higher-speed switches and better cabling from the start, or do you upgrade only when necessary? I'd be interested in hearing what has worked well for you and any lessons you've learned over time. Thanks!
    • Greetings and welcome!!
  • Recent Achievements

    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
    • First Post
      carols23 earned a badge
      First Post
    • One Month Later
      Tom Willson earned a badge
      One Month Later
    • Apprentice
      Asgardi went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      257
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      93
    5. 5
      macoman
      67
  • Tell a friend

    Love Neowin? Tell a friend!