Security
Your calls are your business.
Sayli hears only the calls you start it on, keeps them in your workspace, and shows them only to the people you choose. Here is exactly how.
At a glance.
The six things a security review asks first.
Nothing joins your call.
Sayli hears your computer's audio. No bot, no invite, no roster entry.
Hears nothing until you start it.
It can notice a call begin. It listens only after you press Start.
Private by default.
A new call is visible to the person who took it and workspace admins.
Encrypted in transit and at rest.
Stored on Google Cloud in the United States, in us-central1.
Isolated per organization.
Enforced in the data model. One workspace cannot read another.
A log nobody can edit.
Every change in a workspace is recorded, and admins can export it.
What Sayli hears
Sayli runs on your computer and listens to the audio it already plays and records. Nothing is added to the call: no bot, no participant, no chat message, no change to the invite.
It can notice that Zoom, Google Meet, Microsoft Teams or Webex has started and offer to listen. It hears nothing until you start it, and the first offer carries a button to turn detection off.
Who can open a call
Every call starts Private: only the person who took it and the owners and admins of the workspace can open it.
Sharing is a choice per call. Team opens it to members with a Member role or higher. Org-wide opens it to everyone in the organization, including view-only members.
Enterprise workspaces can turn off public links for the whole company.
Where it is kept, and for how long
Content is stored and processed in the United States, in Google Cloud's us-central1 region, encrypted in transit and at rest. Recordings sit in private storage and open through short-lived signed links.
Recordings are kept so you can hear any moment again. Delete a meeting and its audio goes with it. Delete your account and your meetings, recordings, transcripts, briefs and knowledge leave the live service in one step.
Encrypted backups can hold deleted data for up to 35 days before they are overwritten. Enterprise workspaces set how long their data lives.
Accounts and sign-in
There are no passwords to leak. People sign in with Google or Apple, or with a one-time code.
Access tokens are short-lived and refresh tokens rotate. Sign-in and other sensitive endpoints are rate limited.
AI and the providers that process your data
We do not train our own models on your meetings, and we do not sell your data.
Speech to text and the language models each have a primary provider and a fallback, all in the United States and bound by the same terms, so a call keeps working if one is unavailable.
Business customers, and anyone evaluating Sayli under a mutual NDA, can get the current list of providers, what each one processes and where it runs, from privacy@sayli.ai. We give at least 30 days notice before a new provider starts processing your content.
Logs and telemetry
Error reports are scrubbed of transcript text, questions, answers and tokens before they leave our systems.
Product analytics record which features are used, never what was said in a meeting.
For organizations
When an organization buys Sayli for its team, the organization decides how its content is handled. We act as its processor under a Data Processing Addendum.
Enterprise adds billing by invoice, retention you set, company-wide control of public links, and a direct line to the people who built Sayli.
What we have not done yet
Sayli does not hold a third-party security certification today, and it does not process data inside the European Union. If your review needs either, tell us what it requires and we will answer plainly.
Questions from your security team?
Write to us. You will hear back from one of the people who built Sayli.
Always know what to say.
From your next call on.
Free to start, on Mac and Windows.