Privacy & data

Local-first by design — your data never leaves your machine.

vigie is fully local. Everything stays on your machine.

What is captured and stored

vigie captures and stores locally in SQLite at ~/.vigie/data.db:

• Session metadata: start time, status, agent type, prompt, running cost
• Terminal output: every file read, edit, delete; every shell command with exit code and output
• Input history: commands you’ve run, prompts you’ve sent, for replay and recall
• Context snapshots: checkpoint data for rollback

This is all stored on your machine in a local SQLite file. No encryption is applied by default — treat ~/.vigie/data.db like any other sensitive file on your machine.

What is NOT captured

• Your source code is never copied or transmitted — vigie only logs file paths and operations (read, write, delete)
• Your API keys and credentials never pass through vigie — agents connect directly to their providers (Anthropic, etc.)
• Telemetry: no telemetry, no usage tracking, no analytics
• Remote sync: no cloud backup, no remote servers, no webhooks

BYOA privacy

vigie never sees your tokens or code. Because you bring your own AI (BYOA), your connection to Anthropic (or any provider) is direct — vigie supervises the PTY session but never intercepts or inspects the agent’s token stream.

GDPR friendly

Because all data is local and under your control, vigie is GDPR-friendly by default. You own your data. You can delete ~/.vigie/data.db anytime. There’s no cross-border data transfer, no third-party processors.

Where to next

• Configuration — local storage paths
• How it works — the local daemon architecture