A Campus Protest Map Can Become a List of Participants

One pin marking the April 2024 encampment at Columbia University looks like a compact piece of public history. A protest happened here. Police entered the campus. Arrests followed.

News organizations reported the confrontation, while students and observers recorded much of it themselves.

The pin also belongs to a database.

That distinction matters. A news article asks to be read. A database row asks to be sorted, copied and connected to another row. Once a demonstration becomes a location, date, event type and set of participating actors, it can travel well beyond the public-interest map that first presented it.

ACLED, the nonprofit Armed Conflict Location & Event Data organization, built a US Campus Protest Tracker with the College Crisis Initiative at Davidson College during the 2024 protest wave. Its underlying model treats demonstrations as events that can be coded consistently across locations. Researchers identify an occurrence through public sources, classify it, assign actors and place it on a map.

That work has obvious value. It can show whether officials are exaggerating disorder, whether police intervention is concentrated at particular schools and whether spectacular television coverage reflects the broader protest landscape. It can also create a durable index of political participation, assembled at a moment when university administrators, elected officials and employers have shown considerable interest in identifying who took part.

The Columbia pin contains both possibilities. The same structure supports accountability and surveillance.

The map is only the front end

A public tracker often presents itself as a visual explanation. The user sees circles, filters and a short event description. Underneath sits a schema, the fixed set of fields used to organize each record. ACLED’s event data model includes information such as date, location, event category, involved actors, source material and notes.

The precise fields displayed by a dashboard can vary, but the underlying logic is stable: convert messy political activity into comparable units.

That conversion requires judgment. A researcher decides where one event ends and another begins, which organization counts as an actor, whether a confrontation qualifies as disorder and how much confidence to place in a social post or local report. Those decisions may be methodologically defensible. They are still decisions, and the clean row conceals the ambiguity that produced it.

The Columbia encampment did not arrive as a spreadsheet entry. It arrived through student statements, university notices, police activity, livestreams and reporting produced under intense pressure. Coding made those materials legible at scale. It also removed much of their friction.

Friction protects people more often than the transparency industry likes to admit. A hostile researcher once had to search scattered articles, locate archived organization pages and work through inconsistent spellings. Structured data lowers that cost. An actor field can be filtered.

A location can be geocoded, meaning converted into coordinates. An event description can be searched automatically. An export can be retained after the original publisher changes its policy.

The mechanism is mundane. That is why it works.

Identification happens through the join

A campus tracker does not need to publish a student’s name to help identify that student. It only needs to narrow the field.

Take the Columbia pin. Its date and location can be matched against public Instagram posts, student newspaper photographs, livestream archives, arrest reporting and organization statements. A group named as an actor can be linked to its public account. The account can be linked to event flyers.

Flyers may list organizers or carry contact details. Photographs can establish who stood near a banner, though they cannot reliably establish membership, intent or conduct.

This is a data join, a connection between records that share a field such as time, place or organization. Each source may look innocuous alone. Combined, they produce a dossier.

Entity resolution pushes the process further. The term means deciding that references across separate datasets describe the same person or group. A common name, campus affiliation, profile photograph and repeated username can be enough for a researcher, investigator or automated system to infer a match. The inference may be wrong.

A wrong match can still circulate.

There is already a market for tools that turn public online activity into institutional intelligence. Companies including Dataminr and Babel Street have sold products for monitoring publicly available information to government and law-enforcement customers, according to public reporting and civil-liberties research. There is no public evidence that those companies use ACLED’s campus tracker. Their business establishes the demand: institutions pay to have scattered public signals collected, ranked and delivered as actionable alerts.

The original map builder does not have to sell a list of protesters. It can supply one layer in a larger system, while another actor performs the identification and a third decides what consequence should follow.

Public does not mean consequence-free

Map publishers can reasonably say that they are documenting events already reported in public. That defense addresses collection. It does not address reuse.

The First Amendment protects peaceful political association, and the Supreme Court’s decision in NAACP v. Alabama recognized that forced disclosure of membership could chill association by exposing participants to retaliation. Modern trackers are usually not state orders demanding membership rolls. The older principle still identifies the harm: people may withdraw from lawful political activity when participation can be indexed and carried into unrelated decisions.

Those decisions need not come from police. A university can review organizations during disciplinary proceedings. An employer can search an applicant’s affiliations. A private investigator can build a report for a client.

An ideological project can publish profiles designed to influence hiring or immigration scrutiny. Public reporting has documented such consequences around sites including Canary Mission, which compiles dossiers on people and organizations it associates with pro-Palestinian activism.

Federal student privacy law offers little comfort here. FERPA regulates education records maintained by schools receiving federal funds; it does not erase photographs, news reports or independently assembled databases. An arrest that ends without a conviction may remain visible in articles and copied datasets. A correction added to the original tracker may never reach an exported file.

The record outlives the reason it was collected.

That persistence changes the Columbia pin again. During the protest, it helps a reader understand an unfolding confrontation. Months later, it becomes historical data. Years later, stripped from its methodology and combined with other records, it may function as evidence of association.

The row has not changed. Its audience has.

Transparency needs a retention policy

The answer is not to stop documenting protests. Police action, administrative discipline and organized political pressure all deserve records that can be checked. A map that reveals enforcement patterns can protect protesters as readily as it can expose them.

Publishers should stop pretending that publication ends their responsibility.

A tracker can aggregate activity at the campus level rather than publish precise gathering points. It can avoid naming student organizations when the analytical finding does not require them, delay sensitive entries until immediate targeting risks have passed and remove free-text details that add little research value. Download access can be separated from casual viewing, with rate limits and use terms that create consequences for bulk republishing, even though no technical control can prevent every scrape or screenshot.

Retention matters more. Event-level records do not need to remain maximally granular forever. A publisher can establish a schedule that converts older entries into aggregate counts, preserve a restricted research copy and maintain a visible correction log. Arrest fields should distinguish an arrest from a charge or conviction, then reflect later outcomes when reliable public reporting supplies them.

Otherwise the tracker repeats the oldest trick in police publicity: treat the moment of custody as the final meaning of the event.

These measures cost money and time. Researchers must revisit records, handle correction requests and assess risk rather than treating openness as a complete ethical framework. Funders that support civic data projects should pay for that maintenance. Newsrooms embedding trackers should ask about retention and exports before supplying another audience.

The Columbia pin is useful because it fixes an important event in view. It is dangerous for the same reason. The practical test is whether the public needs each field for the stated analysis, not whether a researcher can find that field somewhere online.

Questions people ask

Are campus protest maps public records?

Some entries draw from government records, but the tracker itself is usually a privately assembled publication or research dataset. Its information may come from news coverage, social posts, university notices and police statements, each governed by different access rules and correction practices.

Can a map identify protesters without listing their names?

Yes. A date, precise location and organization can be joined with photographs, public accounts, arrest coverage and event flyers. That combination narrows the possible participants, while entity-resolution tools can infer identities across datasets. Those inferences can be incomplete or wrong.

Who benefits from keeping protest data searchable?

Researchers, journalists and civil-liberties groups can use it to compare police responses and challenge inflated claims about disorder. Universities, political organizations, employers and intelligence vendors can use the same structure for screening or investigation. The benefit depends on which fields persist and who controls the copy.

What would a safer campus protest tracker look like?

It would publish only the detail needed to support its findings, limit precise locations and unnecessary organization names, explain its coding choices, correct arrest outcomes and reduce granularity over time. It would also treat bulk export and long-term retention as governance decisions, rather than neutral technical features.