Skip to main content

Privacy and data

Argus runs entirely on hardware at your site. Detection, rules, clips, captions and the Copilot all run there. This page lists what Argus stores, where, and what can leave the site.

What stays on site​

DataWhere it livesNotes
Live videoEdge node memory onlyThe edge node keeps the last 15 seconds of frames in memory to cut clips. It does not write a continuous recording. The dashboard's Live Wall streams frames from the edge node to your browser over HTTPS without storing them.
Alert clipsObject storage (SeaweedFS) on the siteAbout 10 seconds of video around each rule match.
Detections, tracks and eventsSite database (PostgreSQL)Camera, object class, confidence, position and time of every detection.
AlertsSite databaseStatus, assignee, notes and an action history.
Captions and search embeddingsSite databaseA one-sentence description of each alert clip, and a vector used for search by description.
Camera settingsSite databaseIncluding the source URL of each camera.
Users and sessionsSite databaseEmail, role and a hashed password. Each sign-in is a session record that ends on logout, expiry or when an admin deactivates the user. A password reset request stores only a fingerprint of the link's code, which is deleted a day after it is used or expires.
Audit logSite databaseWho signed in, and who changed cameras, users, workflows, settings and alerts, with the time. See Audit log.

The detector runs on your edge nodes. The captioning, embedding and Copilot models run in Ollama on your site node. Captions and Copilot answers are generated there, not by a cloud service.

Copilot questions and answers are not saved. Each question is answered and then discarded.

What can leave the site​

Only the items below. The first two happen only if you set them up.

Control plane heartbeat​

If you connect the site to a control plane, the site-cloud-sync service sends:

  • The host name of the node that runs it.
  • The number of enabled cameras.
  • The software version.

It also asks the control plane whether the site's licence is valid and polls it for configuration. It authenticates with the site key that VoisX gives you. It never sends video, clips, captions, events, alerts or user data.

If the control plane can't be reached, the site keeps working. Detection, alerts, clips and the Copilot don't depend on it. See Standalone sites.

Notifications, webhooks and API calls you add​

If a rule has a Send Email, Send SMS, Send Webhook or API Call step, Argus sends a message or request each time the rule matches: email through the mail server you configure, SMS through the SMS provider you configure, and webhooks and API calls to the URL you enter. Each carries only what you put in its message or payload template. The available fields are the event ID, camera name, caption, severity and time. See Rules and workflows and Notifications.

Point these steps only at systems and people you trust with that data.

Password reset emails​

If you set up password reset email, Argus sends a reset link to a user's email address when they ask for one, through the email channel or mail relay you pick. The email contains the link and a short note on what it is for. Nothing else about the site is sent.

Detection library usage statistics​

The edge nodes detect objects with Ultralytics YOLO. While an edge node can reach the internet, this library sends anonymous usage statistics to its developer. To stop this, close outbound internet access for the edge nodes after the install. See Cameras and network.

Captions are neutral by design​

The captioning model is instructed to describe only what is visible, such as clothing colour, vehicle colour and actions like "is entering". It is told never to guess age, gender, identity, intent, emotions or criminality. Captions come from an AI model, so review them before you rely on them.

Who can see the data​

Anyone who can sign in to the dashboard can see alerts, clips, captions, events and the camera list. Camera source URLs, with any user name and password written into them, are shown only to admins. Give dashboard accounts only to people who should see this. See Sign-in, users and roles.

The dashboard, API, clips and live streams are served only over HTTPS. See Install.

How long data is kept​

The retention service deletes events and their clips once they are older than your retention window and no open alert refers to them. The default window is 30 days. You set it in Settings. See Retention.

The retention sweep removes events, the alerts and alert history on those events, their workflow runs, their clips and tracks with no remaining events. It does not remove the audit log. Contact us if you need it purged.

Was this page helpful?