{"id":2563,"date":"2015-04-26T18:01:24","date_gmt":"2015-04-26T09:01:24","guid":{"rendered":"https:\/\/regex.info\/blog\/2015-04-26\/2563"},"modified":"2015-04-26T18:01:24","modified_gmt":"2015-04-26T09:01:24","slug":"potential-privacy-issue-with-lightroom-cc6-and-people-keywords","status":"publish","type":"post","link":"https:\/\/regex.info\/blog\/2015-04-26\/2563","title":{"rendered":"Potential Privacy Issue with Lightroom CC\/6 and People Keywords"},"content":{"rendered":"\n\n
\n

Note: The bug mentioned in this article has been fixed as of Lr6.1 (Lr CC 2015.1)<\/span>\n<\/p>\n<\/div>\n\n

Lightroom CC\/6 has been\nout for a few<\/span> days<\/a>, and in working with\nLightroom's new Face Tagging feature, I've run across something that could\nbe a privacy<\/span> issue for some folks.<\/p>\n\n

Keywords in Lightroom have an “<\/span>Include on\nExport”<\/span> option; if it's disabled, the keyword\nis not (supposed to be) included in exported copies of photos. This is\nuseful for workflow-related keywords that you use merely to help manage\nyour catalog, or for keywords you'd rather not expose to the public.<\/p>\n\n

The problem I've discovered in Lightroom CC\/6 is that the “<\/span>Include on Export”<\/span>\noption is ignored if it's a “<\/span>Person”<\/span> keyword (one used with the new Face Tagging\nfeature).<\/p>\n\n

For example, imagine tagging photos from an office party and giving your boss\nthe snarky name “<\/span>My Jerk of a Boss<\/span>”<\/span>. Of course, you'd not want to expose that\nin copies you uploaded or shared with others, so you'd think you were safe\nby disabling “<\/span>Include on Export”<\/span> like this:<\/p>\n\n

<\/div>\n\n

Lightroom's Publish\/Export dialog includes a standard<\/span> section on what metadata to include in\nthe exported copies:<\/p>\n\n

<\/div>\n\n

The “<\/span>Remove Person Info”<\/span> option is new in Lightroom CC\/6, and it seems\nthat it (and it alone<\/i>) controls whether “<\/span>Person”<\/span> keywords are\nincluded in export. If this remove<\/span> option is not\nturned on, all Person keywords are exported even if their “<\/span>Include on Export”<\/span>\noption has been explicitly disabled<\/i>.<\/p>\n\n

In the “<\/span>My Jerk of a\nBoss<\/span>”<\/span> example, you might have wanted\nother<\/i> People keywords to be included, so not turned on the “<\/span>Remove Person Info”<\/span>\noption, thinking that the lack of “<\/span>Include on\nExport”<\/span> would keep “<\/span>My Jerk of a Boss<\/span>”<\/span> out of the images you share. I\nassume<\/span> that's how it's supposed<\/i> to work, but it doesn't.<\/p>\n\n

I don't suppose that this bug (if that's what it is) will actually affect very many people,\nbut if it does, it could be a doozy.<\/span><\/p>\n\n

I've reported it to Adobe. I'll update this post with new info as it becomes available.<\/p>\n\n\n

In related news, I've figured out how to bring the Face-Tagging feature\nto my Facebook\nplugin<\/a>. For example, after having used Lightroom's Face Tagging feature to identify faces of\nfriends in the photos from the 100km bike ride<\/a> I\nrecently<\/span> wrote about, all the tagging in\n\nthe exported copies at Facebook<\/a> was automatic via the beta version of\nmy plugin. It was nice<\/span> not to have to walk through every copy at Facebook\nand tag people.<\/p>\n\n

So that's something to look forward to. It was while<\/span> working on this that I discovered<\/span> the potential privacy issue.<\/p>\n\n\n","protected":false},"excerpt":{"rendered":"

Note: The bug mentioned in this article has been fixed as of Lr6.1 (Lr CC 2015.1) <\/p>

Lightroom CC\/6 has been out for a few days, and in working with Lightroom's new Face Tagging feature, I've run across something that could be a privacy issue for some folks.<\/p>

Keywords in Lightroom have an \"Include on Export\" option; if it's disabled, the keyword is not (supposed to be) included in exported copies of photos. This is useful for workflow-related keywords that you use merely to help manage your catalog, or for keywords you'd rather not expose to the public.<\/p>

The problem [...]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"_links":{"self":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/posts\/2563"}],"collection":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/comments?post=2563"}],"version-history":[{"count":0,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/posts\/2563\/revisions"}],"wp:attachment":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/media?parent=2563"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/categories?post=2563"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/tags?post=2563"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}