{"id":98200,"date":"2023-05-10T09:55:54","date_gmt":"2023-05-10T13:55:54","guid":{"rendered":"https:\/\/cdt.org\/?post_type=insight&p=98200"},"modified":"2023-05-25T11:49:26","modified_gmt":"2023-05-25T15:49:26","slug":"momentum-builds-against-abortion-surveillance-as-new-states-enact-shield-laws","status":"publish","type":"insight","link":"https:\/\/cdt.org\/insights\/momentum-builds-against-abortion-surveillance-as-new-states-enact-shield-laws\/","title":{"rendered":"Momentum Builds Against Abortion Surveillance as New States Enact Shield Laws"},"content":{"rendered":"\n

Washington and New York states recently became the second and third places respectively to enact shield laws<\/em> that seek to prevent in-state companies from complying with out-of-state warrants in connection with abortion investigations. These laws follow the model set by California last year when it passed the nation\u2019s first shield law<\/a> focused on blocking data demands for abortion investigations. While many pro-choice states have enacted laws to protect reproductive health activities in their state (and guard data indicating such activities in-state), these shield laws are unique in protecting communications and data that focus entirely on out-of-state activities.<\/p>\n\n\n\n

The growth of shield laws is an important trend that will help individuals throughout the country minimize the risk of their communications and data being seized to investigate and prosecute reproductive health choices. However, the breadth and effectiveness of these laws\u2019 protections depend significantly on the details of the text.<\/p>\n\n\n\n

Washington\u2019s Shield Law:<\/em><\/strong><\/p>\n\n\n\n

The Washington shield law, HB 1469<\/a>, was enacted on April 27. The law is a significant measure for reproductive rights and data protection, as some of the nation\u2019s largest electronic communications services\u2014notably Microsoft and Amazon\u2014are based in Washington. While largely similar to California\u2019s shield law, HB 1469 also makes several improvements to it.<\/p>\n\n\n\n

Overall, the law prohibits certain Washington companies from complying with legal process demanding records or assistance, if that legal process stems from an investigation or prosecution of \u201cprotected health care services.” The law defines protected health care services to cover any reproductive health care services as well as <\/em>gender-affirming treatments that are legal in Washington state. This is one area where the Washington law provides stronger protections than the California law that preceded it: California\u2019s law does not protect gender-affirming care.<\/p>\n\n\n\n

Specifically, HB 1469 applies to companies that provide electronic communication services (\u201cECS\u201d) that are incorporated or have their principal place of business in Washington. Section 13(d)(i)(A) of the law bars these companies from providing \u201crecords, information, facilities, or assistance\u201d in response to any \u201csubpoena, warrant, court order, or other civil or criminal legal process\u201d that relates to protected health care services.  This language is different from the California law in an important respect: While the California law refers to \u201crecords, information, facilities, or assistance\u201d in California<\/em>, the Washington law makes no distinction on where this aid is located, meaning its protections apply even if data is stored and assistance is provided out of state, so long as the company is incorporated or based in Washington. <\/p>\n\n\n\n

In addition to the strict prohibition for ESC companies, the Washington law also offers a less powerful shield for a broader set of entities. Section 12 of the law states that any \u201cWashington recipient \u2026 shall not be required to comply\u201d with court orders being used to investigate or prosecute protected health care services. The text of this provision appears to broadly apply to all<\/em> Washington-based companies and individuals. And while it does not outright prohibit compliance as Section 13 does for ECS companies, it provides an option for doing so. This is a novel feature: the California shield law offers no comparable option for non-ECS entities to refuse legal process related to abortion investigations. <\/p>\n\n\n\n

Because this provision applies to all Washington entities, not enacting a hard prohibition and penalties could provide leeway to small businesses that might not have the legal resources to track HB 1469 and build in compliance measures (as large companies like Microsoft do). At the same time, because this rule gives Washington entities an option rather than strictly prohibiting compliance, the impact of this measure is less certain, and it is also less likely to succeed in a conflict of laws dispute with the state issuing the legal process, as potential penalties from a state that blocks compliance can serve as a reason for following that state\u2019s law. Going forward, Washington may wish to strengthen the impact of HB 1469 by moving other important categories of companies\u2014such as those that maintain health, medical, and financial records\u2014into the strict prohibition category that Section 13 provides.<\/p>\n\n\n\n

Much like California, Washington\u2019s shield law relies on an attestation rule. Sec 13(d)(i)(B) provides that ECS companies can comply with legal process only if it includes an attestation that the demand \u201cdoes not seek documents, information, or testimony\u201d that is being used to create criminal or civil liability for protected health care services. The fact that this attestation rule is centered on whether protected health care services are impacted in general, rather than focusing on whether the crime being investigated explicitly bars reproductive health services or gender-affirming care, is critical. Facially neutral laws, such as child endangerment, are often used to prosecute reproductive health and gender-affirming activities. <\/p>\n\n\n\n

HB 1469\u2019s attestation requirement also includes another important improvement over the California shield law: The attestation must be made \u201cunder penalty of perjury,\u201d with \u201ca statutory penalty of $10,000 per violation.\u201d This requirement should deter out-of-state law enforcement and prosecutors from circumventing the shield law by lying in attestations. Even if these actors were not concerned with the $10,000 fine and potential prosecution in Washington, any information obtained from a demand built on a false attestation would be the fruits of a criminal action, giving defendants a strong legal claim to suppress evidence. California should consider adding this type of penalty of perjury rule as well.<\/p>\n\n\n\n

The Washington law empowers the state attorney general to pursue legal action to \u201cenjoin any person from violating any provision\u201d (Section 16). However, the law is silent as to what\u2014if any\u2014penalties a company could face for violations of the law. Clearly defined and stringent penalties would strengthen Washington\u2019s hand in any future conflict-of-laws dispute over HB 1469.<\/p>\n\n\n\n

HB 1469 also restricts Washington courts from domesticating out-of-state legal demands. Section 11 of the law states that \u201cthe issuance of criminal process is prohibited if such process is related to criminal liability\u201d for protected health care services. This provision effectively bars Washington judicial officers from domesticating any warrants, subpoenas, or other legal demands that relate to investigating or prosecuting protected health care services. <\/p>\n\n\n\n

While this domestication restriction is unlikely to be important to companies like Microsoft and Amazon with a nationwide presence\u2014as they can be served directly in states enforcing abortion bans\u2014it could prove immensely beneficial to smaller companies. Because HB 1469 restricts domestication of legal process, companies whose offices and employees are exclusively in Washington state will be shielded from even being lawfully served with a warrant or subpoena for investigations related to protected health care services. Therefore, even if a large company refusing to comply with a warrant based on HB 1469 was eventually forced to do so after conflict-of-laws litigation, these smaller, Washington-state-exclusive companies could still be shielded.<\/p>\n\n\n\n

New York\u2019s Shield Law:<\/em><\/strong><\/p>\n\n\n\n

New York also enacted a shield law by adding a new provision, Section 394-f, to New York\u2019s general business law as part of a state budget bill<\/a> that passed on May 2. While this shield law\u2019s protections are unfortunately far less comprehensive than either the California or Washington laws, it nonetheless represents a positive step.<\/p>\n\n\n\n

Like the other states\u2019 shield laws, Section 394-f generally prohibits companies incorporated or headquartered in New York that provide ECS services from complying with legal demands related to a \u201cprohibited violation.\u201d That term encompasses any criminal or civil offense that restricts reproductive health care activities (this follows the same model as California, but does not additionally protect gender-affirming care as Washington\u2019s law does). And like the Washington law, Sec. 394-f empowers the state attorney general to compel compliance with the shield law, but is silent as to whether companies may face penalties for incidents of noncompliance. <\/p>\n\n\n\n

Sec. 394-f falls short of its peer shield laws in two major areas. First, while the California law applies to various types of legal process, and the Washington law applies to virtually all forms of criminal and civil legal process, the New York law only restricts compliance with warrants. This means that an array of sensitive data\u2014such as communications metadata and transaction records\u2014are unprotected from being seized with a subpoena or other types of demands.<\/p>\n\n\n\n

Another key area where the New York shield law falls short is in the absence of an attestation requirement. Sec. 394-f prohibits New York-based ESC companies from complying with warrants when the company \u201cknows<\/em> that the warrant relates to\u201d a prohibited violation (emphasis added). With other shield laws, by forcing legal demands to be accompanied by an attestation, companies would have a clear idea whether the demand relates to reproductive health care activities. However, Sec. 394-f does not include an attestation requirement. It merely states that \u201cif the warrant is accompanied by an attestation,\u201d companies are permitted to comply with it.<\/p>\n\n\n\n

This creates significant loopholes. ESC companies could take a \u201csee no evil, hear no evil\u201d approach, and request no clarifying information or attestation when they receive an out-of-state warrant. In the absence of such information, the company could make a strong argument that they are in compliance with Sec. 394-f, because they do not know<\/em> that any given warrant is being used for an abortion-related investigation. Further, even if companies wish to avail themselves of the shield law and request attestations with warrants, out-of-state prosecutors might simply refuse, and argue that since Sec. 394-f doesn\u2019t make compliance with warrants contingent on receiving an attestation, the company is legally obligated to obey the warrant even if they don\u2019t receive any information about whether the investigation relates to abortion.<\/p>\n\n\n\n

Earlier this year, New York Assemblymember Linda Rosenthal introduced a bill<\/a> that would have been a more effective shield law, notably by requiring that companies only comply with warrants that include an attestation that the investigation does not relate to a prohibited violation. The NY legislature should amend Sec. 394-f to include this requirement and also follow the Washington state model of building a penalty of perjury for lying in attestations. The legislature should also broaden its shield law to apply to all<\/em> legal process for criminal and civil procedures that relate to a prohibited violation, as well as broaden the definition of prohibited violation to also protect gender-affirming care.<\/p>\n","protected":false},"featured_media":86100,"template":"","content_type":[7251],"area-of-focus":[806,816,78,10215,799],"acf":[],"_links":{"self":[{"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/insight\/98200"}],"collection":[{"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/insight"}],"about":[{"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/types\/insight"}],"version-history":[{"count":7,"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/insight\/98200\/revisions"}],"predecessor-version":[{"id":98208,"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/insight\/98200\/revisions\/98208"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/media\/86100"}],"wp:attachment":[{"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/media?parent=98200"}],"wp:term":[{"taxonomy":"content_type","embeddable":true,"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/content_type?post=98200"},{"taxonomy":"area-of-focus","embeddable":true,"href":"https:\/\/cdt.org\/wp-json\/wp\/v2\/area-of-focus?post=98200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}