{"id":234,"date":"2024-05-23T10:07:56","date_gmt":"2024-05-23T14:07:56","guid":{"rendered":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/?p=234"},"modified":"2024-05-23T10:07:56","modified_gmt":"2024-05-23T14:07:56","slug":"the-ai-update-may-23-2024","status":"publish","type":"post","link":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/2024\/05\/23\/the-ai-update-may-23-2024\/","title":{"rendered":"The AI Update | May 23, 2024"},"content":{"rendered":"

\"\"#HelloWorld. Summer days are almost here. In this issue, we dive into the new Colorado AI Act, explore the impact of AI technologies on search providers\u2019 liability shields, and track a U.S. district court\u2019s strict scrutiny of anti-web-scraping terms of use. We finish by recapping a spirited test match on AI policy across the pond. Let\u2019s stay smart together. (<\/i>Subscribe to the mailing list<\/i><\/a>\u00a0to receive future issues.)<\/i><\/p>\n

<\/p>\n

Colorado AI Act<\/b>. These days, states seem to be driving much of the action on AI legislation. In the most recent development, Colorado just passed SB 24-205 \u201cConcerning Consumer Protections in Interactions with Artificial Intelligence<\/a>.\u201d It was signed into law with gubernatorial reservations<\/a> after the Connecticut bill<\/a> on which it was modeled failed due to concerns about stifling innovation. The law takes effect on February 1, 2026, and will be enforced by the state attorney general.<\/p>\n

Following a framework reminiscent of earlier state laws and the EU AI Act, Colorado\u2019s new law sets out requirements for developers and deployers of \u201chigh-risk artificial intelligence systems\u201d\u2014those impacting \u201cconsequential decisions\u201d like education enrollment, employment, lending, essential government services, health-care services, housing, insurance, or legal services.<\/p>\n

Under the law, developers\u2019 and deployers\u2019 principal obligation is to \u201cuse reasonable care to protect consumers from any known and reasonably foreseeable risks of algorithmic discrimination.\u201d (Although, for customer-facing chatbots, having a user policy forbidding discrimination may suffice.)<\/p>\n

Additionally, developers must (a) provide a high-level summary of data types used to train the AI system; and (b) share how the system was evaluated for performance and to mitigate discrimination. Deployers must (a) conduct impact assessments at least annually and following any major system modification; (b) notify consumers when an AI system is being used; and (c) provide consumers with information about the system, an opportunity to correct their personal data, and a chance to appeal adverse consequential decisions.<\/p>\n

Not-so-safe harbors?<\/b> \u201cAI Overviews\u201d\u2014webpage summaries generated by LLMs in response to web search queries\u2014are coming soon to fabled search engines<\/a> near you. Traditionally, these kinds of online intermediary platforms were able to benefit from safe harbors like Section 230 of the Communications Decency Act<\/a> and Section 512(a) of the Digital Millennium Copyright Act<\/a>. These legal shields, roughly speaking, protect online platforms against tort and copyright claims when the platforms merely pass through content provided by third parties (and comply with various other conditions).<\/p>\n

But what to do when AI-generated summaries leave out citations and hyperlinks to the original sources? Can these online safe harbors still apply then? While the law remains open, a recent Washington Post<\/i> article<\/a> provides an early exploration of the issue. One strand of emerging thinking signals significant risk that these legal shields may be lost. By leaving out attribution information, AI summaries can obscure the third-party content from which the answers were derived. So what can be done? Perhaps search engines will deliberately build back hyperlinks and attribution in future iterations of AI summaries. Or perhaps, per the Post<\/i>, they\u2019ll frame the generated summaries as \u201cmere suggestions rather than actionable information.\u201d Internet law aficionados, watch this space closely.<\/p>\n

Public data scraping, terms of use, and copyright preemption<\/b>. On the subject of websites: Since the Ninth Circuit\u2019s 2019 decision hiQ v. LinkedIn<\/i>, <\/i>there\u2019s been a heuristic of sorts around scraping the web. It is permitted for data designated as public (think your public-facing social media account), not behind a paywall, so long as the scraper isn\u2019t on actual notice of anti-scraping clauses in binding, enforceable website terms of use. On May 9, however, the Northern District of California took a turn down a different road.<\/p>\n

In X Corp. v. Bright Data Ltd., No. C 23-03698 WHA, Dkt. No. 83 (N.D. Cal. May 9, 2024)<\/a>, the former Twitter sued Bright Data, alleging among other things, that its scraping of public posts violated X\u2019s Terms of Service, including a specific clause stating that \u201cscraping the Services in any form, for any purpose without our prior written consent is expressly prohibited.\u201d Straightforward contract breach, right? No so fast. The district court held that copyright law pre-empted the claim. Why? Because those same Terms of Service gave X only a nonexclusive<\/i> license to users\u2019 posts, not ownership over that data. Why does that matter? Because copyright law permits only exclusive <\/i>owners to enforce rights in their works against third-party copiers\u2014and X\u2019s anti-scraping contract clause would seem to confer those classic ownership rights on nonexclusive<\/i> licensees. So? According to the court, this creates a \u201cprivate copyright system\u201d that \u201cwould yank into the private domain and hold for sale information open to all, exercising a copyright owner\u2019s right to exclude where it has no such right.\u201d<\/p>\n

The upshot for AI: With high-quality online data only increasing in value for model training purposes, site owners that rely on public content postings would do well to start marshalling legal strategies for defending their anti-scraping service terms of use.<\/p>\n

What we\u2019re reading. <\/b>The U.K. House of Lords is keeping the pressure on. Back in February, its Select Committee on Communications and Digital published a report<\/a> exhorting the U.K. government to address certain generative AI risks, including copyright fairness. The government responded<\/a> in April, but the Committee just keeps on pushing. On May 2, it published a letter<\/a> urging the government to go further and faster, in three pages of no punches pulled. \u201cThe government\u2019s record on copyright is inadequate and deteriorating.\u201d Oof.<\/p>\n

What should<\/i> we be following?<\/b> Have suggestions for legal topics to cover in future editions? Please send them to AI-Update@duanemorris.com<\/a>. We\u2019d love to hear from you and continue the conversation.<\/p>\n

Editor-in-Chief<\/em><\/strong>: <\/strong>Alex Goranin<\/a><\/p>\n

Deputy Editors<\/em><\/strong>:<\/strong> Matt Mousley<\/a> and Tyler Marandola<\/a><\/p>\n

If you were forwarded this newsletter, <\/em>subscribe to the mailing list<\/em><\/a> to receive future issues.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

#HelloWorld. Summer days are almost here. In this issue, we dive into the new Colorado AI Act, explore the impact of AI technologies on search providers\u2019 liability shields, and track a U.S. district court\u2019s strict scrutiny of anti-web-scraping terms of use. We finish by recapping a spirited test match on AI policy across the pond. … <\/p>\n

Continue reading “The AI Update | May 23, 2024”<\/span><\/a><\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[176,41,15,185,186,184,13,17],"ppma_author":[5],"class_list":["post-234","post","type-post","status-publish","format-standard","hentry","category-general","tag-ai-policy","tag-ai-update","tag-alex-goranin","tag-colorado","tag-connecticut","tag-matt-moousley","tag-theaiupdate","tag-tylermarandola"],"authors":[{"term_id":5,"user_id":6,"is_guest":0,"slug":"duanemorris3","display_name":"Duane Morris","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/843ff6e7a8fe5fc92109b47a45f34b6cf0ea499e6e788db23456c838b0ae6747?s=96&d=blank&r=g","0":null,"1":"","2":"","3":"","4":"","5":"","6":"","7":"","8":""}],"_links":{"self":[{"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/posts\/234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/comments?post=234"}],"version-history":[{"count":0,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/posts\/234\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/media?parent=234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/categories?post=234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/tags?post=234"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.duanemorris.com\/artificialintelligence\/wp-json\/wp\/v2\/ppma_author?post=234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}