Law in the Internet Society

View   r20  >  r19  >  r18  >  r17  >  r16  >  r15  ...
SethLindnerFirstPaper 20 - 07 Sep 2011 - Main.IanSullivan
Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="FirstPaper"
>
>
META TOPICPARENT name="FirstPaper2009"
 

Privacy Loopholes in Google Voice, and Why Users Won't Even Notice

Line: 108 to 108
 -- HeatherStevenson - 25 Nov 2009
Changed:
<
<
My paper was on a similar topic. You went more in-depth into Google's Privacy Policy than I did, however.
>
>
My paper was on a similar topic. You went more in-depth into Google's Privacy Policy than I did, however.
 

It strikes me that a lot depends on how much teeth the Privacy Policy has. If Google (or another company doing similar privacy-sensitive things on the Internet) takes privacy seriously then they'll have people and measures to stop them from being too evil. It's their motto, after all! Strict internal controls would minimize the practical impact of data aggregation, even if there's still a philosophical problem with the data being there in the first place. But we all know how slimy and amoral marketing folks are. They want to sink their talons into any possible way to deliver ads. And if they have enough political pressure within Google then the Privacy Policy doesn't really end up meaning that much because the privacy advocates will get steamrolled.


SethLindnerFirstPaper 19 - 01 Feb 2010 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Line: 66 to 66
  on your side. Explaining in any individual instance that a particular privacy policy does what they all do is a pure waste of words.
Added:
>
>
  • I suppose the value of parsing privacy policies depends on one's opinion of one's audience. Given the number of my classmates that use Google products (e.g., GMail) on a regular basis, I didn't think that it would be completely obvious to them that Google's privacy policies were just as bad as the others. I take your point, however, and I'll make this portion much more concise in my revision.
 Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The first problem is that Google presumes to know what kind of information personally identifies its users. It identifies name, email address, and billing information as examples. Even if we leave sophisticated data mining techniques aside, doesn't it seem possible that something like a simple list of the ten people that you call most often might pretty easily identify you. Next, the Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." So, even if the information that Google didn't classify as "personal" wasn't enough for third parties to identify you, those same parties can get Google to process the personal information to fill in the missing gaps.

SethLindnerFirstPaper 18 - 24 Jan 2010 - Main.EbenMoglen
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Deleted:
<
<
Ready for review. All comments are welcome.
 

Privacy Loopholes in Google Voice, and Why Users Won't Even Notice

Line: 12 to 10
 

Recent Google Acquisitions

Two recent acquisitions indicate that Google may be getting serious about entering the VoIP telecommunications market. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
Added:
>
>
  • Better technical understanding and less superficial Googling would help here. Grand Central is just a server hosting Asterisk, the free software telephone switch that's been mentioned here before. Grand Central allows you to be spied on for doing with all your phone numbers what you could do for yourself very easily and cheaply. Google buys it not because it knows how to do something Google needs to know how to do, but because it's cheaper to buy future competitors while they're small.
 While Google Voice allowed users to consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system.
Added:
>
>
  • Here too, you are hampered by not having understood the technology. Gizmo makes a SIP softphone, and also runs a hosted service that gives that softphone (which could be running on your laptop, on your Nokia smartphone, or in many other devices) a DID, that is, a telephone number, at which it can receive calls (Skype will also sell you a telephone number by the month, if you want one). The Gizmo softphone is less good than free software smartphones available that run in the sample places. You might have compared it to Twinkle or Linphone, for example. Once again, Google isn't learning anything or acquiring any technology that it can't have for free: it's just eliminating a possible competitor.
 Currently Google claims to have more than 1.4 million users of Google Voice.

"A Higher Sense of Privacy" -- User Reactions to Google Voice

Line: 25 to 46
 This comment makes me nervous because I think this guy is almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. But remember, Google already knows how to play this game. It knows that we do not want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to give users exactly they are looking for -- a "higher sense of privacy."
Added:
>
>
  • Google has no intention whatever of inserting advertising in phone calls. If you would spend a minute or two in thinking, rather than rushing to respond to some comment made by an anonymous fool on a website, you would see what the actual purpose of Google Voice is, which you don't mention anywhere and which was untouched by the not very well-informed websites you turned up by Googling.
 

The Loopholes in the Google/Google Voice Privacy Policies

A careful reading of Google's privacy policy reveals what privacy means to Google. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.
Added:
>
>
  • There's no point parsing privacy policies, for the reason I gave in class: privacy policies all say "we can do whatever we want" in words that sound as pro-you as possible. This gives them the right to do whatever they want without risk of pressure from the FTC to keep their promises (because they promised you they would do whatever they wanted) while sounding like they're on your side. Explaining in any individual instance that a particular privacy policy does what they all do is a pure waste of words.
 Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The first problem is that Google presumes to know what kind of information personally identifies its users. It identifies name, email address, and billing information as examples. Even if we leave sophisticated data mining techniques aside, doesn't it seem possible that something like a simple list of the ten people that you call most often might pretty easily identify you. Next, the Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." So, even if the information that Google didn't classify as "personal" wasn't enough for third parties to identify you, those same parties can get Google to process the personal information to fill in the missing gaps.

