Skip to content

Privacy and data

Driga runs on your machine and has no account, server or API key. This page is about the app; the website is covered on its own privacy page.

Local agent session metadata and logs, the process table, machine health and local Git state. Agent configuration is changed only by explicit setup and hook commands, each previewed first.

The default capture_text = "titles" stores generated session titles, file paths, and session, process, Git and machine metadata.

capture_text = "snippets" additionally stores prompt and handoff snippets, each scrubbed for secrets and capped at 200 characters.

Full transcripts are never stored. Paths and titles can identify you, and secret scrubbing cannot guarantee privacy.

Nothing, unless you turn one of these on:

FeatureWhat leavesWhere
Paired machinesMetadata and titles by default; snippets only if both sides opt inViewers you paired with
Chat and driga askYour question, scrubbed, and context filtered by the capture policyClaude, through your installed claude CLI and its login
SummariesProject name, branches, counts, commit subjects, session titles; handoff text only with snippetsSame

Chat tools you approve may make network connections. Claude’s own session history is managed by Claude, not by Driga’s capture policy.

OTLP intake listens on loopback, and drops prompt, response and tool content, user.* attributes and organization.id before storage. The web dashboard listens on loopback and requires a local access token.

DatamacOSLinuxOverride
Database and collector state~/Library/Application Support/driga/$XDG_DATA_HOME/driga or ~/.local/share/driga/DRIGA_DATA_DIR
Hook spool~/Library/Application Support/driga/events/$XDG_STATE_HOME/driga/events or ~/.local/state/driga/events/DRIGA_SPOOL_DIR
Configuration$XDG_CONFIG_HOME/driga/config.toml or ~/.config/driga/config.toml$XDG_CONFIG_HOME/driga/config.toml or ~/.config/driga/config.tomlDRIGA_CONFIG

On Windows the data directory is %LOCALAPPDATA%\driga\ and the configuration is %APPDATA%\driga\config.toml.

Database and spool files are mode 0600 in 0700 directories. driga doctor warns when the database and its WAL exceed 500 MB.

MCP server trend detail is kept at minute resolution for 24 hours, then as hourly endpoints for 30 days. Persisted Chat conversations are kept for 30 days.