Data & privacy

Exactly what leaves this machine, and what never does — grounded in the code, not the marketing. Your runner logs every outbound call, and the logs stay on your disk, so you can check it yourself.

Your runner

Open the Vinculum desktop app on the machine running your runner to see its live status — where it connects, its bound repo — and to toggle file capture. Headless? Set capture_disabled in the runner's config.json, or export VINCULUM_CAPTURE_DISABLED=1.

Leaves this machine

Entries you write
The decisions, specs, and notes you author. This is the point — they're shared because you wrote them to be.
Session activity
When a session starts and stops, the model it's running, and its working directory — so it shows up live on the dashboard.
Activity pulses
Tool names only, never their inputs or outputs. Sent so the worker cards pulse; nothing is stored.
Presence
A heartbeat with your hostname and runner version, so a machine reads as alive.
Files a spawned worker edits
Spawn a worker to do a job and the files it edits are sent, so its work survives a crash before it's committed. Only files the worker touches — never your own sessions. Toggle it off below.
Crash logs
If a spawned job crashes, its last output lines go to telemetry — secret-scrubbed on the server, never into your entries.
Auth
Pairing and session tokens, plus the approval requests for supervised spawns.

Never leaves this machine

Your codebase
Never uploaded. The one exception is files a worker you spawned edits (see left) — and only when you spawn one.
Files you edit yourself
The contents of files in your own sessions never leave. Capture is scoped to spawned workers, not you.
Tool inputs and outputs
The activity feed carries the tool name and nothing else.
Local model inference
Run a local model and its prompts and completions stay on your hardware.
Runner logs
They stay on your disk. The desktop app reads them locally — nothing is uploaded to show them.