New Jersey Saves City Facebook Posts You Still Can't Find

The useful object is not a mayor’s polished Facebook post. It is Cherry Hill Police Department’s Facebook block list, a record generated inside the page’s administrative controls and invisible to everyone outside them.

Rise Against Hate, an advocacy organization, requested that list from Cherry Hill Township under New Jersey’s Open Public Records Act, known as OPRA. The township argued, among other things, that Facebook maintained the information. The dispute reached the New Jersey Supreme Court, which treated the list as a government record because police administrators could access it and their decisions created its contents.

That finding matters beyond one police page. A block list is not displayed like a council agenda or budget. It sits behind a platform login, formatted according to a private company’s interface, until an employee exports it, copies it, or otherwise turns it into something a records custodian can produce. The public record exists.

Public access begins several steps later.

New Jersey municipalities now operate across Facebook, Instagram, X, YouTube and other services while their records systems remain organized around departments, custodians and requests. A review of public-facing records routes used by municipalities including Cherry Hill, Newark, Jersey City and Hoboken shows the recurring structure: residents get an OPRA form or portal, perhaps a request log, but not a citywide social-media archive that can be searched by account, date, deleted comment, direct message or moderation action.

The distinction sounds administrative. It determines who can reconstruct what a city said.

Retention answers the city’s question

Government retention rules tell an agency how long it must keep a record before authorized destruction. They do not require the agency to publish that record in a form residents can browse.

New Jersey’s records-management system classifies material according to the public business it documents, rather than granting every Facebook post one universal lifespan. A social post announcing a meeting may inherit the retention period of the meeting notice. A direct message reporting a broken traffic signal may become service correspondence. A message containing a complaint about an officer may belong with records governed by a different schedule and separate disclosure restrictions.

That approach is defensible as records management. The medium should not erase the function. It also means there is no clean shelf marked “municipal social media” where a resident can expect to find the complete account.

Cities can capture platform activity manually, through native account-download tools, or with commercial archiving software that records posts, edits, comments and messages. The software may preserve metadata, meaning information about a record such as its timestamp, account and edit history, which can establish what appeared and when. Vendors sell this capture as compliance infrastructure. Municipal departments or their technology contractors pay for it, while the public usually sees only the request form at the other end.

Retention therefore works for the institution first. It creates evidence for litigation, audits, internal investigations and records requests. A searchable public mirror, if one exists at all, is a separate product and a separate policy decision. The city can satisfy its preservation duties while making the preserved material difficult to discover.

The Cherry Hill block list exposes the gap neatly. Police administrators could reach it through Facebook’s controls. A resident could not know who appeared on it, when a name was added, which comment preceded the block, or whether an entry had later disappeared without first knowing that this concealed administrative record existed.

The request form is part of the barrier

OPRA does not turn a records custodian into a researcher. Requests must identify government records with enough specificity for the agency to locate them, and New Jersey’s amended records law gives custodians room to reject requests framed as open-ended research. Agencies may also impose a special service charge when a request requires an extraordinary expenditure of time or technology.

Those rules collide with platform design. A resident looking for a deleted comment may remember the issue but not the posting date. Someone who sent a direct message may know the account name but not which department controlled it at the time. A researcher examining moderation could need records from several pages because police, emergency management, recreation and the mayor may each operate separate accounts with separate administrators.

The portal asks for precision before the city has shown the catalog.

A conventional archive lets a user search broadly, inspect neighboring records and refine the inquiry. A request system reverses that sequence. The requester must describe the record before seeing the collection, then wait while the custodian interprets the description, asks a department to search, considers exemptions and prepares a production. If the result arrives as a flattened PDF or a stack of screenshots, text search may fail and relationships among a post, its comments and later moderation can disappear.

This is where nominal public access becomes a technical scavenger hunt. The burden falls hardest on residents investigating a pattern rather than chasing one known document: repeated deletion of criticism, changes to emergency guidance, private messages that moved a public complaint off the visible page, or blocks imposed across multiple municipal accounts.

The city knows its account inventory, administrator permissions, retention vendor and naming conventions. The requester usually knows none of them.

Platforms remain inside the records room

A municipality may own the public business conducted through an account, but Meta or another platform still controls the interface that stores and exposes much of the evidence. Administrative views change. Export formats change. Application programming interfaces, the connections that let archiving software collect platform data automatically, can be restricted or withdrawn.

This dependence creates two separate risks. The first is loss: a city that relies on the live platform may discover that deleted material, edits or message context cannot be reconstructed later. The second is opacity: even where an outside archive captured everything, residents may receive only the portion located by a search that they cannot inspect or reproduce.

Direct messages make the problem sharper. They can contain ordinary constituent service, sensitive personal details, threats, complaints or communications that belong in another official system. Some material will be exempt from release, and redaction may be necessary. None of that excuses a city from knowing which accounts receive messages, who monitors them, where the records are retained and how a custodian searches them.

A public archive would not mean dumping every inbox online. It would mean publishing the account inventory, retention method and searchable material that can lawfully be disclosed, while preserving a request route for records requiring review. The alternative is the current black box: residents submit a description, and the agency announces what its search found.

Access requires an index

The practical reform is less dramatic than another rewrite of OPRA. Each municipality could publish a registry of official social accounts, including the responsible department, the period of operation, whether comments and direct messages are enabled, the system used to retain records and the office that searches them. That registry would function as a finding aid, an archive’s map of what it holds.

For public posts and comments, municipalities could provide searchable exports at regular intervals. Deleted material could carry a status field and moderation reason where disclosure is lawful. Productions should preserve timestamps, parent-child relationships between posts and replies, and account identifiers in machine-readable files rather than screenshots alone. None of this requires exposing private complainants or protected investigative records.

It does require money. Archiving vendors charge agencies, staff must review material, storage has a cost, and accessible publication needs maintenance. Yet cities already pay part of that bill to preserve the records and answer one request at a time. Keeping the archive hidden behind individualized searches does not eliminate labor.

It distributes that labor inefficiently, then transfers discovery costs to every resident who starts from the same blank form.

The block list remains the test. After the Supreme Court litigation, its status as a record became clearer. Its discoverability did not. A person still has to know that Facebook maintains such a list, know that police administrators can access it, and formulate a request that points the custodian toward the correct account controls.

A city social-media archive is useful to the city even when nobody else can see it. Public access starts when residents can identify what was kept, search what can be released and understand what is missing. Until then, preservation is custody with better backup.

Questions people ask

Are municipal

Facebook posts public records in New Jersey?

They can be when municipal employees create or maintain them in the course of official business. Retention and disclosure depend on the post’s function, applicable schedules and any lawful exemption; the fact that Facebook stores the material does not, by itself, remove it from public-records law.

Can a city delete comments from an official social-media page?

A city may moderate under a lawful, consistently applied policy, but deletion can create both First Amendment and records questions. The original comment, moderation action and related metadata may still need to be retained even after the public-facing version disappears from the page.

Can residents request direct messages sent to a city account?

Residents can request identifiable official records, including messages connected to municipal business. An agency may redact or withhold protected information, and a broad request can fail if it demands research rather than describing records, which is why account inventories and date ranges matter.

What would real public access look like?

A municipality would publish its official account registry, explain how each account is archived and provide searchable, machine-readable exports of disclosable posts and comments. Requests would remain necessary for private messages and sensitive records, but residents would no longer need to reverse-engineer the city’s platform setup first.