Both Google+ and Picasa are governed by Google's Terms of Service, and involve a nonexclusive license of user data to Google. Take away the license, and you take the "share" out of a sharing service. Users are right to pay attention to the scope and implications of the license, and it's fantastic to see people examining it and making sure they're comfortable with the terms.

Professional photographer, podcaster, and prolific bloggerScott Bourne is no stranger to giving close reads to user license grants. Scott has decided not to use Google services in connection with his photography because he's rightly concerned it's impossible for him to grant an exclusive license for use and display of his work — something he and other photographers routinely need to do — if he has already licensed those rights elsewhere. It's an excellent point that photographers should bear in mind when using any Web service that stores, displays, and distributes their work. (We discussed this more on TWiL last week in connection with looking at the Dropbox terms of service.)

For users who don't need, as a matter of livelihood, to grant exclusive licenses to the text or photos they might otherwise share on a social network, Google's terms are a different matter. They grant Google the license to use submissions as necessary to run its services, with the following limitation:

This license is for the sole purpose of enabling Google to display, distribute and promote the Services...

"The Services" are elsewhere defined as Google's products, software, services and web sites. Google would have a hard time using user content for anything other than operating and "promoting" its services (more on that below) given this language.

There are, however, a couple of areas where, as a lawyer and user, I wish the Google terms were more clear and user-cognizant.

First, users agree to let Google "make [their] Content available to other companies, organizations or individuals with whom Google has relationships for the provision of syndicated services," and that Google and those third parties may "use such Content in connection with the provision of those services." "Syndicated services" aren't otherwise defined, so I'm not sure what to make of this. What kind of activity is this intended to cover? API calls? RSS and Atom? It would be nice to see an explanation there, bearing in mind that while users may decide they trust Google, granting unspecified, Google-discretionary rights to "other companies, organizations or individuals with whom Google has relationships" is (or should be) a user red flag. Those relationships are Google's, not the user's.

Second, and another user red flag issue, is the "promotion" license. By signing up for Picasa and Google+, users do not reasonably contemplate pictures of their little "Sophie," conscientiously shared only to a "family" circle, showing up in ads or other materials Google may use to "promote" its services. I'm not saying Google would do this, but if that's not the intent, the license is too broad and the language should change. Worse, it's off-putting and inconsistent with the huge strides Google is making on the user trust, confidence, and privacy fronts with its Circles system. My suggestions: either eliminate "to promote" from the description of the license purpose, or provide reasonable limits, choices, and opt-outs for users for what kind of promotion is acceptable, and which submissions, if any, are eligible. (Maybe some parallel to Circles could be useful in implementing.) Surprises on this front are frustrating for users, and a potential PR disaster for the service — as Google wellknows.

Bottom line: I'm not personally overwrought by the license Google asks users to grant, but it could use some clarification and adjustment on the issues of third parties and promotional use.

Also worth noting:

The "Ending your relationship with Google" section, paragraph 13 of the terms, is a well-written, straightforward, user-friendly complement to Google's Data Liberation Front.

Picasa supports Creative Commons. Go to Picasa's Settings > Privacy and Permissions tab, and you'll see four CC licenses available. Unfortunately, this is a batch selection, not a photo-by-photo one. (Another potentially good place to implement Circles-type controls.)

Updates, July 11, 2011:

William Carleton comments he thinks the full/downloaded app version of Picasa allows for photo-by-photo license selection. I've been using Picasa Web Albums, which is all of the product a user might ever see if they're using it solely in connection with Google+.