Google Voice has its own privacy policy and even more problems. Let's take a look at what happens when you delete a record from your Google Voice account. The first thing that happens is that the message immediately disappears from your view.

Line: 40 to 79
 It is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice is evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). Even if Google continues its current practice of not showing advertisements on the site, users need to think seriously about how their information is actually being used. It is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy curtailed, those things aren't indeed happening on a massive scale.
Added:
>
>
  • It's safe to assume that Google can only make money from one thing: monetizing search. You have not grasped why Google is doing what it's doing. You should try.
 

SethLindnerFirstPaper 17 - 24 Dec 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.

SethLindnerFirstPaper 16 - 07 Dec 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.

SethLindnerFirstPaper 15 - 03 Dec 2009 - Main.BrianS
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 78 to 78
 I think there is also a tool that allows voice mail to redirect to Google Voice, and Google Voice transcribes the conversation and sends it to you by email. I wonder if this means that Google Voice actually has a recording of every conversation that made over the service (I wonder too if Skype does have that recording. In China, I felt that whenever I spoke about the government over in Skype, I noticed that the connection would go choppy.)

-- AllanOng - 30 Nov 2009

Added:
>
>

Allan is right (and as you note, Seth, in your essay), there at least was previously such a transcription option: http://www.pcmag.com/article2/0,2817,2343429,00.asp

-- BrianS - 03 Dec 2009

 
 
<--/commentPlugin-->
\ No newline at end of file

SethLindnerFirstPaper 14 - 01 Dec 2009 - Main.BradleyMullins
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.

SethLindnerFirstPaper 13 - 30 Nov 2009 - Main.AllanOng
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 73 to 73
 -- GavinSnyder - 29 Nov 2009
Added:
>
>

I think there is also a tool that allows voice mail to redirect to Google Voice, and Google Voice transcribes the conversation and sends it to you by email. I wonder if this means that Google Voice actually has a recording of every conversation that made over the service (I wonder too if Skype does have that recording. In China, I felt that whenever I spoke about the government over in Skype, I noticed that the connection would go choppy.)

-- AllanOng - 30 Nov 2009

 
 
<--/commentPlugin-->

SethLindnerFirstPaper 12 - 29 Nov 2009 - Main.GavinSnyder
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 62 to 62
 I don't really have any other comments- this paper looks good to me!

-- HeatherStevenson - 25 Nov 2009

Added:
>
>

My paper was on a similar topic. You went more in-depth into Google's Privacy Policy than I did, however.

It strikes me that a lot depends on how much teeth the Privacy Policy has. If Google (or another company doing similar privacy-sensitive things on the Internet) takes privacy seriously then they'll have people and measures to stop them from being too evil. It's their motto, after all! Strict internal controls would minimize the practical impact of data aggregation, even if there's still a philosophical problem with the data being there in the first place. But we all know how slimy and amoral marketing folks are. They want to sink their talons into any possible way to deliver ads. And if they have enough political pressure within Google then the Privacy Policy doesn't really end up meaning that much because the privacy advocates will get steamrolled.

Maybe the key is to use outside pressure and publicity to keep privacy in the spotlight. It seemed to work on Facebook. On the other hand, people don't seem to get riled up about minor privacy incursions, only really egregious ones. Which means that the marketing people will be probably be able to chip away slowly and silently.

-- GavinSnyder - 29 Nov 2009

 
 
<--/commentPlugin-->

SethLindnerFirstPaper 11 - 28 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 23 to 23
 "I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."
Changed:
<
<
This comment makes me nervous because I think this guy is almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. But remember, Google already knows how to play this game. It knows that we do want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to give users exactly they are looking for -- a "higher sense of privacy."
>
>
This comment makes me nervous because I think this guy is almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. But remember, Google already knows how to play this game. It knows that we do not want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to give users exactly they are looking for -- a "higher sense of privacy."
 

The Loopholes in the Google/Google Voice Privacy Policies

A careful reading of Google's privacy policy reveals what privacy means to Google. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.

SethLindnerFirstPaper 10 - 28 Nov 2009 - Main.BrianS
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 51 to 51
 I have no other substantive comments. It looks good, reads well, and is an important and engaging topic. Nice work.
Added:
>
>
11-28-09 EDIT: Seth, I ran into this story on Google Voice/cell phones today and thought it might be useful for you.
 -- BrianS - 24 Nov 2009

SethLindnerFirstPaper 9 - 25 Nov 2009 - Main.HeatherStevenson
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 52 to 52
 I have no other substantive comments. It looks good, reads well, and is an important and engaging topic. Nice work.

-- BrianS - 24 Nov 2009

Added:
>
>

Seth, This is a really interesting paper and topic. You imply the relationship is important, but to what extent do you think it matters that Google voice is run by Google and not some random small company? In other words, does it matter that with google voice, Google has access not only to a persons phone conversations, but also potentially to his email, calendar, googlereader, googlegroups, etc. This is both a practical and theoretical question, as I couldn't tell from the privacy policies how information from the various google products is used. Would it be less scary if some other company came out with a similar product with a similar privacy policy? It seems it would, but I wonder if we can know exactly why.

I don't really have any other comments- this paper looks good to me!

