Montana Public Records Initiative

An official website of the Montana Public Records Initiative

Free public records for Montana

Arrests, courts, jails, meetings & county lookup

The Montana Blotter
Montana Public Records Directory
Montana Blotter / PII & Privacy Transparency

Transparency

What we scan for, what we catch, what we redact.

Before any post is published, it is run through an automated PII auditor that scans for personal identifiers and redactions, then it is reviewed by an editor. This page shows the aggregate picture.

Audit Dashboard Updated 2026-05-31

How clean is the public post corpus?

Counts come from the posts table. Flagged means a post that had at least one PII span detected during audit; redacted spans do not appear in the public text.

Posts Audited
512
Clean
497
Manual Review
15
Pending
0
% With Flags
63.1%
323 flagged posts

PII types detected

Type Detections Why we redact it
home_address 2282 Street addresses β€” redaction triggered when a residential identifier (apartment, trailer, home) is paired with a personal label.
dob 57 Dates of birth labeled as personal (DOB, birthday, born on). Birthdays that appear as event context are kept.
other 2 Other PII surfaced by Claude during tone/context review. Re-reviewed manually before publication.
phone 2 Phone numbers β€” redaction triggered when the number is paired with a personal label (caller, victim, witness).

Severity breakdown

High = direct identifier (SSN, MT DL). Stops publication automatically. Medium = contextual identifier (residential address, personal phone). Redacted and editor-reviewed. Low = contextual date or label (DOB, age). Reviewed before publication.

Medium: 2267
High: 19
Low: 57
How It Works

What runs before a post goes public.

1. Regex scan

Every post draft is scanned against a list of pattern detectors β€” SSN shape, MT DL format, US phone, residential street address with a personal-context label, and labeled DOBs. The detectors are deliberately conservative: a street address without a residential context word (apartment, residence, home, trailer) is allowed because it is typically the public incident location.

2. Claude review

When the API is available, the post is also passed to a second-pass model that flags contextual PII the regex misses β€” for example, an indirect reference to "her boyfriend's truck, which is usually parked at 412 Spruce" β€” and returns a clean rewrite. The clean version is the one that publishes.

3. Editor sign-off

Posts flagged as manual_review are not published until an editor reviews them. A clean post is published automatically. A pending post has not yet been audited.

4. The corrections log

If something slips through, we log the fix in the public corrections log. Editorial framing changes, factual errors, and PII redactions after the fact are all visible there.

Editorial Standards

Montana Blotter is designed to make public records and public meeting information easier to access. It is not a government office, and it does not replace official notice, clerk records, court files, or agency databases.

1. Primary Source Rule
We prefer direct links to official county, city, court, sheriff, police, and state judiciary pages. Where possible, each page should point readers back to the original public record, agenda, minutes page, or official document listing.

2. What We Standardize
Date and time formatting — location and body-name labeling — document labels such as agenda, packet, or minutes — searchable statewide filters and metadata.

3. What We Do Not Claim
We do not claim to be the official keeper of public records. We do not guarantee that a third-party government site is complete, current, or correctly maintained. We do not treat summaries or extracted text as a substitute for the official source file.

4. Update Cadence
Automated sources are checked on a recurring basis. If a source is stale, broken, or moved, the originating public body remains the authoritative reference until the source is repaired.

5. Provenance and Visibility
We aim to show where information came from, when it was last refreshed, and how users can verify it.

6. Redactions and Sensitive Material
We may review records for obvious sensitivity, legal restrictions, or redaction issues. The existence of a public record does not automatically mean every field or derivative presentation should be amplified without review.

7. Corrections
If a source link breaks, a meeting is mislabeled, a record is duplicated, or a page needs clarification, see the Corrections Policy for the reporting workflow.

8. Government and Clerk Communications
If you work for a Montana public body and need a source updated, corrected, or removed, contact us directly. We prefer exact URLs, dates, and a brief explanation of the change.

9. Contact
Montana Blotter — records@montanablotter.com

Read full standards →

Corrections Policy

We want corrections requests to be specific, easy to verify, and fast to act on. The more concrete the report, the faster it can be reviewed.

1. What To Report
Broken official source links — moved agenda or minutes pages — incorrect meeting date, body name, or location label — duplicate records or meetings — stale source pages — material factual errors in a summary or description.

2. What To Include
The exact Montana Blotter URL — the exact official source URL that should be used — a short description of what is wrong — if timing matters, the date and time the official source changed.

3. Where To Send It
Email records@montanablotter.com with subject line Correction Request or Source Update. If you represent a government office, say so in the message.

4. Review Standard
We review corrections against the official source when available. If a report cannot be verified, we may ask for a clarifying URL, screenshot, or exact document reference before changing the page.

5. Response Goal
Our goal is to review straightforward source and labeling issues within two business days. Complex disputes, legal issues, and record-sensitivity questions may take longer.

6. How Fixes Are Handled
Broken or moved source URLs are updated at the source-config level when possible. Mislabeled dates, titles, or locations are corrected in the public presentation. If a government source removes or replaces a document, the official source controls.

7. Limits
A correction request does not automatically guarantee removal. Montana Blotter may preserve accurate public-record references while updating labels, links, timestamps, or explanatory text.

Read full corrections policy →

Montana Laws Reference
Browse Montana Blotter
Sign In Join

Look up records

Public Meetings Jail Rosters New Bookings Bail Bonds Case Tracking

Maps & trends

Crime Map Crime Data

Safety alerts

Code Violations License Sanctions Offender Alerts Active Warrants

News & help

Blog Help & Support

Stay updated

Get Alerts