When a school threat becomes a law‑enforcement matter, every district asks the same fair question: what happens to our data — and is our students' information protected? Here is the exact journey a threat takes from a school inbox to a law‑enforcement case, what is protected at each step, and who stays in control.
The journey — step by step
- SAM detects the threat — on your premises
SAM is designed to screen email and call content on district-managed systems rather than send student-identifying content to TDR cloud analysis. This property must be verified for the applicable release and deployment.
School · on‑premise
- You decide the handoff
A district-authorized person controls whether information is handed to law enforcement. Notification timing and approval follow district policy, configuration, legal authority, and the verified capabilities of the deployed release.
School controls
- Privacy processing minimizes student-identifying data before an authorized handoff
The workflow is designed to minimize student-identifying data before an authorized handoff and to stop the handoff when required privacy processing is unavailable. The district remains responsible for legal authority, policy, and disclosure approval.
SAM · automatic
- The original stays with you
The system is designed to retain the full original on district-managed storage and to record integrity information for authorized review. The exact retention, access logging, hashing, and timestamping controls must be verified for the applicable release and deployment.
School · retained locally
- Law enforcement receives a redacted case
Law enforcement receives only the case information approved for handoff under district policy and applicable law. The contents and privacy controls must be verified for the deployment.
Law enforcement
- Law enforcement investigates
After an authorized handoff, the agency controls its investigation. SAM‑LE is intended to help authorized personnel organize approved case information for human review; supported workflows depend on the verified agency deployment.
Law enforcement · pilot
- The answer comes back to the school
Law enforcement may return guidance to the school under agency and district procedures. Credibility, response, charging, disclosure, and disposition decisions remain with authorized people.
School · guidance returned
Who controls what
| The school controls | SAM is designed to support | Law enforcement controls |
|---|---|---|
| Whether and when a threat is handed off · its own data and the local original · which staff have access | Privacy processing before an authorized handoff · organizing approved case information · retaining the district original, subject to verified release and deployment controls | The investigation · what it shares with other agencies · charging and disposition |
SAM is designed to keep student-identifying data under district control and minimize data before an authorized handoff. Law-enforcement deployments must be configured and assessed against applicable agency policy, the CJIS Security Policy, and 28 CFR Part 23 where applicable. TDR does not claim blanket compliance or agency certification without a documented assessment.
For law-enforcement agencies. SAM‑LE is designed to help authorized personnel organize approved case information for human review. Availability and supported workflows depend on the verified agency deployment; investigative and legal decisions remain with the agency.
TDR Technology Solutions. This page describes the intended data flow. Release-specific controls, deployment configuration, district authorization, and applicable law determine the information that may be handed to law enforcement.