-- HeatherStevenson - 25 Nov 2009

 
 
<--/commentPlugin-->

SethLindnerFirstPaper 8 - 24 Nov 2009 - Main.BrianS
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Ready for review. All comments are welcome.
Line: 41 to 41
 It is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice is evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). Even if Google continues its current practice of not showing advertisements on the site, users need to think seriously about how their information is actually being used. It is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy curtailed, those things aren't indeed happening on a massive scale.


Added:
>
>

Seth,

I follow Google closely, so this was a very interesting read for me. Two quick easy comments: there seems to be a "not" missing in "It knows that we do [___] want to feel like someone is standing over our shoulder." in the last paragraph of part 2, "A Higher Sense of Privacy." Also, you might consider hyperlinking to our data mining readings in the second paragraph of part 3, "The Loopholes," and adding some citation or link for the statement that Google has backups and that they never get deleted. Maybe just linking to the policy where you give permission to Google would cover the latter.

Substantively, your point about the top 10 most called bit as personally identifying is a good one. I also agree that the prospect of Google monetizing Google Voice via targeting ads based on phone calls is a formidable specter. I wonder if it really loses any punch, though, even if Google doesn't actually target ads in that way? I'm not sure it does (lose any punch, that is). And I think that it is important that it doesn't because Google seems to have a lot of projects that I don't believe it currently uses to tailor ad delivery (perhaps it does and I'm simply not remembering/aware), so there is some chance that it won't monetize Voice using ads based on call contents. Another idea, and one that perhaps seems more likely than Google actually using some sort of filter that grabs keywords from your phone calls and delivers ads relevant to them, is maybe Google would just look-up (via automated software) the numbers you call. Oh, you call Pizza Joe's on Fridays? Guess we'll target ads to you that afternoon of other pizza places. You call a Laundromat 5000 on every other Sunday? Well look at that, free coupons hit your email box on Friday when you're about to drop it off. And so on. That seems like a more likely form of tailored-ad than the Google-as-fulltime-listener one. That might be something good to note more if you can find space.

I have no other substantive comments. It looks good, reads well, and is an important and engaging topic. Nice work.

-- BrianS - 24 Nov 2009

 
 
<--/commentPlugin-->

SethLindnerFirstPaper 7 - 23 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Added:
>
>
Ready for review. All comments are welcome.
 
Changed:
<
<

IN PROGRESS...

>
>
 

Privacy Loopholes in Google Voice, and Why Users Won't Even Notice

-- By SethLindner - 06 Nov 2009

Recent Google Acquisitions

Changed:
<
<
Two acquisitions over the past two years indicate that Google may be getting serious about significantly entering the VoIP telecommunications market. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
>
>
Two recent acquisitions indicate that Google may be getting serious about entering the VoIP telecommunications market. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
 
Changed:
<
<
While Google Voice allowed users to essentially consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system that simultaneously threatens pay services like Skype and cellular telephone services like Verizon and AT&T.
>
>
While Google Voice allowed users to consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system.
 
Changed:
<
<
Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
>
>
Currently Google claims to have more than 1.4 million users of Google Voice.
 

"A Higher Sense of Privacy" -- User Reactions to Google Voice

Changed:
<
<
I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." The response seems mostly positive. One article discussed some of the advantages and disadvantages of Google Voice, noting that although the Google Voice site was currently ad-free, it could change this in the future. Then came a reader comment that really worried me:
>
>
I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." One article discussed some of the advantages and disadvantages of Google Voice, noting that although the Google Voice site was currently ad-free, it could change this in the future. Then came a reader comment that really worried me:
 
"I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."
Line: 23 to 25
 This comment makes me nervous because I think this guy is almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. But remember, Google already knows how to play this game. It knows that we do want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to give users exactly they are looking for -- a "higher sense of privacy."
Added:
>
>

The Loopholes in the Google/Google Voice Privacy Policies

 A careful reading of Google's privacy policy reveals what privacy means to Google. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.

Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The first problem is that Google presumes to know what kind of information personally identifies its users. It identifies name, email address, and billing information as examples. Even if we leave sophisticated data mining techniques aside, doesn't it seem possible that something like a simple list of the ten people that you call most often might pretty easily identify you. Next, the Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." So, even if the information that Google didn't classify as "personal" wasn't enough for third parties to identify you, those same parties can get Google to process the personal information to fill in the missing gaps.

Changed:
<
<
Google Voice has its own privacy policy and even more privacy problems. Let's take a look at what happens when you delete a record from your Google Voice account. The first thing that happens is that the message immediately disappears from your view.
>
>
Google Voice has its own privacy policy and even more problems. Let's take a look at what happens when you delete a record from your Google Voice account. The first thing that happens is that the message immediately disappears from your view.
 
"Whew! Good thing I got rid of THAT message. I could be in big trouble if it got around."
Changed:
<
<
Then, sometime in the next 90 days, Google removes the information from its "active servers." Unfortunately, Google also has backups of everything. And those don't ever get deleted. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it. The danger, of course, is that most users will simply forget that Google still has it, once it is removed from their view. This shows again why Google Voice is uniquely dangerous. People will use it without even knowing how much information they are really sharing with Google. And even if they realize that they've shared something they wish they hadn't, there isn't any way to get it back.
>
>
Then, "up to 90 days" later, Google removes the information from its "active servers." Unfortunately, Google also has backups of everything. And those don't ever get deleted. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it. The danger, of course, is that most users will simply forget that Google still has it, once it is removed from their view. This shows again why Google Voice is uniquely dangerous. People will use it without even knowing how much information they are really sharing with Google. And even if they realize that they've shared something they wish they hadn't, there isn't any way to get it back.
 It is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice is evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). Even if Google continues its current practice of not showing advertisements on the site, users need to think seriously about how their information is actually being used. It is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy curtailed, those things aren't indeed happening on a massive scale.
