Security, stated plainly.
Investigation data is sensitive. This page lists what is in place today and what we do not claim, so your IT team can check it line by line.
In place today
- EU-hosted dataApplication data is stored in the EU.
- Row-level tenant isolationEach organisation’s records are separated at the database layer.
- SAML 2.0 single sign-onIncluded from the Business plan.
- Multi-factor authenticationA second factor at sign-in.
- Full audit trailA record of changes to investigation data.
- Soft deletesDeleted records are marked, not erased at once.
- Encryption in transitTLS between your browser and the service.
What we do not claim
- Not certified to SOC 2 or ISO 27001We are not certified against either standard and will not imply otherwise.
- No live connector to other EHS platformsReports and actions feed your system of record by export today; scoped data exchange is set up per integration.
- No published mobile appsThey are in build.
Every line on this page needs to be re-checked against the September 2026 system audit before this template ships.
See the full capability inventoryThe coach and your data.
The coach reads the case you are working on. Here is what that means for the data.
- Only the case in front of youSuggestions are formed from the investigation being worked on. Verify scope
- Not used to train AI modelsInvestigation data is not used for model training. Verify provider terms
- Can be switched offEnterprise customers can disable AI features by policy. Verify
- Nothing filed without a personEvery suggestion waits for an investigator to accept, edit or reject it.
Bring your IT team’s questions.
We will walk them through exactly what does and does not exist.