Last updated
Trust and Data
Read this before you install the CLI: what it sends us, what it never sends, how long we keep it, and where it lives.
The short version
| What we collect | Token counts, the tool, the ticket, who ran it and when. Not your prompts, not your agent’s replies, not your source code. |
|---|---|
| How long we keep it | For the life of your organization. There is no automatic expiry today, and deleting the organization removes all of it. |
| Where it lives | Our database runs in the European Union (AWS eu-west-1, Ireland). A five-minute cache and some supporting providers are in the United States, listed below. |
What the CLI sends
Your coding agent keeps running on your machine, under your own account with its model provider. The CLI tells Source which ticket it is on and what it spent. This is a complete usage report:
POST /api/agent/events
{
"token": "<your CLI key>",
"event": "report",
"sessionKey": "<random id for this session>",
"tokensIn": 18204,
"tokensOut": 3120
}| Your data | Reaches Source? |
|---|---|
| Prompts you type | No. In Claude Code, a local hook scans each prompt on your machine for a ticket reference. Only the reference, such as NS-12, is sent. |
| Your agent’s replies, thinking and tool output | No. |
| Source code, diffs and file contents | No. |
| The agent’s transcript file | No. The CLI reads Claude Code’s transcript on your machine and adds up its usage figures. Only the two totals leave. |
| Ticket reference, tool name, token counts | Yes. Tokens in counts input and cache-creation tokens; cache reads are not counted. Tools other than Claude Code report no counts unless they are passed to the CLI explicitly. |
| Who ran it, and when | Yes. The account the CLI key belongs to, plus start, last-activity and end times. |
| Your IP address | Seen, not recorded on the session. Every request carries one. We use it to rate-limit invalid keys. |
| Comments, tickets and pages your agent writes | Yes, deliberately. Running npx neuvikon comment or pages update stores that text in your workspace, as if a teammate had typed it. If an agent pastes code into a comment, that code is stored too. |
Check it yourself
- The CLI is published as neuvikon on npm, so you can read exactly what runs.
npx neuvikon report --verboseprints the counts it is reporting.npx neuvikon initadds its hooks to.claude/settings.json, in plain view and easy to remove.npx neuvikon logoutdeletes the key from your machine.
Bots are different
Everything above is about agents running on your machine. Bots run from our servers, so they do move content to a model provider. They are off unless your organization adds its own Anthropic API key.
- Sent to Anthropic, under your key: the bot’s instructions, what woke it, and what it reads: tickets, pages, chat and member names. If a project allows bots to work in a connected repository, that repository is mounted into the bot’s session too.
- Stored by Source: the bot’s instructions, any note added to a run, its final answer, what it changed, any error and its token counts. The step-by-step session stays in your Anthropic workspace, under your agreement with Anthropic.
How long we keep it
| Data | Kept |
|---|---|
| Agent session records and token usage | Until the organization is deleted. They stay when a project is deleted or a member leaves, so the organization’s totals do not change retroactively. A departed person appears as “Former member”. |
| Bot run logs | The latest 100 runs per bot, deleted with the bot or the organization. Your Anthropic workspace keeps its own copy until you delete it there. |
| CLI keys | Stored only as a SHA-256 digest and the last four characters. Removed when their owner deletes their account or the organization is deleted. |
| Cached project pages and board columns | At most five minutes. |
| Tickets, pages and other workspace content | Until you delete it. Deleted pages stay in the trash for 30 days first. Full details are in the Privacy Policy. |
An organization’s owner can export everything from its settings, and deleting the organization removes its agent records, keys and bot runs along with its content.
Where it lives
The CLI talks directly to our database provider’s EU endpoint. These are all the providers that process data for Source; the sub-processor page has the full detail. Neuvikon itself operates from Türkiye.
| Provider | What reaches it | Where |
|---|---|---|
| Convex | Account records, workspace content (tickets, pages, whiteboards, comments, attachments), agent session records, audit logs, notifications. | European Union (AWS eu-west-1, Ireland), operated by a United States company |
| Vercel | Request metadata reaching the edge network — IP address, user agent, requested path. No workspace content is stored here. | United States, with a global edge network |
| Polar | Name, email address, billing and tax details, seat count, subscription and invoice history. Card details go to Polar's payment processors and never reach us. | United States and the European Union |
| Resend | Recipient name and email address, and the contents of the message being sent. | United States |
| Upstash | Cached project page text and board columns, held for at most five minutes and keyed by project, never by person. | United States |
| OpenRouter | The title and description of the ticket being rewritten, including any personal data written in them. Nothing is sent unless a person presses the button. | United States and other countries, depending on the model provider |
The legal basis for transfers out of the EEA and Türkiye is set out in section 6 of the Privacy Policy and in the Data Processing Addendum.
Questions
If your security review needs something this page does not answer, write to support@neuvikon.space.