Security and privacy

Runtrace collects software metadata, not developer files.

Runtrace collects the package, version, device, and finding metadata needed for vulnerability management. It does not upload source code, file contents, secret values, shell history, screenshots, or clipboard contents.

Review the data inventory Open the trust center

Data boundary

Collect what the security workflow needs.

The agent reports structured metadata. These categories remain on the Mac.

Secret values, API tokens, private key contents, certificate contents, or .env values.
Source file contents, document contents, screenshots, clipboard contents, shell history, or terminal output.
Full package-lock.json, lockfile, manifest, or script body contents; Runtrace stores dependency metadata and install-script keys only.
Arbitrary command output. Remote scans are structured scan-profile requests, and remediation jobs use fixed package-manager argument arrays instead of shell commands.
Raw enrollment tokens after creation. Stored enrollment tokens are hashed; the raw token is shown once.
Lifecycle phase receipt bodies, enrollment tokens, Keychain values, or local evidence directories. Runtrace retains only the bounded final receipt and phase SHA-256 values.

Collected metadata

Data used to identify and remediate exposure.

Collected fields support inventory, exact-version advisory matching, fleet prioritization, remediation workflow, billing, or audit history.

Device and organization metadata

Identify the enrolled developer device and keep tenant-scoped fleet state current.

Organization slug, device ID, device name, agent version, and check-in/upload timestamps.
Admin-maintained owner, team, and business criticality labels.
Enrollment token usage metadata, device bearer-token authentication state, and last-seen timestamps.

Developer inventory metadata

Identify installed developer software so the hosted service can check exact package versions and return device results.

Package, tool, or binary name, version, ecosystem/kind, source path or filename, and last-observed timestamp.
Per-item identity method and confidence, install scope, package-manager origin, parent package, executable path, file SHA-256, and signing identifiers where available.
Per-item central vulnerability coverage status, checked source/time, package identity, advisory count, and bounded explanation.

Findings and vulnerability metadata

Prioritize remediation by vulnerability, affected package, affected devices, and fix availability.

Finding category, title, severity, confidence, affected path or package, evidence summaries, and remediation text.
Advisory identifiers, aliases, CVSS score/vector, installed version, fixed version, CISA KEV status, FIRST EPSS score/percentile, and authoritative malicious-package evidence when available.
Workflow status, admin notes, actor, and timestamps for fixed, accepted-risk, and false-positive decisions.

Remote scan, remediation, and report metadata

Audit remote scans and allowlisted package updates, then produce weekly security reports without arbitrary remote execution.

Remote scan profile, selected custom roots, configured scan caps, reason, requester, status, timestamps, result, and error summary.
Structured remediation action type, package and target version, affected device and vulnerability, approval reason, lifecycle timestamps, exit status, verification result, and bounded error summary.
Active scanner policy pack ID/name, scheduled home-relative workspace roots, upload-path preference, EndpointSecurity flag, and sensitive path rule patterns.

Billing and session metadata

Gate Business and Enterprise features and keep the account auditable.

Plan, billing status, seat limit, active device count, current period, Revolut customer/subscription identifiers, and webhook event IDs.
Business workspace request contact metadata: company name, requester name, work email, seat estimate, notes, status, and admin follow-up note.
OIDC subject, email, roles, allowed organization claims, session expiry, and CSRF-protected admin form metadata.

Product controls

Bounded access and auditable actions.

Organization-scoped enrollment and per-device authentication
Role-based administrator access with server-side sessions
Structured remote scan profiles with local validation and fixed limits
Tenant-scoped policies, allowlists, and audit history
Telemetry validation before findings are stored
Organization export and controlled deletion workflows

Documentation

Information for security and privacy review.

Security review

Review the data boundary before deploying the agent.

Request a demo View pricing