Added:
>
>

 
<--/commentPlugin-->

SethLindnerFirstPaper 6 - 23 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"

IN PROGRESS...

Line: 8 to 8
 

Recent Google Acquisitions

Changed:
<
<
Two acquisitions over the past two years indicate that Google may be getting serious about significantly entering the VoIP telecommunications industry. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
>
>
Two acquisitions over the past two years indicate that Google may be getting serious about significantly entering the VoIP telecommunications market. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
 
Changed:
<
<
While Google Voice allowed users to essentially consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP? puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system that simultaneously threatens pay services like Skype and cellular telephone services like Verizon and AT&T.
>
>
While Google Voice allowed users to essentially consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system that simultaneously threatens pay services like Skype and cellular telephone services like Verizon and AT&T.
 Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.

"A Higher Sense of Privacy" -- User Reactions to Google Voice

Changed:
<
<
I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." One article discussed some of the advantages and disadvantages of Google Voice, noting that the possibility of advertisements was a disadvantage, although Google hadn't yet included any ads on the Google Voice site (as it has for Gmail). Then came a reader comment that really scared me:
>
>
I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." The response seems mostly positive. One article discussed some of the advantages and disadvantages of Google Voice, noting that although the Google Voice site was currently ad-free, it could change this in the future. Then came a reader comment that really worried me:
 
"I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."
Changed:
<
<
I'm worried by this statement because I think this user almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls or voice messages. And I think most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. The problem is that Google already knows how to play this game. It knows that we do want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to encourage us to believe that is offering a service that is both free and private.
>
>
This comment makes me nervous because I think this guy is almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. But remember, Google already knows how to play this game. It knows that we do want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to give users exactly they are looking for -- a "higher sense of privacy."
 
Changed:
<
<
A careful reading of Google's privacy policy reveals what are likely the real dangers. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.
>
>
A careful reading of Google's privacy policy reveals what privacy means to Google. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.
 
Changed:
<
<
Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." I see at least two problems here. First of all, even though Google says that it won't directly "share" personal information with third parties without consent, Google still has a whole lot of personal information that it can use for its own purposes. Second, it seems that third parties (advertisers, banks, potential employers?) could learn quite a lot about you just by "processing" your personal information.
>
>
Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The first problem is that Google presumes to know what kind of information personally identifies its users. It identifies name, email address, and billing information as examples. Even if we leave sophisticated data mining techniques aside, doesn't it seem possible that something like a simple list of the ten people that you call most often might pretty easily identify you. Next, the Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." So, even if the information that Google didn't classify as "personal" wasn't enough for third parties to identify you, those same parties can get Google to process the personal information to fill in the missing gaps.
 
Changed:
<
<
Google Voice has its own privacy policy and even more clever deception. For instance, if you delete something from your Google voice account, the deletion will take immediate effect in your account view.
>
>
Google Voice has its own privacy policy and even more privacy problems. Let's take a look at what happens when you delete a record from your Google Voice account. The first thing that happens is that the message immediately disappears from your view.
 
"Whew! Good thing I got rid of THAT message. I could be in big trouble if it got around."
Changed:
<
<
Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. The danger, of course, is that most users will simply forget that Google still has it, once it is removed from their view. This shows again why Google Voice is uniquely dangerous. People will use it without even knowing how much information they are really sharing with Google. And even if they realize that they've shared something they wish they hadn't, there isn't any way to get it back.
>
>
Then, sometime in the next 90 days, Google removes the information from its "active servers." Unfortunately, Google also has backups of everything. And those don't ever get deleted. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it. The danger, of course, is that most users will simply forget that Google still has it, once it is removed from their view. This shows again why Google Voice is uniquely dangerous. People will use it without even knowing how much information they are really sharing with Google. And even if they realize that they've shared something they wish they hadn't, there isn't any way to get it back.
 
Changed:
<
<
I think it is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice a reality is strong evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). If Google continues its current practice of not showing advertisements on the site, I think users need to think seriously about how their information is actually being used. There is no question that Google is making money off of its users, so it is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy being curtailed, those things aren't indeed happening on a massive scale.
>
>
It is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice is evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). Even if Google continues its current practice of not showing advertisements on the site, users need to think seriously about how their information is actually being used. It is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy curtailed, those things aren't indeed happening on a massive scale.

SethLindnerFirstPaper 5 - 20 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"

IN PROGRESS...

Changed:
<
<

