Publicly Available Information Is Not “Identifying Information” Under S.C. Code § 24-3-580; Only the Initial Breach of Confidentiality Can Trigger Liability
I. Introduction
In ACLU v. Wilson (S.C. Sup. Ct. Sept. 2, 2026), the Supreme Court of South Carolina answered two certified questions from the
United States District Court for the District of South Carolina concerning the scope of South Carolina’s execution-secrecy statute,
S.C. Code Ann. § 24-3-580 (2025).
The plaintiff, the American Civil Liberties Union of South Carolina Foundation, challenged the breadth of statutory provisions that impose
civil liability and criminal penalties for the knowing disclosure of “identifying information” about current or former members of an
execution team. The defendants were Alan Wilson (Attorney General) and Joel Anderson (Interim Director of the South Carolina Department
of Corrections), with Henry McMaster (Governor) intervening.
The core issues were interpretive: whether information that is already publicly available can still qualify as protected “identifying information,” and whether
repeating such information can constitute a prohibited “knowing[] disclos[ure]” under the statute.
II. Summary of the Opinion
The court answered both certified questions “No.”
-
Question (1): Publicly available or nonconfidential information is not “identifying information” under
§ 24-3-580(A)(2).
-
Question (2): A person cannot “knowingly disclose” publicly available or nonconfidential information under
§ 24-3-580(C).
Central to the holding is the court’s textual conclusion that the statute covers information that “reveals” identifying data—i.e., information that
was secret, hidden, or otherwise not publicly accessible prior to the alleged disclosure. Once identifying details enter the public domain,
they cease to be “identifying information” for purposes of § 24-3-580.
III. Analysis
A. Precedents Cited
Although the opinion primarily applies textual interpretation, it anchors its method in several South Carolina decisions and well-known interpretive authorities:
1. Smith v. Tiffany, 419 S.C. 548, 555-56, 799 S.E.2d 479, 483 (2017)
The court relied on Smith v. Tiffany for the baseline principle of statutory interpretation: if statutory language is “clear and plain,” courts do not look
beyond the text “to divine its meaning.” This served as the gateway to a strictly textual analysis of § 24-3-580(A)(2) and (C), resisting broader policy-based
expansions of criminal and civil liability.
2. In re Manigo, 398 S.C. 149, 157, 728 S.E.2d 32, 36 (2012)
In re Manigo supplied the contextual constraint: statutory words must be construed “in context” and “in harmony with [the statute’s] subject matter.”
The court used this to read “identifying information” alongside the statute’s repeated emphasis on “confidential[ity]” and its stated legislative objective to ensure
“absolute confidentiality.”
3. Adkins v. Varn, 312 S.C. 188, 191, 439 S.E.2d 822, 824 (1993)
The court invoked Adkins v. Varn for the “plain and ordinary meaning” rule and the admonition against “subtle or forced construction which limits or expands
the statute’s operation.” That citation is pivotal because the State’s broader reading would effectively expand the statute to punish republication of lawfully public facts—an
outcome the court declined to reach absent unmistakable textual direction.
4. Interpretive Authorities: Henry J. Friendly; Scalia & Garner
The opinion echoes Judge Friendly’s maxim—“(1) Read the statute; (2) read the statute; (3) read the statute!” (Henry J. Friendly, Benchmarks 202 (1967))—to
emphasize disciplined focus on enacted text. It also cites Antonin Scalia & Bryan A. Garner, Reading Law: The Interpretation of Legal Texts 56 (2012) for the
proposition that meaning is derived from context and purpose. These authorities reinforced a method: textual meaning first, then context/purpose to confirm—not rewrite—the text.
5. Statutory Parallels: § 44-117-360 and § 60-4-10
The court drew interpretive support from the General Assembly’s usage of “reveal” in confidentiality regimes outside the death-penalty context:
-
S.C. Code Ann. § 44-117-360 (2018) (Prescription Information Privacy Act; “Improper revealing of confidential information”).
-
S.C. Code Ann. § 60-4-10 (2022) (library patron records; records that “would reveal the identity” are “confidential information” and may not be “disclosed”
except in limited circumstances).
These parallels mattered because they show legislative consistency: “reveal” is used to describe making confidential information known, not the repetition of
information already in the public domain.
B. Legal Reasoning
1. The “reveals” requirement narrows “identifying information” to nonpublic facts
The statutory definition in § 24-3-580(A)(2) lists many data types (name, date of birth, contact information, addresses, etc.), but the court focused on the
grammatical hinge: “any record or information that reveals” such data. The court emphasized that the statute does not define “identifying information”
as any record that merely “includes” such data; instead, it requires a record that reveals it.
Applying ordinary meaning (including dictionary definitions), the court concluded “reveal” means making something “secret or hidden” publicly known. From that, it drew the
key implication: one cannot “reveal” what is already public. Therefore, information that is publicly available or otherwise nonconfidential cannot be “identifying information” under
the statute.
2. “Disclose” in subsections (C) and (G) reinforces a confidentiality-only reading
The court observed that the statute itself uses “disclose” as a near-synonym for “reveal,” including in the enforcement subsection,
§ 24-3-580(C), and the government non-disclosure mandate,
§ 24-3-580(G). “Disclose” likewise connotes making known something previously kept secret. The pairing of “reveal” and “disclose” across the statute
supported the same limiting principle: the statute is triggered by exposing confidential identity information, not by repeating public facts.
3. Express legislative intent to ensure “absolute confidentiality” confirms the text’s focus
The court treated § 24-3-580(I)—directing broad construction to ensure “absolute confidentiality”—as a confirmation of what the operative words already require:
that the protected category is information that is, in fact, confidential. The opinion also relied on the statutory title (“Execution team and drugs used to administer death sentence confidential”),
§ 24-3-580(B) (declaring identifying information “confidential” and not subject to compulsory process), and 2023 S.C. Acts No. 16, § 1
(stressing “absolute confidentiality”).
Notably, the court used “broad construction” not to enlarge liability to cover public information, but to fortify the conclusion that the legislature was legislating about
confidentiality—i.e., keeping the protected set of information from becoming public in the first instance.
4. Liability concentrates on the first public disclosure
Answering the second certified question, the court reasoned that because publicly available information is no longer confidential, it no longer fits the statute’s definition of “identifying information.”
As a result, “it would appear only the first person to publicly disclose ‘identifying information’—i.e., the source of the disclosure or revelation—can violate subsection 24-3-580(C).”
This “first disclosure” logic significantly narrows exposure under § 24-3-580(C) for downstream speakers (e.g., journalists, advocacy groups, researchers, or members of the public) who
repeat information already in the public domain.
C. Impact
1. Reduced chilling effect for republication of public information
By excluding publicly available information from “identifying information,” the decision limits the statute’s ability to impose criminal/civil consequences on those who
share or comment on information already accessible to the public. This is particularly consequential in contexts where the statute might otherwise deter reporting,
advocacy, or litigation-related investigation through fear of downstream liability.
2. Litigation and enforcement will shift to disputes over “publicly available” and “confidential” status
Future cases will likely turn on evidentiary questions such as:
- What counts as “publicly available” (e.g., posted online, in court filings, in public records, on social media, in news archives)?
- Whether a purported “public” disclosure was meaningfully accessible to the general public or was technically available but practically obscure.
- Whether information was made public unlawfully or inadvertently—and whether that affects its “confidential” character for purposes of § 24-3-580.
3. Increased focus on source identification and leak prevention
The court’s “only the first person” framing may incentivize the State to:
- Concentrate enforcement on identifying the originator of the leak.
- Strengthen internal controls within SCDC and associated entities to prevent initial disclosure.
- Rely more heavily on administrative, employment, or contractual mechanisms to deter and punish insiders who disseminate confidential information.
4. Interaction with FOIA and compulsory process
The opinion did not directly adjudicate Freedom of Information Act access or discovery disputes, but its reading aligns with the statute’s premise that
government entities may not “disclose” the confidential category. If the information is already public, however, the decision implies the statutory secrecy
mechanism cannot be used to penalize a requester, recipient, or republisher for merely repeating public facts—though it does not necessarily compel agencies
to produce such information if other provisions apply.
IV. Complex Concepts Simplified
- Certified questions
-
A procedure where a federal court asks a state supreme court to definitively interpret state law. The state court answers only the legal questions posed,
which then guides the federal court’s handling of the case.
- “Identifying information” (as used here)
-
Not every fact that could identify someone, but a “record or information that reveals” specified identifiers. The court reads “reveals” to mean
exposing something not already public.
- Plain meaning / ordinary meaning
-
A core interpretive rule: if statutory language is clear, courts apply its ordinary meaning without rewriting it based on policy preferences.
- Confidential vs. public domain
-
“Confidential” information is restricted/secret. Once information becomes publicly available, it generally loses its confidential character for purposes of
statutes designed to prevent initial exposure.
- “Only the first person” liable (practical effect)
-
The statute targets the initial disclosure that makes confidential information public; repeating already-public information does not qualify as disclosing
“identifying information” under the court’s reading.
V. Conclusion
ACLU v. Wilson establishes a clear narrowing construction of § 24-3-580: the statute protects confidentiality, not identity per se.
Publicly available or nonconfidential information is not “identifying information,” and repeating such information cannot constitute a prohibited “knowing[] disclos[ure].”
The decision concentrates statutory liability on the moment confidential execution-team identifying details are first made public, shaping future enforcement and litigation around
the boundary between confidential information and the public domain.