What Omnodex Can See
What your agents do (prompts, tool calls, parameters, commands, file paths, hosts and detection findings) is end-to-end encrypted. It is encrypted on your machine, and only your machines and your signed-in browser hold the keys. Running the service still needs some data we can read. This page lists all of it. When another page says we cannot read your data or that we store only ciphertext, it means everything except what is listed here.
If you never connect a machine to the hosted dashboard, none of this applies. Recording and local analysis make no network calls. The CLI checks the public npm registry for updates in the background (turn this off with OMNODEX_NO_UPDATE_CHECK=1), and plugin bundles download from downloads.omnodex.com when you install them.
Your account
Section titled “Your account”| What | Why | Kept |
|---|---|---|
| Email address | Signing in and account email | While the account exists |
| IP address and browser user agent of each dashboard sign-in | Recorded with the sign-in session, for investigating account misuse | Until you sign out or the session expires (at most 30 days) |
| IP address of requests to sign-in, sign-up, password reset, waitlist and invite pages | Rate limiting | For the rate-limit window, at most one hour |
| Plan and subscription status | Billing. Payment details are held by Stripe, not by us | While the account exists |
Each connected machine
Section titled “Each connected machine”| What | Why |
|---|---|
| Machine ID: 16 random hex characters, generated once on the machine | Keeps each machine’s data apart in the dashboard. It says nothing about the machine |
| Once, on a machine that synced with an older version: its old machine ID, which was derived from the hostname | Moves that machine’s data to its new ID, so it keeps its history |
| Size and arrival time of each encrypted upload, and the hour of its latest activity | Storage, plan limits, and deleting it on schedule |
| Random IDs of uploads and live events, when each live event was sent, and which key encrypted it | Delivery, dropping duplicates, and expiring old live events |
| A check value derived from the stream secret | Catches a wrong secret. It cannot be turned back into the secret or a key; see Encryption |
| If your account has a finding policy: each stream’s copy has a version number, a save time, a size and the account that saved it, and a machine sends the version it already holds | Lets a machine skip a policy it already has, and stops two dashboards overwriting each other’s saves. The entries themselves are encrypted |
Some names travel with this metadata but stay encrypted, so we can’t read them: the machine label you set, the agent platform and project name a connection link carries, and the name you give a stream. They are encrypted under the stream secret, on the machine or in your browser, and only the dashboard decrypts them. Agent session IDs travel only inside the encrypted data.
Encrypted data and the metadata stored with it are deleted on the schedule in Data Handling.
Monitoring status
Section titled “Monitoring status”On the Hosted plan and above, a connected machine reports how its monitoring looks about every 15 minutes while an agent or the Omnodex plugin is running, and sooner when that changes. The report keeps coming while uploads are paused, so an agent can’t hide removing Omnodex by pausing sync first. See Monitoring status.
| What | Why |
|---|---|
| For each agent platform: whether Omnodex’s hooks, plugin and MCP entry are in place, whether the agent’s hooks are switched off, how many installations were checked, and whether a session its hooks recorded is open | Shows when monitoring was removed or switched off |
| Whether recording or uploads are paused, and whether any agent session is open | Tells a pause or an idle machine apart from missing monitoring |
| The Omnodex CLI version | Shows which version was monitoring at the time |
| How many unexplained monitoring changes the machine recorded since its last report | Counts changes to monitoring that no Omnodex command made |
| When the report was made and, after the machine was offline, when it went offline | Tells a gap in reports apart from a machine that stopped reporting |
The service keeps the latest report for each machine, and a record each time a platform’s monitoring state or the CLI version changes. Those records are kept for 180 days, except each platform’s current state. A machine that hasn’t reported in 180 days is dropped.
None of this includes paths, commands, tool names, parameters or conversation content.
Counts
Section titled “Counts”| What | Why |
|---|---|
| In shadow and guardrails mode, and when you agree to count your actions on findings: a day, a rule ID, a kind such as “would block” or “mute”, and a number | Tuning the rules. See Rule Counts |
| On Pro: per day, how many tool calls Pro rules checked and how many findings they raised | Billing |
| License checks | Confirming your plan |
None of these include tool names, paths, commands, hosts, parameters, credentials or conversation content.
The network
Section titled “The network”Cloudflare hosts the service and, like any web host, sees the IP address of each request your machine and browser make. All requests use HTTPS.
Checking this list
Section titled “Checking this list”The Omnodex client is open source. Its repository includes a test that lists every field the client sends to the hosted service and fails when a new readable field appears that is not on its list, so a change to what we can see shows up in review. This page is updated in the same change.