The Many Privacy Problems with Google's Entry into Broadband Telecommunications, and Why Users Won't Even Notice

>
>

Privacy Loopholes in Google Voice, and Why Users Won't Even Notice

 -- By SethLindner - 06 Nov 2009

Recent Google Acquisitions

Changed:
<
<
Two acquisitions over the past two years indicate Google's interest in entering into the VoIP telecommunications industry. Google's first move was its acquisition in 2007 of a company called GrandCentral, a web-based call forwarding system that provided users with a single phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences (like who was calling and when). In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages. Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
>
>
Two acquisitions over the past two years indicate that Google may be getting serious about significantly entering the VoIP telecommunications industry. In 2007 Google bought a company called GrandCentral, which ran a web-based call forwarding system that provided users with a single "central" phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences. In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages.
 
Changed:
<
<
Although the Google Voice service probably seemed useful to those with many phone numbers, it wasn't exactly what people think of as a VoIP service because all phone calls still needed to be routed to a permanent phone number. So, even though Google Voice was free to use, it really wasn't a complete replacement for existing telephone services. This is where Google's recent acquisition of a company called Gizmo5 comes in.
>
>
While Google Voice allowed users to essentially consolidate all of their conventional phone numbers into one Google Voice number, it still required users to have a separate land line or cellular telephone to make or receive calls. It appears that this is about to change. Google recently announced that it had purchased a company called Gizmo5 for $30 million. Gizmo5 offers the missing piece to the VoIP? puzzle for Google by providing an actual phone number and software to make and receive calls. Many people speculate that Google will integrate the Gizmo5 features into Google Voice, creating a no-cost centralized telephone system that simultaneously threatens pay services like Skype and cellular telephone services like Verizon and AT&T.
 
Changed:
<
<

Don't Look Too Closely -- Google's Privacy Policy

I imagine that the eyebrows of even those with the utmost trust for Google were raised upon learning that Google Voice provides written transcriptions of voice mail messages and recorded phone calls.
>
>
Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
 
Changed:
<
<
"Wait a minute. Google knows exactly what someone told me in my voice mail?"

Yes, if you use Google Voice, Google does know the content of your voice mail. You're just surprised because their proving it to you by sending you a transcript.

>
>

"A Higher Sense of Privacy" -- User Reactions to Google Voice

I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." One article discussed some of the advantages and disadvantages of Google Voice, noting that the possibility of advertisements was a disadvantage, although Google hadn't yet included any ads on the Google Voice site (as it has for Gmail). Then came a reader comment that really scared me:
 
Changed:
<
<
"Okay, so even if they DO know what's in my voice mail, I'm sure Google won't share that information about me to anyone, right? Let me take a quick look at their privacy policy to see what it says about all this."
>
>
"I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."
 
Changed:
<
<
Google's privacy policy is what I would call attractively deceptive. The attractive part is what Google wants you to see. The first line reminds us that Google believes that privacy is important. Shortly thereafter, we see a link to the U.S. Department of Commerce's Safe Harbor Program. That sure sounds safe. Reading further, we see that our "personal information" will only be processed for the purposes described in the policy and that our "sensitive personal information" will only be shared with outside individuals/companies with our consent. Further, the policy states that something called "aggregated non-personal information" may be shared with third parties, but that such information does not "identify [users] individually". Up until now, this seems pretty attractive.
>
>
I'm worried by this statement because I think this user almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls or voice messages. And I think most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. The problem is that Google already knows how to play this game. It knows that we do want to feel like someone is standing over our shoulder. It knows that if we pick up the phone and hear nothing but measured breathing on the other end of the line, we're going to hang up pretty quickly. Google's response, then, will be to encourage us to believe that is offering a service that is both free and private.

A careful reading of Google's privacy policy reveals what are likely the real dangers. I call this policy attractively deceptive, because once we look beyond the first line reminding us that Google believes that privacy is important, and the statement of compliance with the U.S. Department of Commerce's Safe Harbor Program (that sounds safe), we see some startling possibilities.

 
Changed:
<
<
Here is the deceptive part. If we look at how Google defines "personal information", "sensitive personal information", and "aggregated non-personal information" and what uses Google explicitly reserves, we see some startling possibilities. Let's begin with "personal information", which is defined by Google as information that "personally identifies you, such as your name, email address or billing information." This type of information can be "process[ed] . . . on behalf of and according to the instructions of a third party" although it seems as though "personal information" cannot be "shared" with third parties without user consent. This begs the questions of We as users have no control over who this is or how the data is processed. And even if Google doesn't directly give away our names or addresses, it does allow targeted advertising.
>
>
Let's first look at how Google handles "personal information," which Google defines as information that "personally identifies you." The Policy plainly allows Google to "process [personal information] on behalf of and according to the instructions of a third party." I see at least two problems here. First of all, even though Google says that it won't directly "share" personal information with third parties without consent, Google still has a whole lot of personal information that it can use for its own purposes. Second, it seems that third parties (advertisers, banks, potential employers?) could learn quite a lot about you just by "processing" your personal information.
 Google Voice has its own privacy policy and even more clever deception. For instance, if you delete something from your Google voice account, the deletion will take immediate effect in your account view.
