How it holds up.
Plain prose. No badges, no seals, no compliance logos. Anything not confirmed appears here as an open item rather than as a claim.
Storage
Transcripts and reads live in the workspace they were created in, encrypted at rest. API keys are held in a vault the application layer cannot read back; it can use a key, it cannot print one.
Deletion
Deleting a call removes it and its reads from your workspace immediately, and from backups within 30 days. That includes the recording, the transcript, every claim derived from it, and the verdicts it contributed to a person's file.
Model training
Your calls never train our models. We use third-party models under zero-retention terms — named on this page, changed only with notice.
Consent and provisioning
Access is invite-only. Every workspace is provisioned by a person, not a form. Reads are produced from calls you supply; nothing is ingested from your calendar or inbox without an explicit connection you make yourself.
Subprocessors
[SUBPROCESSOR LIST — CONFIRM: database and auth host, model provider, transactional email when live, application hosting. Listed by name and purpose once confirmed.]
Analytics
No third-party trackers, no fingerprinting, no advertising pixels. Any measurement is first-party page counts.
Contact
[CONTACT — CONFIRM]