Security & data handling

Written down, per connector.

Systems are read for behavior. Uploads are read for claims. Disconnecting a system stops its reads, and deleting the workspace deletes its data and revokes its grants.

Per-connector data handling

One table. Every connector. No exceptions in the footnotes.

ConnectorZoe readsRetentionRevocationNever stored
QuickBooksFinancecom.intuit.quickbooks.accountingIntuit publishes no read-only accounting scope. Zoe requests this one, reads the statements above with it, and writes nothing back.Profit and loss, balance sheet and cash-flow totals, revenue by customer, AR aging buckets, open bills, expense category totalsDeleted with the workspaceInstant, in QuickBooksIndividual transactions, invoice and bill line items, customer details beyond the company name, payroll records, bank credentials
HubSpotCRMcrm.objects.deals.readDeal-stage transitions, pipeline timestamps, deal owner changesDeleted with the workspaceInstant, in HubSpotContact records, company records, email bodies, call recordings, notes
SalesforceCRMapi refresh_tokenscope pendingAccount concentration, renewal dates, owner historyDeleted with the workspaceInstant, in SalesforceOpportunity notes, attachments, contact records
GitHubEngineeringmetadata:read contents:read pull_requests:readscope pendingCommit and PR cadence, review latency, deploy frequencyDeleted with the workspaceInstant, in GitHubSource code, diffs, commit message bodies
JiraEngineeringread:jira-workCycle time, reopen rate, work-in-progress ageDeleted with the workspaceInstant, in JiraTicket descriptions, comments, attachments
SlackCommunicationschannels:read channels:history groups:read groups:history users:readChannel graph, response latency, cross-team edges, message text in public and private channels, scored and then droppedDeleted with the workspaceInstant, in SlackMessage bodies, DMs, file contents

Uploaded material

What Zoe reads in full, because you gave it to her to test.

MaterialZoe readsStorageDeletion
Pitch deckClaim LedgerRead in full to extract every claim into the Claim Ledger, one row per claim, then checked against the connected systems.Stored encrypted in the diagnostic’s workspaceDeleted with the workspace
Data-room PDFs and CSVsEvidenceRead to support or refute claims in the ledger. Optional; the deck is the only required upload.Stored encrypted in the diagnostic’s workspaceDeleted with the workspace
Company Call transcriptScored answersRead to score each answer as answered, dodged, or contradicted against the ledger.Stored encrypted in the diagnostic’s workspaceDeleted with the workspace

Security Scorecard

What we have, and what we don’t yet.

For the company being read

You’re the one granting access. Here’s exactly what that means.

If an investor has asked you to connect Zoe, you will get a signed link. Open it, read the DPA, and accept it; the acceptance is logged as a consent event. Then connect each system in your own session. Zoe only reads, though the permission a provider grants can be broader than what Zoe reads. The investor never sees a credential. The decision is yours: disconnecting a system stops future reads, and Zoe also asks the provider to revoke its access. Message bodies are never stored.

Prepare for diligence →
Your grantsZoe only reads
  • QuickBooksRevoke
  • HubSpotRevoke
  • SalesforceRevoke
  • GitHubRevoke
  • JiraRevoke
  • SlackRevoke

Each grant is separate. Revoking one doesn’t break the others.

Inspect the controls

See how the diagnostic handles company data.

Review the access model, evidence trail, and boundaries before you invite a company.

Rather not wait? Start a diagnostic, add the company’s deck, invite the company to connect, and receive the Deal Package inside 24 hours.