A cyanotype print, seen from above: an open card-catalogue drawer of ruled index cards on a desk, with an ink pad and a rubber stamp beside it.

Can you prove what each AI vendor keeps?

Owin answers the AI section of a buyer’s security questionnaire for every endpoint you run, from each vendor’s own page, with the vendor’s sentence behind every answer.

Try it Open the app

I built Owin because a buyer’s security questionnaire asks whether your AI providers keep customer data, and the true answer differs per endpoint.

For the founder or CTO of a 2 to 50 person B2B SaaS team, answering an enterprise buyer’s security review with the vendor pages open in other tabs.

A cyanotype print on a desk: one blank ruled index card with rounded corners and a punched hole.

The finding,
on real vendor text

  1. Your trust page says “zero data retention”. Lumen Notes wrote answer 3 on September 1, 2026, and listed one exception.
  2. One endpoint calls a feature ZDR does not cover. /api/crm-sync writes call summaries into the customer’s CRM through Anthropic’s MCP connector.
  3. Owin reads Anthropic’s own page. Three readings, and the quote is checked word for word against the page it came from.
  4. Answer 3 is not true for /api/crm-sync. It holds for 3 of 4 endpoints. Owin drafts the fix; you send it.
/api/crm-synccalls Anthropic · MCP connector
Question 3 Not true

Do you have zero data retention with your AI providers?

Your answer · September 1, 2026

“Yes. We use zero data retention with our AI providers. Exception: nightly digests (/api/digest) use Anthropic Message Batches, kept up to 29 days.”

“The MCP connector is not covered by ZDR arrangements.”
Anthropic, MCP connector docs · fetched 2026-10-21 21:23 EDT

Five statuses.
None of them is a guess.

Plain code picks the status from the vendor’s own page. Each status has its own frame, so it reads without colour too.

Not true

Your answer and the vendor’s sentence disagree.

Answer 3 for /api/crm-sync: “The MCP connector is not covered by ZDR arrangements.”

Outdated

The page your answer rests on changed after you wrote it.

Answer 5, written September 1: OpenAI updated its sub-processor list on October 14, 2026.

Needs review

Owin’s three readings disagree, so it asks you instead of picking a side.

OpenAI Responses, who else sees the data: two readings say third parties do, one finds nothing stated.

Not stated

The page says nothing on it, so the answer is marked not stated, never invented.

Anthropic’s rate-limits page has no data-use terms: every field for that endpoint is marked not stated.

Verified

The vendor’s sentence still supports your answer.

Point /api/crm-sync at Anthropic’s Messages API, and answer 3 holds again.

A cyanotype photogram: the white shapes of an index card with a punched hole, a rubber stamp seen from above, paper clips and a catalogue rod on Prussian blue.

Nemotron reads.
Plain code decides.

  1. Tavily fetches each vendor page whole. With its fetch time, hash and “Last updated” date, so Outdated is a dated observation, not a hunch.

    Vendor page

    platform.claude.com/docs/en/agents-and-tools/mcp-connector

    Fetched
    2026-10-21 21:23 EDT
    By
    Tavily extract
    Text
    31,051 characters
    sha256
    248e3bd6e879df41…
  2. NVIDIA Nemotron 3 Super reads it three times. The open-weight model on Nebius Token Factory turns the page into fields with one quote each, and every quote is checked against the page word for word.

    Zero data retention · three readings

    • First readingnot coveredquote found word for word
    • Second readingnot coveredquote found word for word
    • Third readingnot coveredquote found word for word

    3 of 3 agree, so Owin answers.

  3. Plain code decides. An answer is filled only when every successful reading agrees, at least two of them; otherwise it goes to a person. A test feeds model prose into every status, and nothing moves.

    The rule, for /api/crm-sync

    You said
    zero data retention
    Anthropic says
    not covered by ZDR

    Not true

  4. Your buyer gets a read-only report. PDF, CSV or link, with the vendor’s sentence, link and fetch time behind every answer, and none of your internal notes.

    Buyer report · read-only

    Do you have zero data retention with your AI providers?

    /api/crm-sync Not covered by ZDR

    “The MCP connector is not covered by ZDR arrangements.” platform.claude.com · fetched 2026-10-21 21:23 EDT

    PDFCSVLink

It answers when its readings agree.
When they don’t, it asks you.

On 7 AI vendors, 6 of them new to Owin: 11 features on 8 pages, with labels committed before the prompt was written. On the 6 answers it handed over, a majority vote would have been right only 2 times.

Recompute itowin eval selective --corpus datause --split v3freshAsk this server nowEvery number, with its source

Split v3fresh · 33 answers

Filled on its own27/33
Right, of those26/27
Handed to a person6

What we’ll tell you
before you find it

  • The demo company is fictional. Lumen Notes and its settings are invented. Every vendor sentence, link and fetch time is real.
  • One labeller, no human audit yet. An AI coding agent labelled every item; a second pass spot-checked. We kept the one label error we found, because labels were pre-registered.
  • Re-fetches run on a schedule you set. Owin re-fetches every watched vendor page, daily at 06:00 UTC by default when a Tavily key is present. The live demo’s recorded numbers don’t change.
  • Owin is not legal advice. It quotes vendors and compares answers; it does not tell you what you may do.
A cyanotype print of a card-catalogue drawer full of index cards, with a rubber stamp lying on loose cards in front of it.

Answer the AI section with the vendor’s own words.

Try it Open the app Source on GitHub