For the company being read

An investor asked you to connect Zoe. Read this first.

This is one of the lighter asks you will get in a diligence process, and one of the fastest. A few read-only connections, one call, and the investor has what they need. Here is what you accept before anything connects, what Zoe reads, what she can’t, and what you keep control of. Written for you and your security or legal reviewer.

01

The short version

Message bodies are never stored.

From the systems you connect, Zoe reads the shape of activity: who talked to whom, how often, how fast, and when that changed. Not what was said in Slack. Not one message body, not one line of source. The one exception is what is placed in the case on purpose: your pitch deck, any data-room files, and the Founder Call transcript, which Zoe reads to build and test the Claim Ledger.

02

Your controls

You accept it. You grant it. You revoke it.

It starts with a signed link from the investor. You are shown the DPA before anything connects, and your acceptance is logged as a consent event you can point to later. Every connector is then a separate read-only OAuth grant you make in your own session and can withdraw at any moment, without breaking the others. Credentials never leave your systems.

03

After the deal

Sealed, then a certificate.

When the investor closes the case it is sealed, and normalized metrics are destroyed 30 days later, whether or not the deal closes. You receive the destruction certificate directly. If the investor keeps monitoring after close, it runs only on grants you still hold and can revoke.

In one look

From your systems: the shape of activity, never the content.

Zoe reads from your systems

  • Who talked to whom
  • How often, and how fast
  • When that changed

Zoe never stores from your systems

  • Message bodies
  • Documents
  • Source code

Before you connect

A checklist for your security reviewer.

  1. 01Open the signed link and read the DPA

    The invite comes from the investor through Zoe. The DPA is shown before anything connects, and your acceptance is logged as a consent event on the case.

  2. 02Confirm which connectors are in scope

    You choose. A diagnostic runs on four of six as readily as six of six. Coverage is reported rather than assumed, and the score carries a confidence percentage and a coverage tier.

  3. 03Have your admin make the grants, not the investor

    Each grant is a read-only OAuth consent from your own admin console, in your own session. Credentials never move and the investor never sees one.

  4. 04Read the per-connector table with your reviewer

    One canonical page lists what Zoe reads, what she never stores, retention, and revocation for each source, plus how the deck, data-room files and call transcript are handled.

  5. 05Note the Slack line explicitly

    Message bodies are never stored. If your counsel needs that in writing beyond this page, ask and it goes in the agreement.

  6. 06Expect the Founder Call

    Once your books are connected, Zoe checks the deck against them and turns the gaps into questions. Your founder or CEO answers them on a call with the investor; the transcript is scored as answered, dodged or contradicted. Prepare for it like an IC.

  7. 07Agree what happens at close

    Seal, with a 30-day destruction certificate to you, or continued monitoring on grants you can revoke.

  8. 08Keep the revocation path open

    Any connector can be withdrawn mid-diagnostic without breaking the others. The readout then reports reduced coverage.

Full per-connector data-handling table →