AI TOOL TRACKING / SECURITY

Security by design. Visibility with boundaries.

AI oversight should reduce your exposure, not create a new store of sensitive documents. These principles guide the production platform we are building.

Product development status
This is a product preview. The controls below are production requirements and design commitments, not claims of completed certification or currently deployed protections.

Inspect locally. Share the finding.

The intended default is local document inspection with only metadata, detector identifiers, match counts, and redacted evidence sent to the service. Full file and prompt retention are excluded from the default event schema. Unsupported or unreadable content must be marked uninspected.

Keep identity and access explicit.

The production service will require tenant isolation, Entra ID sign-in, least-privilege access roles, and an audit trail for analyst actions. Device enrollment and event ingestion will use device-bound credentials with revocation and rotation. These controls must pass verification before customer data is accepted.

Show what the evidence can support.

A file read or an AI connection alone does not establish that a document was uploaded. Events will distinguish confirmed observations, correlated signals, inferred activity, and unavailable content. Detection confidence and action confidence are separate.

Build a small, testable endpoint component.

The planned Windows architecture combines a managed browser adapter, a user-mode classification service, and narrowly scoped kernel telemetry. File parsing and PII detection remain outside the kernel. Signing, memory-integrity compatibility, upgrade rollback, and stress testing are release gates.

Respect organizational boundaries.

Monitoring is intended for enrolled organizational endpoints with administrator deployment and clear employee notice. Collection scope, retention, exclusions, and access to identifiable data must be configured before rollout. The product is not designed for covert employee surveillance.

Today’s demo

The demo contains fictional records. It does not inspect your files, read your browsing activity, connect to Microsoft 365, or install an agent. Demo policy and incident changes are stored in your browser only; you can reset them in Settings.

No unearned badges.

We do not currently claim SOC 2, ISO 27001, or any compliance certification. Security documentation, assurance evidence, service commitments, and contractual terms must be finalized for a production pilot.

Explore the development roadmap →
A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope

This creates a planning document. It does not enroll devices or submit a request.