Sayli runs in rooms where the conversation is the work. We built it the way we would want a tool used in our own calls. This page is precise on purpose. It says what we do and what we do not, with no weasel words.
What we record
We record the transcript of your call and the brief we write from it. Both are scoped to your organization and to your visibility settings. That is what makes Sayli useful, and it is all we keep to do the job.
What we never do
We never send a bot into your meeting. Sayli is invisible on screen share at the operating-system level, so the host sees no extra participant and no recording banner.
We never train models on your data. Our AI processors are bound by terms that prohibit training on customer data; see the named subprocessor list. We never sell your data.
Redaction at ingest
Before any text is stored, shown, or read by the language model, Sayli redacts the sensitive parts. The model sees the conversation, not the secrets inside it.
Where your data lives
Your data runs on cloud infrastructure (Google Cloud). Sayli relies on a small set of subprocessors: speech-to-text, language-model inference, embeddings, vector search, cloud infrastructure, email delivery, billing, analytics, and error reporting. The canonical, named list, with what each one sees, is at Subprocessors. The full security posture, including what we do not have yet, is at Security overview.
Recordings
Sayli can keep a recording so you can hear any moment again. The recording is tied to your account. It is never used to train models, and you can delete it.
Retention and deletion
You can delete a meeting. The delete cascades, so the transcript, the brief, and everything derived from them go with it. When data is gone, it is gone.
Tenant isolation
Every query is scoped to your organization by the data model itself, not by convention. There is no code path for one organization to read another's data.
Where HIPAA stands
Sayli is not HIPAA-compliant today, and we will not pretend otherwise. No business associate agreement exists with us or with any of our vendors. The product has a per-organization HIPAA mode that reroutes language-model traffic to a dedicated endpoint and turns off product analytics, but speech-to-text and embeddings still use our standard processors, so it is not a compliant path. A dedicated compliant inference plane is on the enterprise roadmap. If you handle PHI, talk to us before using Sayli: enterprise@sayli.ai.
Sign-in and SSO
Sign in with Google or Apple today, or with a passwordless email link. SAML single sign-on and SCIM provisioning are on the enterprise roadmap.