01
Lawful purpose and authorization
Stratir systems are built for customer-authorized workflows. Hospital, intelligence, and operational deployments require explicit scope, lawful basis, and contractually defined use.
Stratir governance
Privacy and Civil Liberties
Stratir builds software that runs in sensitive environments: hospitals, logistics networks, intelligence workflows, and operational command posts. This page states how we think about privacy, civil liberties, and accountable use when our products sit close to people's lives and livelihoods.
Software that runs operations is never neutral. It decides what gets recorded, who can see it, how long it persists, and whether an automated suggestion becomes an action. Stratir takes that responsibility seriously in every forward-deployed engagement.
We are a founder-led applied AI company, not a data broker. Our incentive is to ship production systems partners can inspect, trust, and run. That requires privacy and civil liberties to be architectural constraints, not marketing footnotes added after the demo works.
When we deploy in hospitals through programs like MedicOS, in logistics through design partners, or in intelligence-adjacent workflows, we start with authorization, role design, retention, and export discipline. If a feature cannot be explained to the operator who will be accountable for it, it does not ship.
Operating principles
02
Data minimization by design
Products collect what operators need to run the workflow, not what vendors find convenient to monetize. Fields, retention windows, and export paths are scoped to purpose.
03
Human judgment on high-risk paths
Automation accelerates 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 should be inspectable. Partners and operators must be able to reconstruct 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 work in health, logistics, and security contexts demands restraint: collect what the mission requires, protect what you collect, and delete or export when the mission ends.
Health deployments
Additional constraints for hospital and public health programs
MedicOS and other Stratir health research programs operate where patient trust, ministry oversight, and ward reality intersect. The following constraints apply in addition to our general operating principles.
- Patient identifiers are role-gated. Ward staff, pharmacy, and director views expose different slices of the same ontology.
- MedicOS research pilots require hospital board or ministry authorization, defined retention, and export paths aligned to local regulation.
- Offline sync is conflict-safe and logged. Silent merges that drop clinical or stock events are unacceptable design outcomes.
- Structured notes and protocol variance are reviewable artifacts, not disposable chat. Supervisors retain escalation authority.
- Partner exports (DHIS2, CSV, ministry windows) strip fields not required for the reporting purpose.
- Stratir does not sell patient data, broker access to hospital records, or train general models on identifiable clinical content without written authorization.