# What stays on your machine

What Salidium keeps, where it keeps it, and what it runs in your repository.

Source: https://salidium.com/docs/local

The daemon, the event store, the report and the interface never leave your machine. There is no account, no telemetry and no hosted service.

- State lives in `~/.salidium`, or wherever `SALIDIUM_HOME` points. [Environment](https://salidium.com/docs/environment.md) lists the rest.
- The daemon listens only on `127.0.0.1`, by default on port `47822`.
- Every request for your data carries a token, regenerated each time it starts.
- The directories it creates are readable only by you, and it repairs their permissions on every start.

## Your repository

When a turn ends, when a session starts, and after the agent commits, for a live session inside a git repository, Salidium runs four read-only commands to record where the work sat.

- `git rev-parse --show-toplevel`
- `git rev-parse HEAD`
- `git rev-parse --abbrev-ref HEAD`
- `git status --porcelain=v2 --untracked-files=normal`

Nothing is written, and `SALIDIUM_NO_GIT=1` switches it off.

## Redaction

Credential-shaped strings are redacted, and files on paths that hold credentials have their contents withheld. Both happen when an event is ingested rather than when it is shown. So what Salidium suppresses is suppressed everywhere: in what it shows you, and in the packet an [explanation](https://salidium.com/docs/explanations.md) is written from.

> How much was redacted is counted, and the count is in Quantities under data handling.