Trout Monfalco points out that Twitpic recently used its licenses from users to enter into a deal with World Entertainment News Network whereby the latter will sell images originally posted on Twitpic for publication. (See Joshua Brustein/NY Times, Fine Print Blurs Who's in Control of Online Photos.) Remember that Google's terms of service expressly limit the purpose of the license to "enabling Google to display, distribute and promote the Services" (presumably ruling out deals like the Twitpic/WENN one as long as the limitation remains in place). Note Facebook has no such "purpose" limitation; users simply grant Facebook a license to "use" their "IP content."

Rolando Gomez further examines Google's terms of service from a photographer's perspective, and particularly focuses on the perpetual, nonrevocable nature of the user license. (The content license to Google would survive even a user's express termination of her/his relationship with Google per paragraph 13 of the terms, since rights "which are expressed to continue indefinitely" are exempted.) The duration of the user license on Facebook has been subject to much public discussion and backlash, and it currently "ends when you delete your IP content or your account unless your content has been shared with others, and they have not deleted it." So, is Google guilty of a "rights grab" if the user license remains nonrevocable? I think the express "purpose" limitations go a long way toward making the duration of the license (i.e., as long as the original copyright exists) palatable. Creative Commons licenses too arenonrevocable. And as Creative Commons wisely cautions, "if you depend on controlling the copyrights in your resources for your livelihood, you should think carefully before giving away commercial rights to your creative work."

Reader Comments (11)

Good post. I've found Picassa suddenly relevant as the combination of Android, Google+ on mobile, and Picassa on the web all interact so well. Small point but I do think it's possible to edit the copyright and CC permissions photo-by-photo, at least on the full Picassa web site (though maybe when I think I am doing that to a single photo, I am resetting others -- not 100% sure).

I addressed Bourne's absurd post in one of my one. Scott has been known to cry wolf more times then I can count on my fingers. Do a google search for his name at Weta Pixel and you will find some interesting back story.

My biggest concern with the ToS is that it doesn't give me the right to tell Google to stop using my stuff, should I decide that I don't like what they're doing with it.

Much of the ToS is CYA, allowing Google to make anything you post public, whether by accident or on purpose. That may be a reasonable requirement, given that they're likely to make poor design decisions and likely to introduce embarrassing errors. But in essence, the ToS asks us that we trust Google to do the right thing, without Google spelling out exactly what the right thing is.

Google is asking us to trust them without giving us the ability to back out later. Sure, we can quit posting additional material and terminate the ToS, but it seem that 13.5 allows Google to continue using anything we've already posted even if we don't like what they ended up doing with it.

Picasa Web does allow for setting the license on a per image basis.Examples:CC BY-NC: https://picasaweb.google.com/lh/photo/zIubaohSDMXCWlw-dzD0iQ?feat=directlinkAll rights reserved: https://picasaweb.google.com/lh/photo/g31t32hIGYsPWGeQs5MIfw?feat=directlink

To change it go to the image, on the lower right it says "Photo reuse" with the license and an edit link. Click on edit and a form comes up that allows you to change the license.

I can NOT deny reuse to photos uploaded automatically from my android device to google+ and thence to an album in picasa web.

So, if you care, do not upload photos via your android device. There is a setting on your android device to automatically upload photos, uncheck the box. Plug your device into your PC and upload that way.

I'm glad people are growing more concerned over terms of service and terms/conditions. Please be aware of a website dedicated to monitoring those, and educating the public about what reasonable terms and conditions are for the many contest solicitations that exist today: artists-bill-of-rights.org

I don't think anyone has legally challenged the passive granting of rights to social services. Where there has been improvements to the consumer is when there has been broad public outcry. So guess who really has to look after our interests? We do.

True, the Google+ T/S are an improvement. However, "canceling" ToS do not apply to what already exists on Google's servers, IMHO. How is Google to know where all those images exist that have been reused in all their syndicated services? How do they prevent other entities "re-sharing" those images back onto the Google pipeline?

My point is, just like a CC license, you cannot "ungrant" what privileges you granted unless the party violated the original terms of your license. Google could make the same argument. Some may think I'm hysterical, but remember, Google was in complete support of the Orphan Works Act of 2008 that passed the Senate and nearly passed the House. Under that law, any image that was not registered with the U.S. Copyright Office, and any number of "independent" registries, could be "orphaned" and allowed to be used for commercial or any other purpose. The reason you may not have known about that law is that all the "bargaining" took place very quietly, and it passed the Senate without a single vote being cast, a process called "hotlining". I don't think hardly a single Senator even read the bill.

I'm not saying Google would do this, but if that's not the intent, the license is too broad and the language should change. Worse, it's off-putting and inconsistent with the huge strides Google is making on the user trust, confidence, and privacy fronts with its Circles system.DCUO Cash