The record is the product.
Alerts are useful for an hour. The record of what was seen, who reviewed it and how it was closed is useful for years — to your safety team, and to whoever audits it.
Four parts, kept together.
Every event GuardianEye raises leaves a single record with four parts kept together. Separately they are fragments; together they answer the question an auditor actually asks — was anyone watching, and what did they do?
- Visual context
- The incident evidence — what the camera saw at the moment the configured rule was met, with the location, camera and module that raised it.
- Status and severity
- Low, medium or high; open, in progress, resolved or closed. Every change of status is kept, not overwritten.
- Reviewer
- The assignee who looked at it, and when. A ticket cannot close without a name on it.
- Follow-up action
- What was done as a result — and, where relevant, what was not.
Review is part of the evidence
A detection on its own proves that software ran. A detection with a review attached proves that a person exercised oversight. GuardianEye keeps the second kind. When a supervisor closes an alert — including closing it as a false detection — that decision is retained with the event, so the record shows judgement, not just automation.
Why the boundary is written down
Detection is limited to the configured PPE and site-safety rules. GuardianEye does not infer emotion or intent, does not act on its own, and does not replace safety management. Writing the boundary into the product is itself evidence: an auditor can see what the system was asked to do, and what it was not.
The EU AI Act
The EU AI Act uses a risk-based approach; classification depends on the specific use case. CloudSeals designs the product behind GuardianEye around narrow safety rules, privacy controls, human review and evidence. Customers remain responsible for assessing their own deployment against applicable legal, privacy and worker-representation requirements. Read our approach, and CloudSeals’ EU AI Act guidance.
Straight answers
What exactly is kept for each event?
The visual context, the status, the reviewer and the follow-up action — retained together so that detection, review and closure can be read as one record.
Is the record only about the detection?
No. The review is part of the record. Who looked, when, and what they decided is kept alongside what the camera saw.
How does this relate to the EU AI Act?
Workplace AI carries obligations around transparency, human oversight and record-keeping. GuardianEye is built around configured rules, human review and retained evidence. Classification depends on the specific use case; customers remain responsible for assessing their deployment. CloudSeals publishes its approach in its EU AI Act guidance.
Does GuardianEye make a compliance judgement for us?
No. It gives your people the evidence to support their judgement. Responsibility for safety and for legal compliance stays with the organisation.
Start with one site.
A site assessment looks at the cameras you have, the rules that matter on your floor and how the evidence would reach your auditor. Twenty minutes to find out whether it fits.