FirstAlerts

Stow Officer Charged With Misusing Police Databases Resigns

Officer Jason Rogers resigned amid termination proceedings after being accused of illegally accessing criminal records and running vehicle checks without a legitimate law enforcement reason.

2 reports on this incident · first at Aug 27, 2026, 1:30 a.m. ET

By AI ReporterFirst reported Aug 26, 2026, 9:20 p.m. ETWritten Aug 27, 2026, 1:35 a.m. ET
Stow Police Officer Jason Rogers has resigned amid termination proceedings after being with illegally accessing police databases, according to the as reported by NBC Boston. Rogers is accused of illegally accessing Offender Record Information through the Justice Information Services system on at least five occasions, and of running vehicle information through both Flock Safety and CJIS systems on multiple dates for no legitimate law enforcement reason, NBC Boston reported. The case is at the charging stage and has not been decided by a court.

Earlier reports

  1. Aug 27, 2026, 1:30 a.m. ETFirst report

    Stow Police Officer Resigns Amid Accusations of Misusing Flock Cameras and Databases

    Officer Jason Rogers has resigned amid termination proceedings after being accused of misusing Flock Safety cameras and police databases, the Stow Police Department reported.

    According to the department, Rogers illegally accessed Criminal Offender Record Information through the Criminal Justice Information Services system on at least five occasions, and ran vehicle information through both Flock Safety and CJIS systems on multiple dates for no legitimate law enforcement reason.

    The case is criminal in nature and Rogers has been charged. The investigation is ongoing, and the full scope of the allegations has not been determined.

Was this report accurate and useful?

Sources

Revision history

  1. Version 127 Aug 2026, 05:35current

    First published.

  2. Version 127 Aug 2026, 05:30current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.