Where your data lives, and who controls it.

Imagery is processed on-prem, inside your network.

Captured imagery travels over the local network to a customer-controlled inference server — an on-prem GPU machine that runs the computer-vision model. Inference happens there. No imagery is sent out of your network for processing.

• Processing location: on the customer-controlled inference server, on the local network.
• Inference: local / on-prem — not a cloud service round-trip.
• Connectivity required: a local network path from the glasses to the inference server — that's all the system needs to verify.
• Offline behavior: verification happens when imagery reaches the server. If a device is temporarily offline, captures buffer on the device and sync automatically once the connection is restored, so no inspection is lost. Connectivity is arranged to suit your site.

Retention is optional, off by default, and yours to set.

SureSight needs no visual-data retention to operate — verification produces an inspection record without keeping the underlying imagery. Where you do want to retain images or video, retention is a configuration you control.

• Retained by default: no — the system operates without keeping imagery.
• Optional retention: configurable to your data-retention policy when you choose to keep records.
• Policy owner: the customer sets and changes the retention policy.

The record is metadata, not footage.

Each verification writes a compact, queryable record. This is what makes third-party auditing a query rather than a forensic project — and it is what the system produces even when no imagery is retained.

Verification does not require worker identity.

SureSight verifies observable work. It does not need to know who performed an inspection to confirm that the inspection occurred. Where your workflow requires attribution, you can optionally associate a record with an authenticated user or device — a deliberate, customer-side choice, distinct from tracking workers by default.

• Identity required to verify: no.
• Optional association: a customer may link a user or device/session to records where the workflow requires it.
• Anonymous verification vs. tracking: the default confirms that the work happened; associating it with a specific employee is an explicit, opt-in configuration — not the baseline.

You own the deployment.

SureSight runs inside your environment, on your terms. The controls that matter to a security review stay with the customer.

• Deployment configuration: owned by the customer.
• Access control: the customer controls who can access the system and its records.
• Retention: the customer controls whether and how long imagery is kept.
• Integrations: the customer controls what SureSight connects to.