Security and trust
Your footage never leaves your site.
Video is processed where it’s recorded. What does leave is sealed, signed and logged.
Credentials
Audited, certified, tested.
SOC 2 Type I and Type II reports, ISO/IEC 27001 certification and an independent penetration test.
SOC 2 Type I
The design of our controls, assessed independently.
SOC 2 Type II
Our controls, tested in operation over time.
ISO/IEC 27001
Our information security management, certified.
Penetration test
Completed by an independent tester.
The data path
What stays, what travels.
Three places, one direction. The device always starts the connection.
On site
FloFrame
- Video is decoded, analysed and recorded here.
- Rules and outputs run here, with or without the internet.
- Camera passwords are sealed to the device.
The link
Outbound only, on 443
- The device calls out with its own key.
- No inbound ports, no VPN to open.
- Each alert carries a seal made on the device.
FloFusion
Hosted or private
- Alerts, the evidence you choose and scores.
- Seals checked on arrival.
- Every change and sign-in on a chained log.
If the link drops, detection, rules and outputs carry on. The device catches up when it’s back.
Data
Private by default.
- Footage stays on site
- Video is processed where it is recorded. Only alerts, the evidence you choose and measurements leave the building.
- Outbound only
- Devices connect out over HTTPS on 443. Nothing on the internet can reach in.
- Credentials sealed to the device
- Camera passwords and API keys entered in FloFusion go sealed to the device. FloFusion never keeps or shows them.
- Bystander blur on evidence
- Per site, people who aren’t an alert’s subject are blurred in the evidence copies FloFusion shows, shares, exports and emails.
- No face recognition
- Rules look for people, vehicles, PPE and posture. They don’t identify who anyone is.
- Sealed backups
- Each device backs up its configuration daily, sealed so only FloFusion can open it.
Evidence
Proof that holds up.
Evidence is sealed where it’s made and checked where it lands. Anyone can verify the score history.
- Sealed at the source
- Each alert is sealed with the device’s own key when it happens. FloFusion checks the seal on arrival and shows any that fail.
- A signed, chained score history
- Every hour, each compliance score is signed and chained to the one before. Editing or deleting one breaks the chain.
- Auditor links that expire
- Auditors get read-only, time-limited links to scores. Every view is logged.
How scores are built: Comply
Access
Every action has a name on it.
- Roles down to the device
- Custom roles grant read, write, update and delete per page, and can be limited to some devices.
- A tamper-evident audit log
- Every change, sign-in and access to evidence is logged. Each entry is chained to the last, so any edit shows.
- Sign in your way
- Username and password, or your organisation’s Google or Microsoft accounts.
- Each organisation on its own
- Organisations never see each other’s data. A partner sees a customer’s cameras and alerts only in a support visit the customer allows: time-limited, with a reason, and logged.
Devices
Updated, revocable, replaceable.
- Signed updates, with rollback
- Updates run in a window you choose. A device that isn’t healthy within ten minutes goes back on its own.
- Keys you can revoke
- A lost or stolen device can be cut off at once. It reconnects only with a new one-time code.
- Replace a device, keep its history
- A replacement restores the sealed backup and carries on as the old device. The old one is disconnected for good.
Deployment
Hosted by us, or run by you.
Use FloFusion hosted by Camnitive, or deploy it privately in your own cloud or data centre. Footage stays on site either way.
Bring your security review.
Our engineers will walk your team through the architecture and the controls, and share our reports.