Public content, reviewed by people, with a paper trail.
This page is written for the compliance officer or procurement lead who has to sign off. Send them the link.
What the data is
Transcripts of executives speaking on the record in public settings: podcasts, broadcast and streamed interviews, conference keynotes and panels, earnings commentary, and public forums. Each record carries the speaker, their company and title at the time, the date the statement was made, a timestamp for every turn, and a link to the original public source. We also index public newsletter posts from Substack as a clearly labeled secondary source.
Public by construction
Every record originates from content the executive chose to give publicly and that remains publicly accessible. We do not record calls, ingest private communications, scrape paywalled content, or accept user uploads into the shared corpus. Where a source is later removed by its publisher, the record is flagged and withdrawn from the product.
No personal data
The corpus consists of professional statements by public figures made in public. It contains no personal data in the GDPR or CCPA sense: no contact details, no financial or health information, no private individuals. Executive profiles hold name, employer, title, and a public headshot only. Our own customer records (account email, billing through Stripe) are covered by the privacy policy and are never mixed with the corpus.
No material nonpublic information, by construction
Because every statement was made publicly, on the record, and is linked to its public source, the corpus cannot contain material nonpublic information. Human reviewers additionally screen each record for anything that appears to be nonpublic, and any such record is withheld and escalated. The product surfaces what was said publicly, when, and where, so a compliance team can verify any quote against the source in seconds.
Review workflow
- Automated sourcing and model pre-vettingSpeaker-source match and relevance checks before anything enters the pipeline.
- Human review on every recordConfirms the named executive is the one speaking; screens for personal information, apparent nonpublic information, dubbed or synthetic audio, and secondhand commentary.
- Provenance and datingSource link and per-turn timestamps retained. Appearance date resolved from the content, so statements are never misdated to an upload.
- Issue handlingCustomers flag a record from the app or by email. Flags are triaged within one business day; confirmed issues are corrected or withdrawn and the change is logged.
Security basics
- All traffic over HTTPS. Sessions and API keys are revocable from the account page.
- Payments processed by Stripe. We never see or store card numbers.
- API access is per key, rate limited, logged, and scoped to the plan.
- Production data lives in managed PostgreSQL on DigitalOcean with encrypted backups.
- Client watchlists and portal configurations are private to the client.
Procurement
We can provide
Vendor due-diligence questionnaire responses, a security questionnaire, W-9, invoice or purchase-order billing, a data dictionary, and a written description of the verification pipeline for your methods section or vendor file.
Typical timeline
Universities: same-day invoice. Funds: DDQ returned within five business days, redlines on an annual license within two weeks. Trial access can run in parallel.
Contact
Compliance and procurement questions: [email protected]. Commercial: [email protected], or book a 20-minute call.
Last reviewed September 2026. This page describes our practices and is not legal advice.