Trust Centre
Data Handling & Retention
What we hold, where it lives, who can see it, and for how long.
What we hold
Account and sign-in data; meeting audio, transcriptions, and metadata; AI-generated output such as summaries, action items, and draft observations prepared for advisor review; and security/audit data such as immutable access logs and consent records.
Where it lives
Customer data is stored and processed in infrastructure located in the European Union. Audio and object storage are S3-compatible; the database is PostgreSQL with the pgvector extension. Data is encrypted at rest with AES-256 and in transit with TLS 1.3.
Who can see it
Access is tenant-scoped and enforced with PostgreSQL row-level security, with workspace-level boundaries layered on top for memory retrieval. Authentication uses OpenID Connect (Google, Microsoft 365). Every meaningful access is written to an append-only, hash-chained audit log.
For how long
Retention is configurable per tenant and governed by your settings, contractual terms, and applicable legal obligations. When data is no longer needed, it is deleted or anonymised. Specific retention periods are defined in customer agreements rather than stated as universal constants here.
Who processes it on our behalf
A bounded set of sub-processors handles meeting capture and transcription. See the Sub-processor List for the current register and its publication status.
Sub-processor List
A bounded set of sub-processors handles meeting capture and transcription. See the Sub-processor List for the current register and its publication status.
Sub-processor List