{"id":51868,"date":"2016-09-30T11:27:00","date_gmt":"2016-09-30T16:27:00","guid":{"rendered":"https:\/\/content.findlaw-admin.com\/ability-legal\/supreme\/legal-commentary\/facebook-follies-why-facebooks-recent-change-to-its-user-agreement-was-a-bad-move-and-will-likely-be-unenforceable.html"},"modified":"2016-09-30T11:27:00","modified_gmt":"2016-09-30T16:27:00","slug":"facebook-follies-why-facebooks-recent-change-to-its-user-agreement-was-a-bad-move-and-will-likely-be-unenforceable","status":"publish","type":"supreme","link":"https:\/\/supreme.findlaw.com\/legal-commentary\/facebook-follies-why-facebooks-recent-change-to-its-user-agreement-was-a-bad-move-and-will-likely-be-unenforceable.html","title":{"rendered":"Facebook Follies: Why Facebook&#8217;s Recent Change to its User Agreement Was A Bad Move, and Will Likely Be Unenforceable"},"content":{"rendered":"\n<div class=\"wp-container-core-columns-is-layout-9d6595d7  fl-block-columns fl-sectionWithSidebar fl-container fl-flex fl-flex-wrap fl-gap30\">\n    \n    <div class=\"fl-page-articles   fl-block-column fl-section-main fl-section-main-full-width\">\n        <div class=\"yui-g\" id=\"leftcol-module\">\n      <!-- Right Line of Links Section -->\n      <!-- BEGIN PICTURE INSERTION -->\n      <!-- BEGIN TITLE AND AUTHOR INSERTION -->\n      <table>\n        <tr>\n\n          <td width=\"100\" rowspan=\"3\" class=\"wauthor\"><a href=\"\/legal-commentary\/anita-ramasastry-archive\"><img decoding=\"async\" src=\"https://supreme.findlaw.com/static/f/images\/writ\/anita.ramasastry.jpg\" border=\"0\" alt=\"Anita Ramasastry\"><\/a><\/td>\n\n          <td class=\"wititle\"><h1>Facebook Follies: Why Facebook&#8217;s Recent Change to its User Agreement Was A Bad Move, and Will Likely Be Unenforceable<\/h1><\/td>\n        <\/tr>\n\n        <tr>\n          <td class=\"wauthor\"><a href=\"\/legal-commentary\/anita-ramasastry-archive\" class=\"graybold\"><h2>By ANITA RAMASASTRY <\/h2><br><\/a><\/td>\n        <\/tr>\n        <tr>\n          <td class=\"widate\">Tuesday, Feb. 24, 2009<\/td>\n\n        <\/tr>\n      <\/table>\n\n<p> Why are 130,000  Facebook users very angry? The culprit  is a small but significant change to Facebook&#8217;s Terms of Service (its contract  with its users) that was made without full notification to all users. The change was a seemingly radical shift:  Facebook amended its contract language to reserve the right to continue to use  member content forever &#8212; even long after users have closed their accounts or  deleted their content.<\/p>\n<p> Users post  a great deal of content on their Facebook pages, from age, to marital status,  to favorite movies, cars, and even political affiliations. This content is valuable to Facebook and its  affiliates for marketing purposes and for possible resale. Can Facebook now do anything it wants with  that content? That answer is unclear, but what <u>is<\/u> clear is that Facebook  should not &#8212; and legally cannot &#8212; unilaterally change its Terms of Service without  giving users proper notice.<\/p>\n<p> In this  column, I will outline Facebook&#8217;s actions and the public&#8217;s response. I will also discuss why Facebook was legally  required to give its members proper notice of the change, coupled with a chance  to unsubscribe or at least to have their prior data governed by the earlier  user agreement.<\/p>\n\n\n<!-- 300x250 AD -->\n\n\n<p><strong>Facebook&#8217;s Foolish Move: Amending Its  Terms of Service and Failing to Be Open with Users About the Change<\/strong><\/p>\n<p> This is not the  first time that Facebook has caused a public outcry over its privacy  practices. As I have noted in previous  columns <a href=\"\/legal-commentary\/facebooks-fan-sumers-do-social-ads-violate-users-privacy.html\">such  as this one<\/a>, Facebook has tried new features involving user content  that have sparked controversy. This  time, however, Facebook took a bold step with its contract that seemed to alter  the very nature of the bargain it had struck with its members.<\/p>\n<p> When you join  Facebook, under its Terms of Service, you grant Facebook a &#8220;license&#8221; (that is,  legal permission) to use your content &#8220;on or in connection with the  Facebook Service or the promotion thereof.&#8221; To some extent, such a license is  necessary. While you are using Facebook,  it may need to process, store, or share your data with others as part of providing  services to you. The controversy  occurred because of Facebook&#8217;s recent revision to the license \u2013 purporting to  eliminate language that guaranteed that the license would &#8220;automatically  expire&#8221; if content were removed from the site.<\/p>\n<p> How did Facebook  notify customers of this change? First, Suzie White, Facebook&#8217;s corporate counsel  for commercial transactions, announced the change on the company&#8217;s blog on  February 4. Ms. White wrote, &#8220;We want to  let you know that today we&#8217;re updating our Terms of Use &#8212; the rules you and  Facebook agree to when you sign up to use the site. We used to have several  different documents that outlined what people could and could not do on  Facebook, but now we&#8217;re consolidating all this information to one central  place. We&#8217;ve also simplified and clarified a lot of information that applies to  you, including some things you shouldn&#8217;t do when using the site.&#8221; <\/p>\n<p> White did  provide a link to the new Terms of Service, but did not highlight the change  relating to the perpetual license.  Facebook also did not send out an email or any other mass communication  to notify users of these changes. And  White&#8217;s brief post, which didn&#8217;t call attention to the content license, largely  went unnoticed by users.<\/p>\n<p> A few days  later, a blog, <a href=\"http:\/\/consumerist.com\/\" rel=\"noopener\">The Consumerist<\/a>, drew public attention to the change. The blog described the change as &#8220;We Can Do  Anything We Want With Your Content. Forever.&#8221;  That description was pretty much accurate. The new Terms of Service read as follows: <\/p>\n<p>&#8220;You hereby grant Facebook an irrevocable, perpetual,  non-exclusive, transferable, fully paid, worldwide license (with the right to  sublicense) to (a) use, copy, publish, stream, store, retain, publicly perform  or display, transmit, scan, reformat, modify, edit, frame, translate, excerpt,  adapt, create derivative works and distribute (through multiple tiers), any  User Content you (i) Post on or in connection with the Facebook Service or the  promotion thereof subject only to your privacy settings or (ii) enable a user  to Post, including by offering a Share Link on your website and (b) to use your  name, likeness and image for any purpose, including commercial or advertising,  each of (a) and (b) on or in connection with the Facebook Service or the  promotion thereof.&#8221;<\/p>\n<p> The new Terms of Service differed  from the old Terms of Service, due to the deletion of these two sentences: &#8220;You may remove your User Content from the  Site at any time. If you choose to remove your User Content, the license  granted above will automatically expire, however you acknowledge that the Company  may retain archived copies of your User Content.&#8221; These sentences had made the license limited,  not perpetual. <\/p>\n<p><strong>Users Revolt, EPIC Threatens to  Complain, and Facebook Caves<\/strong><\/p>\n<p> In response to  the furor over the Facebook Terms of Service changes, the nonprofit Electronic  Privacy Information Center (EPIC) prepared a draft complaint, which it planned  to file with the Federal Trade Commission (FTC), stating that Facebook&#8217;s  changes amounted to a deceptive trade practice. The complaint contended that &#8220;It simply cannot  be correct that Facebook, having induced millions of Internet users to provide  detailed personal information to share with their friends and colleagues, can  now transform the terms of service under a take-it-or-leave-it edict that does  not even allow users who choose to cancel the service the opportunity to  recapture the data they provided. It is precisely in such circumstances that  agencies charged with protecting consumers and safeguarding a fair and  transparent marketplace must intervene.&#8221;<\/p>\n<p> Meanwhile,  Facebook users founded the site People against the New Terms of Service to  protest the change &#8212; which now has 130,000 members and is growing.<\/p>\n<p> Based on the  possible FTC enforcement action and the public criticism, Facebook caved. Barry Schmitt, a Facebook spokesperson,  noted, &#8220;It was never our intention to confuse people or make them uneasy about  sharing on Facebook. I also want to be very clear that Facebook does not, nor  have we ever, claimed ownership over people&#8217;s content. Your content belongs to  you.&#8221; Schmitt added, &#8220;We do need certain  licenses in order to facilitate the sharing of your content through our  service. That&#8217;s where the Terms of Use come in.&#8221; Schmitt noted that Facebook would be studying  its Terms of Use and revising them anew but &#8220;[i]n the meantime, we&#8217;ve decided  to revert to the old Terms as we work to address this.&#8221;<\/p>\n<p> EPIC and  other privacy groups rightly heralded this as a victory for Facebook  members. But let&#8217;s imagine that Facebook  hadn&#8217;t backed down. Could it have prevailed in defending the new Terms of  Service? <\/p>\n<p><strong>Would the New Terms of Service Have  Been Enforceable? Not Without Direct Notice to Customers, According to a Ninth  Circuit Decision<\/strong><\/p>\n<p> Facebook  backed down in the face of opposition.  But was the change to their terms of service enforceable? The answer is likely no. Facebook did not provide true notice to its  members of the changes it had made. And  in 2007, the U.S. Court of Appeals for the Ninth Circuit in <a href=\"https:\/\/caselaw.findlaw.com\/court\/us-9th-circuit\/\" rel=\"noopener\"><em>Douglas v. Talk America Inc.<\/em><\/a>,  held that a company could not unilaterally change its contract with customers  by posting the new terms on its website.<\/p>\n<p> In that case, former AOL subscribers  brought a class action against Talk America (a company acquired by AOL) on the  ground that it had attempted to change its Terms of Service simply by posting a  revised contract on its website, without any further notice to customers. The  revised contract purported to add certain service charges, waive users&#8217; right  to bring class actions, and add an arbitration clause and a New York choice-of-law  provision. The case appears to have been  the first of its kind. The Ninth Circuit  concluded that the revised Terms of Service was not a binding modification or  new contract \u2013 defined by the classic requirements of offer, acceptance and  consideration. Instead, it was merely an  offer, which would not be binding until and unless users accepted it. <\/p>\n<p> The Ninth Circuit also made clear  that users did not accept the offer simply by continuing to use the  service. In addition, it noted the  problem with the practice of simply posting new Terms of Service without  directly notifying users, explaining that a party would not &#8220;know when to check  the website for possible changes to the contract terms without being notified  that the contract has been changed and how.&#8221;  In addition, the Court noted that it would be cumbersome for users to  have to check the site daily for possible changes to the Terms of Service  contract, comparing every word of it with the version that had been posted the  day before. Finally, while the reported decision did not state whether the original contract permitted  posting of changes online, under the Ninth Circuit&#8217;s logic it seems very  unlikely that such a provision would moot the need for direct notice to  customers. <\/p>\n<p><strong>If Facebook Had Simply Given Users  Direct Notice of the Changes to Its Terms of Service, Would The Change Then  Have Been Legal? <\/strong><\/p>\n<p> Now, let&#8217;s  suppose \u2013 contrary to fact \u2013 that Facebook had given users direct notice of the  change to its Terms of Service, rather than merely posting them on its  blog. Would that solve the company&#8217;s  legal problems? Not necessarily, for a  deceptive trade practices issue would still remain. <\/p>\n<p>As EPIC argued, Facebook has induced  people to subscribe and participate because of its privacy practices and its  original Terms of Services &#8212; which seemed to say that once you delete your  material, Facebook relinquishes any right to use it, aside from archiving  it. A court, or the FTC, might deem it  unfair or deceptive for Facebook to change the rules of the game after enticing  consumers to be free with what they posted on their Facebook pages.<\/p>\n<p> But what  if, in addition to providing users with direct notice of the change in the  Terms of Service, Facebook had also offered customers the chance to unsubscribe  and thus have their information kept confidential? Or, what if users received  direct notice and Facebook&#8217;s new Terms of Service had explicitly <u>not <\/u>applied  to existing information, but only to future information? In that case, the Terms of Service might pass  muster, for users could no longer claim a bait-and-switch as to old material,  and it seems unreasonable to ask a company never to change its Terms of Service  in a prospective \u2013 as opposed to retrospective \u2013 way. <\/p>\n<p><strong>The Need for Notice to Users Is Also  Underlined By the FTC&#8217;s Gateway Case<\/strong><\/p>\n<p>  As noted above, EPIC had planned to  file a complaint challenging Facebook&#8217;s actions with the FTC &#8212; which already  requires that users must be given notice, and must accept companies&#8217; material  changes to their privacy policies. For  example, in the case <em>In re Gateway Learning Corp.<\/em>,  filed in 2003, the FTC charged that Gateway engaged in an illegal &#8220;unfair and  deceptive practice&#8221; when it materially changed its privacy policy and attempted  to apply it retroactively to data it had previously collected from  consumers. Gateway had not provided its  customers with notice of the changes. This was the first FTC case of this  nature. <\/p>\n<p> More specifically, the FTC alleged  that Gateway Learning (the sellers of &#8220;Hooked on Phonics&#8221;) had violated federal  law when it rented out its customers&#8217; personal information to marketers,  despite explicit promises made in its privacy policy. The FTC claimed that, after collecting  consumers&#8217; information, Gateway Learning altered its privacy policy to allow it  to share the information with third parties without notifying consumers or  getting their prior consent. This seems  like the same kind of bait-and-switch argument we saw above with the Talk America\/AOL  case, and arguably with the Facebook situation. <\/p>\n<p> According to the  FTC, since 2000, Gateway Learning&#8217;s online privacy policy had stated, &#8220;We do  not sell, rent or loan any personally identifiable information regarding our  consumers with any third party unless we receive customer&#8217;s explicit  consent.&#8221; <\/p>\n<p>  However, the FTC alleged that, despite  these promises, Gateway Learning started renting out its customers&#8217; data &#8212;  including their names, addresses, phone numbers, and even the age ranges and  gender of their children. The marketers  who received such data would use it to send targeted mailings and telemarketing  calls. <\/p>\n<p> In June 2003,  Gateway Learning revised its online privacy policy for its Hooked on Phonics  website to say that &#8220;from time to time&#8221; Gateway Learning would provide  consumers&#8217; personal information to &#8220;reputable companies&#8221; whose products or  services consumers might find of interest, the FTC complaint alleged. However,  according to the FTC, Gateway Learning continued to also rent out data  collected under the earlier policy, and failed to contact consumers who had  already provided their information to give them notice of the new privacy  policy. Nor did Gateway highlight on its  website the fact that the privacy policy had changed. <\/p>\n<p> Ultimately, the FTC&#8217;s settlement  barred Gateway from making deceptive claims about how it would use consumers&#8217;  information, and from applying material changes in its privacy policy  retroactively, without consumers&#8217; consent. <\/p>\n<p><strong>The Lesson for Facebook and Other  Companies: Don&#8217;t Use the Bait-and-Switch  Regarding Past Data, and Give Users Direct Notice of Terms of Service Changes<\/strong><\/p>\n<p>  The Gateway settlement seems directly  relevant to the Facebook dispute \u2013 raising the same kind of issues of privacy,  notice, retroactivity and the bait-and-switch. Among the lessons Facebook should take away  from the controversyis that its members do not like to lose control of their  information for good; they want clear, direct notice if changes are made; and  they do not want information that Facebook promised to protect to be suddenly  stripped of protection. 130,000  concerned members have registered their displeasure and the number is  growing. Facebook needs to re-earn its  users&#8217; trust \u2013 for both legal and loyalty reasons.<\/p>\n<!-- BEGIN AUTHORS FOOTNOTE -->\n\n<hr size=\"1\"><br>\n<p class=\"authorfoot\">\n<a name=\"bio\"><\/a>Anita Ramasastry, a FindLaw columnist, is the D. Wayne and Anne Gittinger Professor of Law at the University of Washington School of Law in Seattle and a Director of the Shidler Center for Law, Commerce &amp; Technology. She has previously written on business law, cyberlaw, computer data security issues, and other legal issues for this site, which contains an <a href=\"\/legal-commentary\/anita-ramasastry-archive\/\">archive of her columns<\/a>.<\/p>\n\n\n\n\n\n <\/div>\n<div class=\"was-this-helpful\">\n    <div\n            class=\"was-this-helpful__question-container\"\n            aria-labelledby=\"was-this-helpful__question\"\n            role=\"group\"\n    >\n        <span\n                id=\"was-this-helpful__question\"\n                class=\"was-this-helpful__question fl-text-lg-bold\"\n        >Was this helpful?<\/span>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"Yes\"\n                value=\"yes\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">Yes<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-up\" clip-path=\"url(#clip0_604_3418)\">\n                        <path id=\"Vector\"\n                              d=\"M6 21H3C2.46957 21 1.96086 20.7893 1.58579 20.4142C1.21071 20.0391 1 19.5304 1 19V12C1 11.4696 1.21071 10.9609 1.58579 10.5858C1.96086 10.2107 2.46957 10 3 10H6M13 8V4C13 3.20435 12.6839 2.44129 12.1213 1.87868C11.5587 1.31607 10.7956 1 10 1L6 10V21H17.28C17.7623 21.0055 18.2304 20.8364 18.5979 20.524C18.9654 20.2116 19.2077 19.7769 19.28 19.3L20.66 10.3C20.7035 10.0134 20.6842 9.72068 20.6033 9.44225C20.5225 9.16382 20.3821 8.90629 20.1919 8.68751C20.0016 8.46873 19.7661 8.29393 19.5016 8.17522C19.2371 8.0565 18.9499 7.99672 18.66 8H13Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\"\n                              stroke-linejoin=\"round\"><\/path>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3418\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"><\/rect>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"No\"\n                value=\"no\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">No<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-down\" clip-path=\"url(#clip0_604_3423)\">\n                        <path id=\"Vector\"\n                              d=\"M16 0.999995H18.67C19.236 0.989986 19.7859 1.18813 20.2154 1.55681C20.645 1.9255 20.9242 2.43905 21 3V10C20.9242 10.5609 20.645 11.0745 20.2154 11.4432C19.7859 11.8119 19.236 12.01 18.67 12H16M9.00003 14V18C9.00003 18.7956 9.3161 19.5587 9.87871 20.1213C10.4413 20.6839 11.2044 21 12 21L16 12V0.999995H4.72003C4.2377 0.994543 3.76965 1.16359 3.40212 1.47599C3.0346 1.78839 2.79235 2.22309 2.72003 2.7L1.34003 11.7C1.29652 11.9866 1.31586 12.2793 1.39669 12.5577C1.47753 12.8362 1.61793 13.0937 1.80817 13.3125C1.99842 13.5313 2.23395 13.7061 2.49846 13.8248C2.76297 13.9435 3.05012 14.0033 3.34003 14H9.00003Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3423\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"\/>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n    <\/div>\n    <span class=\"was-this-helpful__taken-action fl-text-sm-bold\"><\/span>\n    <div class=\"was-this-helpful__feedback-container\">\n        <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n            <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n        <\/div>\n        <form class=\"was-this-helpful__feedback-form\">\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--positive\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this helpful?<\/legend>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--understandable\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Easy to understand\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--understandable\"\n                        >Easy to understand<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--solved-problem\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Solved my problem\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--solved-problem\"\n                        >Solved my problem<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--negative\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this not helpful?<\/legend>\n                    <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n                        <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--missing-info\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Missing Information\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--missing-info\"\n                        >Missing the information I need<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--complicated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Too complicated\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--complicated\"\n                        >Too complicated \/ too many steps<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--dated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Out of date\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--dated\"\n                        >Out of date<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--negative-other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--negative-other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__form-buttons-container\">\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--positive at-feedback-submit fl-button secondary\"\n                    type=\"submit\"\n                >\n                    <span class=\"fl-button-content\">Submit<\/span>\n                    <i\n                        class=\"fa fa-angle-right medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--cancel fl-button primary disabled\"\n                    type=\"reset\"\n                >\n                    <span class=\"fl-button-content\">Cancel<\/span>\n                    <i\n                        class=\"fa fa-times-circle medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n            <\/div>\n        <\/form>\n    <\/div>\n    <div class=\"was-this-helpful__thank-you-message\" role=\"status\">\n        <i class=\"was-this-helpful__thank-you-message-icon fa fa-check\"><\/i>\n        <p class=\"was-this-helpful__thank-you-message-text\" aria-live=\"polite\"><\/p>\n    <\/div>\n<\/div>\n\n\n    <\/div>\n    \n    <div class=\"fl-block-column fl-section-sidebar\">\n        \n    <\/div>\n<\/div>","protected":false},"parent":49876,"menu_order":0,"template":"app\/Http\/Controllers\/Templates\/ArticlePageController.php","meta":{"_acf_changed":false,"_stopmodifiedupdate":false,"_modified_date":"","_cloudinary_featured_overwrite":false},"class_list":["post-51868","supreme","type-supreme","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/51868","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme"}],"about":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/types\/supreme"}],"up":[{"embeddable":true,"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/49876"}],"wp:attachment":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/media?parent=51868"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}