Accessibility & Data Handling

Our accessibility commitment

SitRep Pipeline is built for use by county government staff and, through its public-facing exports, by the residents they serve. We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard set by the U.S. Department of Justice's Title II rule for state and local government web content. Smaller jurisdictions, including Grand County, have until April 26, 2028 to meet that standard.

This is a statement of an ongoing commitment and target, not a claim that an accessibility audit has been completed or that full conformance has been achieved today. If you encounter a barrier using this site, please contact SLT Ventures support so we can address it.

How your data is handled

Every fact in a situation report carries a sensitivity level — public, internal, or restricted — set at the moment the fact is captured. When a report is exported or shared, that sensitivity level mechanically controls what each audience sees:

• Operational exports (internal EOC use) show everything, including restricted detail like exact shelter addresses or other life-safety specifics.
• Executive exports show public and internal information, omitting the most sensitive restricted detail.
• Public Information (PIO) exports show only information explicitly marked safe for public release — nothing is included by default.

This filtering is a fixed, mechanical rule applied the same way every time — it is never a judgment call made by the AI drafting a report. Every fact-bearing field is also required to cite at least one source, so any figure in a report can be traced back to where it came from.

API keys and AI providers

Each county tenant brings and configures its own AI provider API key (Anthropic Claude, OpenAI, or Google Gemini). SLT Ventures does not draft a county's situation reports using its own shared credentials — a county's data is only ever processed through that county's own configured provider account.