01
Lawful purpose and authorization
Stratir systems serve customer-authorized workflows. Investigation and operational deployments require explicit scope, lawful basis, and contractually defined use.
Governance
Privacy and civil liberties
Intelligence software shapes what is collected, who may see it, and whether an automated suggestion becomes a finding. Stratir treats privacy and civil liberties as design constraints in every program we run, especially where collection, aggregation, and review sit close to consequential decisions.
Software built for intelligence work is never neutral. It encodes retention, access, export, and the boundary between suggestion and conclusion. Stratir accepts that weight in every research program we undertake.
We are a research lab, not a data broker. Our work succeeds when partners can inspect what we release, understand how it behaves, and run it under their own authorization and accountability structures. Privacy and civil liberties belong in the architecture, not in a footer.
In sensitive programs, we begin with scope, role design, retention, and export discipline. If a capability cannot be explained to the operator who will answer for its use, it does not ship.
Operating principles
02
Data minimization by design
We collect what the workflow requires, not what a vendor model rewards. Fields, retention windows, and export paths are scoped to purpose and reviewable by operators.
03
Human judgment on high-risk paths
Automation may accelerate clerical work. Diagnosis, escalation, detention, and other high-consequence decisions remain with accountable humans unless partners define otherwise in writing.
04
Auditability over black boxes
Outputs, agent actions, and sync events must be reconstructible. Partners and operators should be able to see what the system knew, when it knew it, and who approved the next step.
05
No secondary use without consent
Customer data is not repurposed for model training, marketing, or unrelated product development unless partners explicitly authorize that use in contract.
06
Proportionality in the field
Forward-deployed intelligence work demands restraint: collect what the mission requires, protect what you collect, and delete or export when the mission ends.
Sensitive programs
Additional constraints for investigation deployments
Investigation and all-source intelligence deployments operate where source handling, access control, and review discipline intersect. The following constraints apply alongside our general operating principles.
- Case material is role-gated. Analyst, reviewer, and leadership views expose different slices of the same evidence set.
- Sensitive collection requires defined authorization, retention policy, and export paths aligned to legal and contractual boundaries.
- Agent-assisted enrichment is logged. Silent automation that bypasses review gates is an unacceptable design outcome.
- Findings and briefs are reviewable artifacts, not disposable chat. Supervisors retain release authority.
- Partner exports strip fields not required for the reporting purpose.
- Stratir does not sell intelligence data, broker access to case files, or train general models on identifiable investigation content without written authorization.