ELBERTA LABS

Appendix B: How It Works, and How Data Is Handled

Prepared for	Gallery Condominiums Board
By	Elberta Labs
Date	25 August 2026
Part of	Managed Camera Intelligence pilot package

This appendix explains how the system works, shows how it changes what the front desk sees, and sets out how data is handled. None of it is required to approve the pilot. It is here for a technically-minded reader.

How the system works

The design layers on top of the cameras and analytics the building already owns, on a foundation of open-source systems, tailored to the building.

Stage 1, local and real-time. Frigate with ONNX object detection runs on a local NVIDIA RTX A2000 appliance sized for up to 12 cameras. It does the constant, real-time watching on the property.
Stage 2, review. When an event needs a closer read, a vision-language model (Qwen3-VL 8B) reviews the snapshot and helps decide how to present it. This runs on-premises through Ollama, with occasional routing to approved hosted providers for harder reviews.
Downgrade, never discard. The AI can recommend a lower presentation priority. It does not delete the source alert. Every event is retained for review and audit.

The pilot will compare local detection performance against the building's current IntuVision outputs. We did not identify an off-the-shelf option that met the building's stated requirements without substantial platform or hardware replacement.

Because the foundation is open-source, the building is not tied to per-camera license fees or a single vendor's platform.

What the change looks like

The value is easiest to see in ordinary events the current setup pushes to the desk as if each were urgent.

Event	Today	With prioritization
Yard maintenance crew on camera	Repeated alerts through the visit	Recognized as routine, logged, presented low
Someone sitting in a parked car	Alert with no context	Flagged for a look with a short description
Routine pedestrian gate traffic	Steady stream of alerts	Grouped and downgraded, still retained
Ambiguous scooter at the gate	Looks like any other alert	Raised for attention as worth a look

Escalation by severity

Presentation and escalation follow the severity of the event, not a single timer.

Severity	Handling
Critical	Surfaced immediately at the top of the queue with an audible priority.
Elevated	Surfaced within 15 minutes for a look.
Routine	Logged and retained, no interruption.

A separate management notification, on the order of an hour, covers missed acknowledgments and system audit. It is not the response target for an urgent event.

Data governance and cybersecurity

Question	Answer
What imagery leaves the property?	Only event snapshots, and only when a Stage 2 review is triggered. Continuous video does not leave the property.
Who can access local footage, snapshots, logs, and the dashboard?	Authorized building staff and Elberta administrators. Remote administrator sessions are logged.
How long is data retained?	Local footage stays under the association's existing retention policy. Approved cloud processors do not retain transmitted snapshots or use them for model training.
What happens if the internet or a cloud model is unavailable?	The system continues on the local appliance and falls back to the original alert priority. It does not go dark.
How are credentials, backups, patches, and network segmentation handled?	Managed by Elberta as part of the service, on the surveillance network, with credentials kept out of chat and shared logs.
Is facial recognition or biometric processing used?	Facial recognition may be used for one narrow purpose: recognizing known residents so their routine movement can be downgraded. Identity matching that names individuals, demographic inference, and biometric processing for any other purpose are excluded. Any resident-matching data stays on the local appliance and is not sent to cloud providers or used to train models.
Can Elberta change cloud providers or models?	Yes, as the technology evolves, provided every provider used meets the same zero-data-retention, enterprise standard. The commitments in this schedule hold regardless of which model runs. Any material change to the data-handling posture is reported to the board.
What is the incident-notification process?	Defined in the managed-services agreement, with prompt written notice to the association on a confirmed incident.
Can Gallery data or name be used in Elberta sales material?	No. No name, image, case study, or performance result is published without separate written authorization.

Approved hosted providers are enterprise services operated under zero-data-retention terms. Transmitted snapshots are not retained by them and are not used to train models. Local footage remains subject to the association's existing retention policy.

Georgia has no biometric-privacy statute, so no statutory resident consent is required for the narrow resident-matching use above. The board is encouraged to decide whether and how to inform residents as a matter of its own policy.