Line: 35 to 33
 "Whew! Good thing I got rid of THAT message. I could be in big trouble if it got around."
Changed:
<
<
Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. I'm sure Google would argue that these backups are necessary for system stability, but the danger is that most users will simply forget that Google still has it, once it is removed from their view.
>
>
Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. The danger, of course, is that most users will simply forget that Google still has it, once it is removed from their view. This shows again why Google Voice is uniquely dangerous. People will use it without even knowing how much information they are really sharing with Google. And even if they realize that they've shared something they wish they hadn't, there isn't any way to get it back.
 
Deleted:
<
<

"A Higher Sense of Privacy" -- User Reactions to Google Voice

I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." One article discussed some of the advantages and disadvantages of Google Voice, noting that the possibility of advertisements was a disadvantage, although Google hadn't yet included any ads on the Google Voice site (as it has for Gmail). Then came a reader comment that really scared me:

"I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."
 
Changed:
<
<
I'm worried by this statement because I think this user almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And I think most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. The problem is that just because Google doesn't show ads on the Google Voice site doesn't mean that they aren't using your phone transactions and the content of your transcribed calls as inputs to their vast data mining operations. It only means that users are less likely to realize that this is what is happening. Unless Google is simply providing the Google Voice service out of the goodness of its heart, we can safely assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice a reality is strong evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth).
>
>
I think it is safe to assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice a reality is strong evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth). If Google continues its current practice of not showing advertisements on the site, I think users need to think seriously about how their information is actually being used. There is no question that Google is making money off of its users, so it is a foolish (but I'm afraid all too common) mistake to believe that just because we can't tell exactly how our privacy is being violated and our autonomy being curtailed, those things aren't indeed happening on a massive scale.

SethLindnerFirstPaper 4 - 19 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Changed:
<
<

In Progress...

>
>

IN PROGRESS...

 

The Many Privacy Problems with Google's Entry into Broadband Telecommunications, and Why Users Won't Even Notice

-- By SethLindner - 06 Nov 2009

Line: 25 to 25
 "Okay, so even if they DO know what's in my voice mail, I'm sure Google won't share that information about me to anyone, right? Let me take a quick look at their privacy policy to see what it says about all this."
Changed:
<
<
Google's privacy policy is what I would call attractively deceptive. The attractive part is what Google wants you to see. The first line reminds us that Google believes that privacy is important. Shortly thereafter, we see a link to the U.S. Department of Commerce's Safe Harbor Program. That sure sounds safe. Reading further, we see that our personal information will only be processed for the purposes described in the policy and that our sensitive personal information will only be shared with outside individuals/companies with our consent. Up until now, this seems pretty attractive.
>
>
Google's privacy policy is what I would call attractively deceptive. The attractive part is what Google wants you to see. The first line reminds us that Google believes that privacy is important. Shortly thereafter, we see a link to the U.S. Department of Commerce's Safe Harbor Program. That sure sounds safe. Reading further, we see that our "personal information" will only be processed for the purposes described in the policy and that our "sensitive personal information" will only be shared with outside individuals/companies with our consent. Further, the policy states that something called "aggregated non-personal information" may be shared with third parties, but that such information does not "identify [users] individually". Up until now, this seems pretty attractive.
 
Changed:
<
<
Here is the deceptive part. If we look at how the terms are defined and at what uses Google explicitly reserves, we see that accepting this policy opens the door to some startling possibilities. For example, Google has permission to process personal information, which includes names, email addresses, and billing information, on behalf of and according to the instructions of a third party, such as our advertising partners. Does this mean that Google will only ever process our personal information according to the instructions of an advertising partner? No. It can process this information to suit the needs of any third party. We as users have no control over who this is or how the data is processed. And even if Google doesn't directly give away our names or addresses, it does allow targeted advertising.
>
>
Here is the deceptive part. If we look at how Google defines "personal information", "sensitive personal information", and "aggregated non-personal information" and what uses Google explicitly reserves, we see some startling possibilities. Let's begin with "personal information", which is defined by Google as information that "personally identifies you, such as your name, email address or billing information." This type of information can be "process[ed] . . . on behalf of and according to the instructions of a third party" although it seems as though "personal information" cannot be "shared" with third parties without user consent. This begs the questions of We as users have no control over who this is or how the data is processed. And even if Google doesn't directly give away our names or addresses, it does allow targeted advertising.
 
Changed:
<
<
Google Voice has its own privacy policy that supplements Google's main policy. Here we find even more clever deception. For instance, if you delete something from your Google voice account, the deletion will take immediate effect in your account view.
>
>
Google Voice has its own privacy policy and even more clever deception. For instance, if you delete something from your Google voice account, the deletion will take immediate effect in your account view.
 
"Whew! Good thing I got rid of THAT message. I could be in big trouble if it got around."
Changed:
<
<
Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. I suppose this is so you'll forget that Google still has it.
>
>
Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. I'm sure Google would argue that these backups are necessary for system stability, but the danger is that most users will simply forget that Google still has it, once it is removed from their view.
 

"A Higher Sense of Privacy" -- User Reactions to Google Voice


SethLindnerFirstPaper 3 - 19 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"

In Progress...

Line: 8 to 8
 

Recent Google Acquisitions

Changed:
<
<
Two acquisitions over the past two years indicate Google's apparent interest in entering into the VoIP telecommunications industry. Google's first move was its acquisition in 2007 of a company called GrandCentral, a web-based call forwarding system that provided users with a single phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences (like who was calling and when). After continuing operations as GrandCentral for about two years, in April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages. Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
>
>
Two acquisitions over the past two years indicate Google's interest in entering into the VoIP telecommunications industry. Google's first move was its acquisition in 2007 of a company called GrandCentral, a web-based call forwarding system that provided users with a single phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences (like who was calling and when). In April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages. Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
 
Changed:
<
<
Although the Google Voice service probably seemed useful to those with many phone numbers, it wasn't exactly what people think of as a VoIP service because all phone calls still needed to be routed to a permanent phone number. So, even though Google Voice was free to use, it really wasn't anything close to a replacement for existing telephone services. This is where Google's recent acquisition of a company called Gizmo5 comes in.
>
>
Although the Google Voice service probably seemed useful to those with many phone numbers, it wasn't exactly what people think of as a VoIP service because all phone calls still needed to be routed to a permanent phone number. So, even though Google Voice was free to use, it really wasn't a complete replacement for existing telephone services. This is where Google's recent acquisition of a company called Gizmo5 comes in.
 

Don't Look Too Closely -- Google's Privacy Policy

Changed:
<
<
One of the significant features of Google Voice is its ability to provide written transcriptions of voice mail messages and recorded phone calls. I imagine that the eyebrows of even those with the utmost trust for the Google conglomerate were raised upon learning of this feature.
>
>
I imagine that the eyebrows of even those with the utmost trust for Google were raised upon learning that Google Voice provides written transcriptions of voice mail messages and recorded phone calls.
 
Changed:
<
<
"Wait a minute. Google knows exactly what someone told me in my voice mail?"
>
>
"Wait a minute. Google knows exactly what someone told me in my voice mail?"
 
Changed:
<
<
Yes, Google does know. Your just surprised because their proving it to you by sending you a transcript.
>
>
Yes, if you use Google Voice, Google does know the content of your voice mail. You're just surprised because their proving it to you by sending you a transcript.
 
Changed:
<
<
"Okay, so even if they DO know what's in my voice mail, I'm sure Google won't share that information about me to anyone. Let me take a quick look at their privacy policy to see what it says about all this."
>
>
"Okay, so even if they DO know what's in my voice mail, I'm sure Google won't share that information about me to anyone, right? Let me take a quick look at their privacy policy to see what it says about all this."
 
Changed:
<
<

"A Higher Sense of Privacy" -- Engineered User Reactions

>
>
Google's privacy policy is what I would call attractively deceptive. The attractive part is what Google wants you to see. The first line reminds us that Google believes that privacy is important. Shortly thereafter, we see a link to the U.S. Department of Commerce's Safe Harbor Program. That sure sounds safe. Reading further, we see that our personal information will only be processed for the purposes described in the policy and that our sensitive personal information will only be shared with outside individuals/companies with our consent. Up until now, this seems pretty attractive.

Here is the deceptive part. If we look at how the terms are defined and at what uses Google explicitly reserves, we see that accepting this policy opens the door to some startling possibilities. For example, Google has permission to process personal information, which includes names, email addresses, and billing information, on behalf of and according to the instructions of a third party, such as our advertising partners. Does this mean that Google will only ever process our personal information according to the instructions of an advertising partner? No. It can process this information to suit the needs of any third party. We as users have no control over who this is or how the data is processed. And even if Google doesn't directly give away our names or addresses, it does allow targeted advertising.

Google Voice has its own privacy policy that supplements Google's main policy. Here we find even more clever deception. For instance, if you delete something from your Google voice account, the deletion will take immediate effect in your account view.

"Whew! Good thing I got rid of THAT message. I could be in big trouble if it got around."

Unfortunately, the information is not deleted from Google's offline backup systems. In other words, it is there forever, permanently, and you've given Google permission to keep it. In effect, the only thing Google does when you delete the information is to keep you from being able to access it anymore. I suppose this is so you'll forget that Google still has it.

"A Higher Sense of Privacy" -- User Reactions to Google Voice

I was curious to see what the buzz on the internet was about privacy issues raised by Google Voice, so I did a search for "google voice privacy." One article discussed some of the advantages and disadvantages of Google Voice, noting that the possibility of advertisements was a disadvantage, although Google hadn't yet included any ads on the Google Voice site (as it has for Gmail). Then came a reader comment that really scared me:

"I don't see Google opening [Google Voice] up to ads, or at the very least, no targeted ads, as I feel that phone calls are a bit more sensitive than emails, and come with a higher sense of privacy. If they launched targeted ads, I think there would be a backlash, and a dropoff in usage."

I'm worried by this statement because I think this user almost completely correct. Most users probably don't want to see advertisements in Google Voice that appear to be targeted to the content of their phone calls. And I think most users believe that phone calls should be entitled to greater privacy protection than other forms of communication. The problem is that just because Google doesn't show ads on the Google Voice site doesn't mean that they aren't using your phone transactions and the content of your transcribed calls as inputs to their vast data mining operations. It only means that users are less likely to realize that this is what is happening. Unless Google is simply providing the Google Voice service out of the goodness of its heart, we can safely assume that Google intends to make money from its users conversations (the $30 million Google just spent in the Gizmo5 acquisition combined with the vast number of companies with whom Google has had to work to make Google Voice a reality is strong evidence that Google's cost of providing the service is significant, even if it pays next to nothing for the bandwidth).


