Physical AI · Security, Privacy & Trust

Know what runs where before a camera is connected.

Edgentik processes the selected camera feeds on site. Only the event data and evidence agreed with the customer leave the site. Access, retention and end-of-engagement handling are confirmed before connection.

1 · Data path

The camera feed is processed on site.

The on-site processing hardware processes the selected camera feeds. Event metadata and any approved evidence move into the Edgentik application for review, pattern analysis and reporting.

High-level Edgentik data path from an existing camera to the customer decision
Connection, evidence mode, users, retention and end-of-engagement handling are agreed before the camera is connected.
On siteCamera-feed processing and event detection
Edgentik applicationApproved evidence, review activity and reports
2 · Evidence and data movement

Agree on what may leave the site.

Continuous source video is processed on site and is not transferred to or stored by Edgentik. Selected still images or short clips enter the application only when the customer approves that evidence mode.

DataDefault treatment
Continuous camera feedProcessed on site and not continuously transferred to the cloud
Full video recordingNot stored by Edgentik; only approved stills or short clips enter the application
Event metadataUsed to create the reviewable operating record
Still imagesOptional and transferred only when agreed with the customer
Short evidence clipsOptional and transferred only when agreed with the customer
3 · Privacy purpose

Safety-control review, not worker surveillance.

Edgentik is designed to measure visible operating conditions and support a site safety decision. It is not designed to identify, rank or monitor individual workers.

No facial recognition or biometric identification
No individual worker history or worker scoring
No individual worker productivity monitoring
No automated disciplinary decisions
4 · Access and security controls

Named access around a defined site record.

Organization and deployment isolation

Named roles limit administration, review and export actions to the customer organization and assigned deployment scope. Optional TOTP MFA can be enabled for application sign-in.

Evidence accountability

Evidence views and exports are recorded against named accounts and the relevant deployment record. Review and export permissions are assigned separately according to the agreed operating roles.

Controlled support and credentials

Support access requires customer approval. Camera and application credentials are handled as secrets and are not placed in page URLs or application logs. Evidence and application traffic use encrypted connections in transit.

5 · Retention and handoff

Decide the evidence lifecycle before connection.

Edgentik and the customer agree the working retention period before camera connection. Retention covers the active operating and review windows needed for the customer to complete decisions and export required records.

Choose the end option

Delete evidence after the agreed review window
Export the approved customer record
Archive evidence under an agreed access arrangement
Retain evidence under a continuing agreement

The selected option, hosting region, authorized users and timing are documented in the deployment review.

6 · Decision boundary

Edgentik automates measurement. The employer owns the safety decision.

That boundary is deliberate: the platform structures evidence, review history and follow-through without substituting software judgment for the employer's hazard assessment and control decision.

Edgentik automates measurement

On-site analysis, reviewable evidence, recurring patterns and follow-up measurement after the site acts.

The employer decides

How the hazard should be assessed, which control is appropriate and whether to expand, refine or stop.

Edgentik does not determine

Regulatory compliance, root cause, fault, worker conduct or corrective-action effectiveness.