A. Precedents Cited
1. Paff v. Galloway Township (the “email log” foundation)
Paff v. Galloway Township, 229 N.J. 340 (2017), supplied the Court’s central conceptual move:
OPRA covers not only the “email contents” but also certain fields of electronically stored information—a log
showing items like sender, recipient, date, and subject. The Court in Galloway treated this as disclosure of existing government records,
not the unlawful “creation” of a new record, so long as the agency has the means to extract the information.
In Rosetti, the Court relied on Galloway for two propositions:
- “Information” stored electronically qualifies as a “record” under N.J.S.A. 47:1A-1.1.
- An “email log” can be a permissible “reconfiguration” of existing electronic information, not an impermissible new record.
But Rosetti also clarified Galloway’s limits. Galloway concerned an electronically generated log from data accessible on a government server.
Here, the Court refused to treat “Galloway-type” server-metadata extraction as the only valid species of log, and it refused to let the concept balloon into
disclosure of entire personal-account logs.
2. Simmons v. Mercado (location/control is not dispositive)
Simmons v. Mercado, 247 N.J. 24 (2021), was crucial to answering the Board’s “not on our server / not in our control” argument.
There, complaint-summonses created by police were stored on Judiciary servers; the Court held OPRA disclosure obligations can follow from the fact that
the agency made the records in the course of official business, regardless of where they are maintained.
Rosetti extended that logic to personal email: an official cannot defeat OPRA simply by placing government-business communications (and thus the information needed to
log them) on a private platform.
3. Burnett v. County of Gloucester (Appellate Division’s “made by officials” emphasis)
The Appellate Division relied on Burnett v. County of Gloucester, 415 N.J. Super. 506 (App. Div. 2010), for the idea that records may be “government records”
even when held by third parties. The Supreme Court did not reject that general principle, but it narrowed the Appellate Division’s broad framing:
the relevant “record” is the government-related subset, not the entire personal-account log.
4. Wilson v. Brown (personal accounts can contain government records)
Wilson v. Brown, 404 N.J. Super. 557 (App. Div. 2009), supported the Court’s statement that OPRA’s reach includes communications on personal devices and
in personal accounts when they involve government business (even though particular privileges or exemptions may still apply).
Rosetti leaned on this to reinforce that the “personal account” label is not a transparency safe harbor.
5. Transparency interpretive backdrop: OPRA construed in favor of access
The Court situated its approach in OPRA’s pro-access interpretive tradition, citing:
- Educ. L. Ctr. v. Dep't of Educ., 198 N.J. 274 (2009) (New Jersey’s tradition of openness).
- N. Jersey Newspapers Co. v. Passaic Cnty. Bd. of Chosen Freeholders, 127 N.J. 9 (1992) (hostility to secrecy).
- Mason v. City of Hoboken, 196 N.J. 51 (2008) (OPRA’s purpose: maximize public knowledge).
- Asbury Park Press v. Ocean Cnty. Prosecutor's Off., 374 N.J. Super. 312 (Law Div. 2004) (same theme, quoted in Mason).
- ACLU of N.J. v. Cnty. Prosecutors Ass'n of N.J., 257 N.J. 87 (2024) and In re N.J. Firemen's Ass'n Obligation, 230 N.J. 258 (2017) (OPRA promotes transparency).
These cases did not supply the mechanical rule for “personal email logs,” but they informed the Court’s insistence that OPRA not be interpreted in a way that would
incentivize off-platform decision-making to evade scrutiny.
6. Burden/exemptions framework: Gilleran v. Township of Bloomfield and OPRA’s burden allocation
Citing Gilleran v. Township of Bloomfield, 227 N.J. 159 (2016), the Court reiterated that agencies bear the burden to justify withholding by proving an exemption.
Although Rosetti is not primarily an “exemption” case, the burden principle matters because it frames the agency’s obligation to do more than make conclusory
assertions that production is difficult or intrusive.
7. Search-certification expectations: Paff v. Department of Labor
The Appellate Division referenced Paff v. Department of Labor, 392 N.J. Super. 334 (App. Div. 2007), to require “persuasive” certifications if a request is claimed to be
unavailable or overly burdensome. The Supreme Court adopted a related mechanism: after searching personal accounts and producing the government-related log(s),
officials must supply a certification describing the search so courts can evaluate adequacy.
8. Persuasive out-of-state analogues: City of San Jose v. Superior Ct. and Toensing v. Attorney General of Vermont
The Court cited:
-
City of San Jose v. Superior Ct., 389 P.3d 848 (Cal. 2017), for the practical solution that agencies can reasonably rely on employees to search their own personal accounts,
with case-by-case review/redaction balancing privacy and access.
-
Toensing v. Attorney General of Vermont, 178 A.3d 1000 (Vt. 2017), for the principle that public-records laws would be undermined if officials could shield public records
by using private accounts.
These cases reinforced the Court’s direction toward an employee-driven search model paired with redaction and certification, rather than a categorical rule
immunizing personal-account metadata from OPRA.
B. Legal Reasoning
1. The statutory anchor: “information stored or maintained electronically”
The Court’s reasoning begins with OPRA’s definition of “government record” in N.J.S.A. 47:1A-1.1, which expressly includes
“information stored or maintained electronically” made/kept/received in the course of official business.
Because emails related to Board business meet that definition even if located in personal accounts, OPRA’s coverage cannot turn solely on
the server’s ownership.
2. “Email logs” are not categorically different from “emails” for OPRA purposes
The Board argued that a log is a distinct, metadata-driven “report” and not the same as an email.
The Court accepted that some logs (like a “Galloway-type” server-metadata extraction) are technically complex and may not be feasible on private platforms
under the Board’s IT control. But it rejected the conclusion that this technical distinction eliminates OPRA access to log-format information
about government-business emails in personal accounts.
Critically, the Court reframed the ask: the production obligation is for a log of government-related emails, and that log can be generated by
reasonable searching within personal accounts, not necessarily by server-level metadata tools.
3. The compliance mechanism: reasonable search + log + certification
The Court endorsed Rosetti’s concession that a log limited to Board-related emails (including those between Board members) would satisfy the request.
It then converted that practical concession into a legal standard:
- Officials must search personal accounts (including folders like sent/trash/other relevant folders) using reasonable methods to locate Board-related emails.
- Officials must produce a log (or logs) of the government-related emails located through that search.
- Officials must file certifications describing what was searched and how, enabling judicial review of adequacy.
- If unrelated private emails appear in the log output, they must be redacted.
This approach operationalizes OPRA’s pro-access purpose while giving courts a concrete tool—certifications—to police completeness and good faith.
4. The limiting principle: OPRA does not convert a whole personal inbox into a public record
The Court identified a serious overbreadth problem in Rosetti’s phrasing (“[e]mail log[s] of Board Members from their own personal email addresses”),
and in the Appellate Division’s broad language suggesting “private servers” logs are disclosable because some emails discuss Board business.
The Supreme Court drew the boundary:
It is only the log of government-related emails that is a government record.
The Court’s example—1,000 total private emails with only 10 government-related—illustrates the point:
even if private entries are redacted, a whole-account log is not itself a “government record” merely because it contains some public-business items.
OPRA access attaches to the government-business subset, not the entire personal-account universe surrounding it.
5. Forward-looking policy admonition: avoid personal accounts
The Court emphasized that using personal accounts does not shield government-business emails from OPRA and strongly advised agencies to steer officials and employees away
from conducting government business via private email—both to reduce litigation and to support lawful recordkeeping and transparency.
C. Impact
1. A new, practical OPRA compliance rule for personal-account communications
The decision establishes a workable statewide standard:
OPRA requesters may obtain logs of government-related emails even when those emails are housed in officials’ personal accounts,
and agencies may satisfy that obligation through reasonable official-conducted searches plus search certifications.
This is a meaningful doctrinal step beyond simply saying “the emails themselves are records,” because it recognizes the log as an access-enabling tool
that helps requesters identify and request specific communications.
2. Litigation will shift to “search adequacy” and “scope discipline”
By rejecting whole-account logs while mandating government-business-only logs, the Court likely redirects future disputes to:
- Scope negotiations: precisely defining “government-related” subject matter and time frames.
- Search adequacy: whether officials searched all relevant folders, terms, participants, and time periods.
- Certification sufficiency: whether certifications are detailed enough to permit judicial evaluation.
- Redaction disputes: whether non-government items were appropriately redacted, and whether withheld portions truly fall outside OPRA.
3. Incentives and governance: discouraging “off-platform” government work
The opinion reduces incentives for officials to move communications to private accounts to avoid visibility.
At the same time, it avoids a privacy-maximal intrusion (whole-account logs), which could have created strong resistance and collateral harms.
The net effect is to encourage agencies to implement (or tighten) policies requiring official business be conducted on government systems.
4. Broader relevance beyond email
Although the holding is framed in terms of “email logs,” the logic—government-business communications in personal accounts are reachable, and must be located via reasonable searches
and verified by certification—may influence OPRA disputes involving other platforms (messaging apps, cloud collaboration tools, personal devices) where “logs” or equivalent indices
are requested to map government communications.