SethLindnerFirstPaper 2 - 18 Nov 2009 - Main.SethLindner
Line: 1 to 1
 
META TOPICPARENT name="FirstPaper"
Changed:
<
<

Paper Title

>
>

In Progress...

The Many Privacy Problems with Google's Entry into Broadband Telecommunications, and Why Users Won't Even Notice

 -- By SethLindner - 06 Nov 2009
Changed:
<
<

Section I

Subsection A

Subsub 1

Subsection B

Subsub 1

>
>

Recent Google Acquisitions

Two acquisitions over the past two years indicate Google's apparent interest in entering into the VoIP telecommunications industry. Google's first move was its acquisition in 2007 of a company called GrandCentral, a web-based call forwarding system that provided users with a single phone number from which calls could be routed to multiple other phone numbers based upon user-configurable preferences (like who was calling and when). After continuing operations as GrandCentral for about two years, in April of 2009 the service was launched as Google Voice. In addition to the call forwarding features of GrandCentral, Google Voice adds call screening, blocking of unwanted calls, and voice transcription to text of voicemail messages. Currently Google claims to have more than 1.4 million users of Google Voice, of which about 570,000 are active users.
 
Changed:
<
<

Subsub 2

>
>
Although the Google Voice service probably seemed useful to those with many phone numbers, it wasn't exactly what people think of as a VoIP service because all phone calls still needed to be routed to a permanent phone number. So, even though Google Voice was free to use, it really wasn't anything close to a replacement for existing telephone services. This is where Google's recent acquisition of a company called Gizmo5 comes in.
 
