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.
- 01
Consent before access
- 02
Zoe only reads
- 03
Revocable per connector
- 04
Message bodies never stored
- 05
Deleted with the workspace
Per-connector data handling
One table. Every connector. No exceptions in the footnotes.
| Connector | Zoe reads | Retention | Revocation | Never stored |
|---|---|---|---|---|
| Profit and loss, balance sheet and cash-flow totals, revenue by customer, AR aging buckets, open bills, expense category totals | Deleted with the workspace | Instant, in QuickBooks | Individual transactions, invoice and bill line items, customer details beyond the company name, payroll records, bank credentials | |
| Deal-stage transitions, pipeline timestamps, deal owner changes | Deleted with the workspace | Instant, in HubSpot | Contact records, company records, email bodies, call recordings, notes | |
| Account concentration, renewal dates, owner history | Deleted with the workspace | Instant, in Salesforce | Opportunity notes, attachments, contact records | |
| Commit and PR cadence, review latency, deploy frequency | Deleted with the workspace | Instant, in GitHub | Source code, diffs, commit message bodies | |
| Cycle time, reopen rate, work-in-progress age | Deleted with the workspace | Instant, in Jira | Ticket descriptions, comments, attachments | |
| Channel graph, response latency, cross-team edges, message text in public and private channels, scored and then dropped | Deleted with the workspace | Instant, in Slack | Message bodies, DMs, file contents |
Uploaded material
What Zoe reads in full, because you gave it to her to test.
| Material | Zoe reads | Storage | Deletion |
|---|---|---|---|
| Pitch deckClaim Ledger | Read 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 workspace | Deleted with the workspace |
| Data-room PDFs and CSVsEvidence | Read to support or refute claims in the ledger. Optional; the deck is the only required upload. | Stored encrypted in the diagnostic’s workspace | Deleted with the workspace |
| Company Call transcriptScored answers | Read to score each answer as answered, dodged, or contradicted against the ledger. | Stored encrypted in the diagnostic’s workspace | Deleted with the workspace |
Security Scorecard
What we have, and what we don’t yet.
SOC 2
Readiness, not certified
Controls are in place and being evidenced; Type 1 is a future milestone. We won't say certified before it is.
Data residency
US
US-first. We don't claim an EU posture we haven't built.
Deletion
With the workspace
Zoe stores synced records and diagnostic evidence. Delete the workspace and Zoe deletes its data and revokes its grants.
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 →
QuickBooks
HubSpot
Salesforce
GitHub
Jira
Slack
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.