See what's downstream of your data.
Openwake discovers the vendors, AI services and agents your organisation actually uses, keeps a cited record of what they promise about your data, and shows you when those relationships change or act outside policy.
Free for five vendors. No password, no card. Sign in with Google, Microsoft or an email code. Agents ask over MCP.
One relationship. Four kinds of truth.
Every vendor, AI service and agent that touches your data is a relationship. Openwake keeps four kinds of truth about it and shows you when they stop agreeing.
Their privacy policy, DPA, AI terms and subprocessors, quoted and dated.
The applications, browsers, APIs and agents that actually reach them.
Material changes, the potential objection window, the impact on you.
Which agent sent which data class where, and whether policy allowed it.
The MSA, DPA and addenda you signed, compared with the three truths above.
Not a document diff. A Finding.
Anthropic PBC added as a model provider under Notion AI. Notion's own subprocessor page, read this morning.
- 31 active users
- 24 endpoints
- 3 agents
- customer content observed
- 30-day subprocessor objection provision
- AI processing: permitted
- Training: prohibited
- 27 days remaining*
- *from the day the change was posted
Registry found the change. Scout knows you use Notion. Agreements knows your DPA. Recorder knows your agents send customer content there. Openwake connects them.
Each answers one question.
Openwake Registry
A public, versioned record of third-party data practices. Every material claim links to the clause it came from, with the URL and the date it was read.
Explore the Registry →Openwake Watch
Openwake re-reads vendor policies, DPAs, AI terms and subprocessor lists every day and turns meaningful changes into Findings you can act on.
Explore Watch →Openwake Scout
Discover the SaaS, AI services and external relationships actually present on endpoints, in browsers and in identity systems, without reading anyone's content.
Explore Scout →Openwake Agreements
Upload the agreements you signed and compare what the vendor committed to against its current public declarations and your observed usage.
Explore Agreements →Openwake Recorder
Record agent delegation, tool actions, external destinations, data classes and policy outcomes, without retaining prompts or tool payloads.
Explore Recorder →Follow the relationship downstream.
Pick a class of data and see every third party that can reach it, through which application, which agent, and which processor underneath.
- Customer content
- Notion
- OpenAI
- Anthropic changed this week
- HubSpot
- Amazon Web Services
- helpdesk-agent agent
- Notion
- Notion
Agents don't stop at your network boundary.
One agent delegates to another. That agent invokes a tool. The tool reaches a vendor. The vendor routes data to a model provider. Openwake keeps the chain connected, from intent to outcome.
- Maxdelegated
- Procurement agentrequested a quote
- CSP agentqueried
- Distributorpricing API
- Microsoft licensingquote returned
Recorder records who acted for whom, what was delegated, the tool, the destination and the data class. Never the arguments, never the results.
The clause changed. Your contract didn't.
Vendors add AI features without changing contract language. A new subprocessor appears on a web page, not in your inbox. The window to object runs from the day they posted the change, not the day you noticed.
Subprocessor added
A model provider appears under a vendor you use. Openwake quotes the line, dates it, and starts the potential window.
AI training terms changed
"We may use customer content to improve our services" is one sentence in a 9,000-word policy. Openwake shows the before and after.
Notice window started
Openwake compares what changed against the agreement you actually signed, and drafts the objection you can send as-is.
Declared. Contracted. Observed. Inferred.
Every fact in Openwake says where it came from, and the kinds are never mixed. "Does Notion train on our data?" is never answered with a bare no.
The vendor said it, in a cited public document.
Your executed agreement says it.
Openwake directly saw it: Scout, Recorder, a connector.
Openwake derived it, with a confidence you can see.
Every check and every change produces a signed receipt that anyone can verify with the public key alone. You don't have to trust Openwake to verify Openwake evidence.
Every profile public. Every fact cited.
Each fact carries the clause it came from, the URL, and the date we read it. Search all 112 vendors.
See relationships, not employee content.
Openwake Scout
Chrome → Claude
node → Anthropic API
VS Code → GitHubCollects: application, vendor, timestamp, first and last seen, the relationship.
Never collects: page content, passwords, keystrokes, screenshots, prompts, clipboard.
Openwake Recorder
helpdesk-agent
→ WRITE
→ Notion
→ customer_content
→ allowedRecords: the semantics of a call: who, what action, where, which data class, the policy result.
Never records: arguments, results, prompt bodies, credentials.
Free covers five vendors. Your company runs forty.
Checking a vendor is free for everyone, including agents over MCP, and stays that way. Paid plans watch your whole list, alert where your team already is, add Scout, Recorder and single sign-on, and export into the tool your auditor reads.