Privacy, Data Ownership and Security of Security

The customer owns the recordings and owns the policy. We design, install, document and support the system. We do not hold your video, we do not broker access to it, and we do not need standing access to your cameras to support you.

Where remote support access is useful, it should be time-bound, logged and revocable, and it should appear in the same audit trail as any other privileged action.

Retention should be chosen deliberately and written down. Both directions carry a real cost, and an honest vendor tells you both.

Short retention reduces privacy exposure and reduces storage cost. It also destroys evidence before some complaints surface, and complaints about harassment, discrimination or workplace injury frequently surface weeks after the event.

Long retention preserves that evidence and increases both cost and exposure. There is no universally correct number. There is a number that matches your risk, your obligations and your budget, and the point is to choose it on purpose.

Role-based access limits what each user can see and do. Audit logging records what they did. Together they are the mechanism that lets you prove after the fact that a record was protected, which is the only form of privacy assurance that survives a dispute.

Design for the smallest workable privilege. A school resource officer, a facilities manager and a district administrator should not share one login, and export should be a privileged, logged action rather than a button everyone has.

The platform can pixelate individuals by default, so operators monitor movement and behavior without identifying people, and unmasking requires a privileged action that is logged. The manufacturer's masking technology holds a European privacy certification.

This is genuinely useful in schools, healthcare and multi-tenant property, where continuous monitoring is justified but continuous identification is not.

No default pooling. No standing external access. When you share, you choose the recipient, the scope and the duration, and you can revoke it without calling us or the manufacturer.

The physical security system is itself a networked system, and the industry calls hardening it security of security. It is the part most integrators skip and most auditors now ask about.

The platform supports the mechanisms these frameworks require of a controller: defined retention, access control, audit trails, masking, export controls and the ability to respond to a subject request. The obligations sit with you as the controller, and we configure the system so you can meet them.

If you operate under a framework with specific documentation requirements, tell us during design. Retrofitting evidentiary controls after commissioning is more expensive than designing for them.

We configure to the jurisdiction and to the customer's policy rather than shipping vendor defaults. Analytics that are legal in one setting can be prohibited in another, and defaults do not read statutes.

In Colorado school deployments that is a statutory requirement rather than a preference, and we design to that constraint from the start.