What does Signals actually do?
It reads the cameras, transactions and sensors an operation already runs, together, and answers questions about them in natural language. You ask in plain English and you can keep asking; it is a conversation, not a report.
How does it fit what we already run?
We configure the platform to your business rules and requirements so it surfaces the intelligence your operation needs. Nothing is migrated and nothing is switched off.
Where does the processing happen?
On site, in the cloud, or split between them. It is settled with you during the site survey and written into the deployment. Either way, you own and access your own data.
What do you retain?
Counts, events and answers, yours to access and export, on your retention schedule. No video is stored by default.
Counting, not tracking
Cameras are everywhere; what matters is how the information is used. Signals counts people: how many, where and for how long. By default the deployment builds no profiles and keeps nothing about an individual.
Identity features
Off by default. Where an operator wants them and regulations allow, they are scoped for that deployment and agreed in writing.
What happens if the internet drops?
Signals keeps accumulating through an outage and catches up on recovery.
Manual override?
Every action path has one, as a design rule. Signals proposes; a person you named signs off. Anything it does on its own is logged and reversible from the same screen.
SOC 2?
Not yet, and no document of ours claims otherwise. SOC 2 Type I begins when an enterprise engagement requires it, followed by Type II on the standard observation window.
