> For the complete documentation index, see [llms.txt](https://www.blainecountysheriffoffice.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.blainecountysheriffoffice.org/sop/section-6-information-release-policy.md). # Section 6 - Information Release Policy Blaine County Sheriff's Office Information Release Policy No deputy, supervisor, or member of the **Blaine County Sheriff's Office (BCSO)** is authorized to release information regarding an active investigation to any unauthorized or uninvolved person without prior approval from the **Sheriff**, a member of the **Command Staff**, or an authorized designee. All confidential, sensitive, and law enforcement-sensitive information shall be safeguarded and handled in accordance with department policy and applicable laws. Unauthorized disclosure of confidential information may compromise investigations, jeopardize public safety, and violate the rights of involved parties. Any employee found to have improperly released confidential information shall be subject to disciplinary action, up to and including suspension, termination, and, where applicable, criminal prosecution. The **BCSO Public Affairs Unit** or another member of the Sheriff's Office specifically designated by the Sheriff or Command Staff shall serve as the official source for releasing information to the public and members of the media. No other employee shall make public statements or release investigative information unless expressly authorized to do so. \ Patrol Ranks can release documents about incidents, events, etc when allowed from CS+ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.blainecountysheriffoffice.org/sop/section-6-information-release-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.