A security tool should be the easiest thing on your machines to trust. Here is exactly what Tracknosis does on a Windows machine, where its results live, and what, if anything, leaves the machine.
Tracknosis reads the file system and registry directly from the disk. It doesn't modify the files and registry keys it examines.
Scan history is kept in a local database on the machine running Tracknosis. There is no Tracknosis cloud and no telemetry sent to us.
Data leaves the machine only through integrations you switch on yourself: sending findings to your Splunk, or drafting a report with AI.
Tracknosis doesn't copy the contents of your documents into its database.
Scanning itself needs no network connection. These optional features do, and each one runs only when you turn it on or click it.
When you enable it, findings are sent to your own Splunk HTTP Event Collector. The collector token is encrypted with Windows data protection (DPAPI) for the user who saved it, not stored in plain text.
When you ask for an AI report draft, the change data selected for that report is sent to the AI provider (Anthropic's Claude API) using your organisation's own API key. Nothing is sent unless you generate a draft. The draft is for your team to review before it goes anywhere.
If you choose to update them, Tracknosis downloads public reference lists (IP location, Tor and VPN ranges) to label network connections. These are downloads only: no data from your machine is sent.
If you click to look up a file online, its hash (a fingerprint, not the file itself) is opened in your browser on VirusTotal. This happens only when you click.
We're happy to go through your questionnaire, walk through how Tracknosis handles data on your machines, or run it with you on a test system first.