Overview

What sensitive data is leaving for AI tools — even on the personal accounts your vendor consoles can't see — and what AI content is coming back in.

Full capture
8 active, all acknowledged
Last capture 8m ago · 90-day retention
Needs attention

  • An AI-origin figure reached 5 destinations across 3 users — trace it before it ships again.

    Trace

  • 5 AI-origin items awaiting attestation.

    Review

  • 12 sensitive submissions to AI tools flagged (3 redacted, 9 warned).

    Triage
Live activity
Prompt monitored2d ago
ChatGPTmorgan.reyes@acme.com
Sensitive data warned3d ago
ChatGPTbianca.okafor@acme.com
Sensitive data redacted before send3d ago
ChatGPTbianca.okafor@acme.com
To AI
data leaving for AI
View
Sensitive submissions
0
of 29 captured · 3 redacted, 9 warned
Distinct AI tools
0
16 accounts · 5 personal / 11 corp
From AIProvenance
where AI content lands
View
AI-origin content
0
traced into real work
Destinations reached
0
places AI content landed
Pending attestations
0
awaiting acknowledgement
Cross-user spreads
0
A generates → B reuses
Trace a claim

Search a phrase or figure across the captured AI-response corpus and follow it to every place it surfaced.

Open From AI
Compliance & Evidence

Built so your next cyber-insurance questionnaire and SOC 2 review answer themselves. Export an evidence pack, not screenshots.

Open Compliance
Activity over time
To AI From AI
Finish setup
3/5
Verify domain (DNS‑TXT)1 domain still pendingDeploy the extension to managed ChromeConfigure employee monitoring noticeInvite your teaminvites outstandingCollect notice acknowledgements