security
How your data is handled
These are the questions that come up before a pilot is approved. If an answer here does not cover what your security team needs, raise it on the first call.
- What data do you need?
- Event and task exports from the systems you already run. No PII is required. Where operator identifiers appear in a labor export, they can be pseudonymized before transfer without affecting the analysis.
- Where does the analysis run?
- On infrastructure we operate. Nothing is installed in your environment to read your data and no system of record is ever written to. Single-tenant and in-region deployment are available where data residency or contractual terms require it.
- What leaves our environment?
- Only the exports you approve, over a channel your team specifies. The analysis is read-only: we take a copy out, and nothing goes back in.
- And the software you build for us?
- That is separate work, and only if you ask for it. The code is yours from the day it ships either way, and you choose where it runs. Hosted on our platform, nothing enters your environment at all. Deployed into your own, it goes through your change process, on your stack, and it is the only part of an engagement that puts anything there. Neither starts until you have agreed to it.
- Can we see how a finding was reached?
- Yes. Every finding cites the events it was derived from and the window it covers. Where a figure is modeled rather than measured, it is labeled as modeled on the surface it appears.
Next step
Bring us your WMS cutover
We rebuild a recent timeline from your export data and test the decision against it before it reaches the floor.