Moscow Tracked Navalny Mourners from the Church to Their Front Doors

What happened

When Alexei Navalny's funeral took place in Moscow in March 2024, Russian authorities had already prepared. New surveillance cameras were installed around the Borisovskoye Cemetery and the church where the service was held, and facial recognition technology was running before the first mourners arrived.

According to OVD-Info, a Russian human rights monitoring group, at least five people were detained at or after the funeral. The detentions were not random. Dmitry Anisimov, a spokesman for OVD-Info, told the independent Russian outlet Agenstvo that police were able to identify individuals from the footage and trace them, in his words, "right up to their door." The surveillance did not stop at the cemetery gates. It followed people home.

The operator of the facial recognition system was Moscow City Police, working under the Russian government's broader security infrastructure. The specific technology vendor and the software version running on the day have not been publicly identified. What is documented is the outcome: people who attended a funeral for a political opposition leader were identified, tracked across the city, and arrested, not for any action taken at the service, but for having been there.

This use of facial recognition to police political attendance is part of a longer pattern in Russia. The country has built one of the largest urban camera networks in the world, and Moscow's system has been used previously to identify and detain protesters. The Navalny funeral case extended that capability into a more pointed application: targeting attendance at an event as a basis for arrest, rather than responding to specific conduct at that event. Being present became the evidence.

The incident exposes a verification gap that applies well beyond Russia. When a government deploys an AI-powered identification system in a public space and uses the results to detain people, there is currently no reliable mechanism for the detained person, a defense lawyer, or an independent observer to inspect how the system reached its identification, what its error rate was on that day, or whether the match that led to an arrest was correct. A provable record of what a system did, who authorized the query, and what confidence threshold triggered action would not prevent governments from building surveillance infrastructure, but it would at least make the chain of decision visible and subject to challenge after the fact.

Reported impact

Affected parties

Not publicly disclosed

Harm type

Not publicly disclosed

Scale

Not publicly disclosed

Financial impact

Not publicly disclosed

Regulatory action

Not publicly disclosed

Classification

Organization

Not publicly disclosed

AI system

Not publicly disclosed

Industry

Not publicly disclosed

Country

Not publicly disclosed

Provider

Not publicly disclosed

Incident type

Not publicly disclosed

Relevant governance controls

Governance control mapping is not available for this record.

• No controls mappedNot publicly disclosed

Control mapping is analytical. It does not state that any control would have prevented the incident.

Sources and evidence

This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.