VisionAery

    Security and data handling

    Where processing happens

    VisionAery Liquid Leak Detection runs on the camera (Axis ARTPEC-9, Hanwha Wisenet 9) or on an edge server at your site (Emerson PACSystems IPC, x86, NVIDIA Jetson Orin). Detection, alarm staging and the web dashboard are served from that device. There is no VisionAery cloud service in the path, and the software works with no internet connection.

    What goes to your systems, and how

    The software publishes alarms, telemetry (device and detection status) and snapshots to the systems you configure: native camera events into your VMS, MQTT with JSON or Sparkplug B to your broker, and HTTP webhooks to your tools. By default these travel over your local network to a broker, VMS or endpoint you control. They reach the public internet only if you configure a destination there. Video itself is never sent anywhere for processing.

    The one connection that leaves the site by design is the optional weather-service lookup for the rain gate, and only if you enable it. A failed weather lookup never blocks detection.

    What VisionAery receives: nothing

    The software sends no usage data to VisionAery, does not phone home, and performs no remote license check. Licenses are signed, hardware-bound entitlements validated on the device: stream counts, expiry, clock-rollback and tamper detection are all enforced locally. An entitlement authorizes channels on exactly one device and does not travel with the hardware. The only recovery from an invalid license state is a re-issued entitlement from VisionAery.

    Packages and updates

    Downloads are signed packages obtained from visionaery.com after EULA acceptance; the Axis application is a signed ACAP package. The model is encrypted inside the package. Updates are applied by installing a new package on the device; nothing updates itself over the network. Configuration can be backed up and restored from the dashboard.

    Access and audit

    The dashboard is served by the device and sits behind the camera's or server's own authentication. EULA acceptance is recorded on the device. Alarm records with snapshots can be exported through your VMS or your MQTT and webhook integrations for audit.

    Website data

    The website collects only what you submit on the contact, quote, trial and download forms, and the download acceptance record. Details and deletion requests are on the privacy page.

    What we do not claim

    No compliance certifications (SOC 2, ISO 27001, CJIS) are held today. If a deployment requires one, contact support@visionaery.com for the current security package.

    Questions

    FAQ

    Is VisionAery cloud-based?

    No. Processing, alarms and the dashboard run on the camera or on an edge server at your site.

    Does any video leave my site?

    No video leaves the site for processing. Alarms, telemetry and snapshots go only to the VMS, MQTT broker or webhook endpoints you configure, over your local network unless you point them elsewhere.

    Does it need an internet connection?

    No. Internet is needed only for the optional weather-service rain gate and for downloading packages.

    Does the software send anything to VisionAery?

    No. There is no phone-home, no usage reporting and no remote license check. Telemetry over MQTT goes to your own broker, not to VisionAery.

    How are licenses enforced?

    Signed, hardware-bound entitlements validated locally on the device.

    How do updates work?

    You download a signed package and install it on the device. Nothing auto-updates over the network.