Added:
>
>

Don't Look Too Closely -- Google's Privacy Policy

One of the significant features of Google Voice is its ability to provide written transcriptions of voice mail messages and recorded phone calls. I imagine that the eyebrows of even those with the utmost trust for the Google conglomerate were raised upon learning of this feature.
 
Added:
>
>
"Wait a minute. Google knows exactly what someone told me in my voice mail?"
 
Changed:
<
<

Section II

>
>
Yes, Google does know. Your just surprised because their proving it to you by sending you a transcript.
 
Changed:
<
<

Subsection A

>
>
"Okay, so even if they DO know what's in my voice mail, I'm sure Google won't share that information about me to anyone. Let me take a quick look at their privacy policy to see what it says about all this."
 
Changed:
<
<

Subsection B

>
>

"A Higher Sense of Privacy" -- Engineered User Reactions


SethLindnerFirstPaper 1 - 06 Nov 2009 - Main.SethLindner
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="FirstPaper"

Paper Title

-- By SethLindner - 06 Nov 2009

Section I

Subsection A

Subsub 1

Subsection B

Subsub 1

Subsub 2

Section II

Subsection A

Subsection B


Revision 20r20 - 07 Sep 2011 - 00:44:13 - IanSullivan
Revision 19r19 - 01 Feb 2010 - 22:40:40 - SethLindner
Revision 18r18 - 24 Jan 2010 - 15:52:29 - EbenMoglen
Revision 17r17 - 24 Dec 2009 - 00:29:28 - SethLindner
Revision 16r16 - 07 Dec 2009 - 00:25:37 - SethLindner
Revision 15r15 - 03 Dec 2009 - 07:04:27 - BrianS
Revision 14r14 - 01 Dec 2009 - 04:05:31 - BradleyMullins
Revision 13r13 - 30 Nov 2009 - 18:12:43 - AllanOng
Revision 12r12 - 29 Nov 2009 - 22:34:48 - GavinSnyder
Revision 11r11 - 28 Nov 2009 - 22:55:41 - SethLindner
Revision 10r10 - 28 Nov 2009 - 06:43:40 - BrianS
Revision 9r9 - 25 Nov 2009 - 18:07:34 - HeatherStevenson
Revision 8r8 - 24 Nov 2009 - 08:53:29 - BrianS
Revision 7r7 - 23 Nov 2009 - 19:56:59 - SethLindner
Revision 6r6 - 23 Nov 2009 - 15:34:08 - SethLindner
Revision 5r5 - 20 Nov 2009 - 17:16:11 - SethLindner
Revision 4r4 - 19 Nov 2009 - 20:54:56 - SethLindner
Revision 3r3 - 19 Nov 2009 - 04:01:23 - SethLindner
Revision 2r2 - 18 Nov 2009 - 02:28:10 - SethLindner
Revision 1r1 - 06 Nov 2009 - 15:07:29 - SethLindner
This site is powered by the TWiki collaboration platform.
All material on this collaboration platform is the property of the contributing authors.
All material marked as authored by Eben Moglen is available under the license terms CC-BY-SA version 4.
Syndicate this site RSSATOM