Privacy

Account data. Your name, work email, a hash of your password (never the password itself), and which workspace and teams you belong to.

Agent telemetry. From each machine running the collector: hostname, operating system, collector version, and for each agent session the agent and model used, the repository path, timing, token counts (input, output, cache read and write), computed cost, tool names, whether each tool call succeeded, and how long it took.

Message bodies. By default, prompt, response and diff text is uploaded so that session history is searchable. This is the only category that contains your source code or prose, and it is the one you can switch off — see below.

• Provider API keys. The collector does not read, store or transmit the credentials your agents use.
• Your model traffic. Nothing proxies your inference path. AgentLens reads logs your agents have already written to disk; if it is unreachable, your agents carry on and the collector backfills later.
• Files you didn't run an agent on. The collector reads agent session logs, not your filesystem.

Connect with --redact and only metrics leave the machine — token counts, cost and timing. Prompt, response and diff text is never uploaded.

The collector is open source and MIT licensed, so this is checkable rather than a promise. Its configuration and token live in ~/.agentlens/config.json at mode 600.

On the hosted service, in a MySQL database on servers in Falkenstein, Germany (EU). Traffic to the service is TLS-encrypted, and each workspace is scoped by organisation on every query.

If that isn't acceptable for your data, run it yourself — self-hosting keeps everything inside your own perimeter and the service never calls home.

Session history is retained for the window your plan covers — Solo 14 days, Pro 90 days, Business 365 days — after which detailed events age out. Aggregate rollups used for cost trends are kept for the life of the workspace.

Delete a workspace and its telemetry goes with it. Revoking a collector token stops new data immediately.

We do not sell your data, and we do not use your prompts, code or telemetry to train models. Access inside Sinai Space is limited to what is needed to operate the service and respond to support you have asked for.

Subprocessors are limited to infrastructure: our hosting provider, and an email provider for transactional mail such as sign-in and alerts.

Ask and we will export or delete what we hold for you. Email agentlens@sinaispace.com or use the contact form. We aim to answer within five working days.

If this page changes in a way that affects what we collect or how long we keep it, we will say so here and date the change. Material changes are emailed to workspace owners.