Privacy

Privacy at LucidWatch

A security system watches people. We think that puts the burden on the system to protect them. This page explains how the product does that, and how this website handles your data.

In the product

Behaviour, never identity

LucidWatch detects what happens, such as a door forced open, a fall or a crowd above a zone limit. It does not identify who anyone is. There is no face recognition anywhere in the product, and no emotion recognition.

When an investigator searches for a person across cameras, the search matches clothing and build. It never uses a face or any other biometric. A person must select the subject of a search; the system does not choose someone to follow.

No camera goes live without a privacy impact assessment

GDPR asks for a data protection impact assessment (DPIA) before systematic monitoring starts. In LucidWatch, a camera goes into service only under a finished DPIA that covers every zone the camera sees. This is a block, not a warning, because a warning is easy to click past.

Face blur stays on without a legal basis

Faces are blurred by default in every zone. An administrator can turn blur off in a zone only where every camera has a documented legal basis and a finished DPIA. An operator who needs to see a blurred face must give a reason. Face blur automatically returns after a short period.

The legal status of every camera

Each camera record shows its lawful basis and the DPIA that covers it. The page lists the cameras that still need one, so the gap is visible, not hidden in a document.

Notice signs

LucidWatch drafts the notice text for each zone, so the sign on the wall matches what the system actually does there. The customer edits and approves it.

Requests from people

A person can ask a site to see or delete footage of themselves. LucidWatch finds that material from records the site already holds, such as a badge number or a named incident. It never searches the archive by face. Material that is part of a sealed case is held until the case owner releases it.

Explainable, with people in control

• Every incident shows the signals behind it: which camera, door or reader, and when.
• Every search answer says what it matched and what it searched.
• LucidWatch proposes the response; people approve actions that change the building. A person can override any automatic action, with a reason.
• If the system fails, the site falls back to manual operation, never to automatic.
• Every action and setting change is recorded. If someone alters a record later, the audit trail makes that visible.

Where the data lives

LucidWatch runs on an on-prem server or in a private cloud. The customer owns its data.

The frameworks we design to

We use the seven Privacy by Design principles as an engineering checklist, and design with GDPR and EU AI Act requirements in mind. This mapping is our own design work. It is not a certification. We plan to certify our information security management under ISO 27001.

On this website

• This website sets no cookies and runs no analytics or tracking.
• It has no forms. The fonts and images load from this website only, so your browser contacts no third party.
• If you email us, we use your email address and message only to reply to you, and we do not share them.
• To ask what we hold about you, or to have it deleted, write to info@lucidwatchai.com.

LucidWatch AI is in development. Product details on this page describe the design and can change as we build.