Getty Images vs Creative Commons and Privacy: What Bloggers Need to Know

This is a guest post written by Simon Schmid of iubenda.

Getty Images recently announced a new image embed feature that allows bloggers (and others) to access and use their vast library of images for non-commercial purposes. This rather remarkable change in policy by Getty Images shows that it’s ready to work with content creators and adapt to the times we live in.

Even WordPress also published an announcement post in which they share the details of Getty’s new offering and how easy it is to embed an image into your blog. There’s now a “</>” below every image in the catalogue that lets you effortlessly publish that particular image into your post (to be completely accurate and to quote from the terms for the first time, “Not all Getty Images Content will be available for embedded use, and availability may change without notice”).

How easy is it really over all though? And is it entirely without complications? Let’s review some of the most important clauses in theterms of the embed feature and we’ll do this by comparing this with another very popular image source (images under a Creative Commons license) for bloggers.

What can you use Getty’s embed for?

At first you must to be very clear about the fact that Getty’s model is the licensing of images. Therefore you will have to play by their rules and expect to do something for them in return. I’ve read comments on the WordPress announcement that communicated their leave from using the system as soon as ads start appearing. What I’m saying is, that this is something that might be in the works and something that you’ll have to be willing to give back in exchange.

“You may only use embedded Getty Images Content for editorial purposes (meaning relating to events that are newsworthy or of public interest).”

Using the “Embedded Viewer” you consent to use the images for editorial purposes only. Editorial purposes are in a very wide sense non-commercial purposes. This becomes more clear when you read the rest of the terms regarding the “Embedded Viewer”. It outlines that you may not use the images in any of the following ways:

• (a) for any commercial purpose (for example, in advertising, promotions or merchandising) or to suggest endorsement or sponsorship;
• (b) in violation of any stated restriction;
• (c) in a defamatory, pornographic or otherwise unlawful manner; or
• (d) outside of the context of the Embedded Viewer

Therefore the most important question that needs to be answered is the notion of “commercial”. What kind of use constitutes commercial use, and therefore exceeds the limits of what is allowed with the viewer? Is Here’s an official statement by Craig Peters that goes into detail and helps us at understanding non-commercial use:

Blogs that draw revenues from Google Ads will still be able to use the Getty Images embed player at no cost. “We would not consider this commercial use,” says Peters. “The fact today that a website is generating revenue would not limit the use of the embed. What would limit that use is if they used our imagery to promote a service, a product or their business. They would need to get a license.” A spokeswoman for Getty Images confirms to BJP that editorial websites, from The New York Times to Buzzfeed, will also be able to use the embed feature as long as images are used in an editorial context.

Compare these facts above to going with Creative Commons content instead:

Creative Commons: Creative Commons-licensed images can be used for any purpose, by anyone, anywhere. That’s as long as you follow the terms of that specific license. None of the CC licences outlines that a piece of licensed content may only be used for a specific purpose–editorial or otherwise.

Creative Commons II: NonCommercial in CC’s Attribution-NonCommercial 4.0 means “not primarily intended for or directed towards commercial advantage or monetary compensation” which naturally is a much friendlier definition.

Creative Commons III: the restriction of not displaying outside of the Embedded Viewer does not apply to CC-licensed content, in fact it expressly states that you are allowed to exercise the licensed rights in “all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so”. This can be a deal breaker for things like image carousels or videos or the like.

One more very interesting fact is that Getty can revoke the access to the embedded imagery at any time: “Upon request, you agree to take prompt action to stop using the Embedded Viewer and/or Getty Images Content”. Creative Commons on the other hand declares their licensing to be irrevocable. This ensures that you don’t have to go back and make changes anytime down the road.

Let’s take a look at both solutions side by side:

Apart from the very obvious branding that the embed gives you, we may have another issue that you should at least know about and isn’t immediately obvious. Embedding services like Youtube and others (like the embedding of your image) and even a like button open up another legal field: data privacy.

Looking at a page with Getty embed in Chrome’s cookie window.

What you can see in this window (Chrome’s developer tools, right click and then “Inspect Element”) are the cookies that this page sets with just the embedded image. There are two main elements. The first being the tracking by Getty’s embedding window, the other one caused by the social sharing buttons by Twitter and Tumblr, both also part of the Embedded Viewer.

So why is this so problematic? Essentially, an iframe like this allows their owner (Google, Facebook, Getty…) to make a connection. That connection is between the embedding site, their reader and the third-party host. Or how EFF puts it:

The third-party host can possibly get and log your IP address and the exact time of the request; information about the web browser you’re using, your browser’s version, your operating system, processor information, language settings, and other data; the URL of the website you’re coming from; and sometimes tracking cookies.

The way this affects you as a site owner is that the least you can do is to minimize legal implications and include a description of this data collection in your privacy policy. Above all in Europe there’s a stance by regulators that assumes that cookies may only be placed without user consent if services wouldn’t work without them. That’s not the case for social sharing buttons (mostly). The vague privacy policy posted on Getty’s site is cause for doubting the future use on a site that’s compliant with privacy laws around the world and most of all, in Europe.

Takeaway I: Getty is taking the right steps by making their images easy to use for editorial purposes, however there are still a couple of issues concerning their acceptable use policy (alleged first comments surfaced claiming that Getty Germany denied a blogger/freelancer the free embedding because of his blog being on the same domain as his freelancer page).

If you aren’t ready to accept some of the drawbacks described above, Creative Commons is more than an interesting alternative.

Takeaway II: the knowledge about Getty’s future data collection is murky at best. At least European bloggers should consider including statements about Getty’s iframe and the Twitter/Tumblr sharing buttons included in the iframe. There are a couple of resources out there that help you with crafting a privacy policy. We at iubenda make it really easy for bloggers to generate their legal document with a couple of clicks by simply adding the Twitter/Tumblr and Getty services to their privacy policy.

Addendum:

How to choose Getty Images for your posts

It’s really as simple as clicking on the “</>” provided below the images and then using the embedding code.

How to choose Creative Commons licensed images for your posts

It isn’t that hard to find CC-licensed pictures either, use one of the following methods below:

• Flickr
• Wikimedia Commons
• Google Search
• Bing Search

Resources used:

I, II, III, IV

Simon Schmid blogs at thegodfounder.com and works on iubenda.