What Makes a Meeting Recording Library Secure?
A library of meeting recordings collects some of the most sensitive things a company says out loud. Here are the seven controls that decide whether it is secure, the questions to ask any vendor, and how Kalima answers each, including what it does not have.
Short answer: a secure meeting recording library is private by default, lets you decide for each recording who can open it, puts a password and an expiry date on links that leave the company, deletes recordings on a schedule, keeps administrators out of the content, supports single sign-on and logs every change. Kalima covers all seven: recordings are private until you share them, teams share through workspaces and projects with roles, outside links can require a password and expire, companies can delete recordings automatically after 30 to 365 days, the admin console never shows recording content, Enterprise adds SSO and SCIM, and every admin change lands in an audit log. Servers are in Germany, AI processing runs in EU data centres, and recordings are never used to train AI models. Kalima holds no SOC 2 or ISO 27001 certification.
Seven controls and how Kalima handles them
| Control | Question to ask any vendor | Kalima |
|---|---|---|
| Default visibility | Who sees a new recording? | Only you, until you share it |
| Team access | Can I share with a team without sharing with everyone? | Team workspaces visible to current team members, and projects with viewer, editor and admin roles |
| Outside links | Can a link expire or need a password? | Read-only links with optional password and expiry. Company admins can switch public links off, require passwords and expiry, and limit invitations to certain domains |
| Deletion | Can recordings be deleted automatically? | You can delete any time. Company accounts can delete recordings, or only the audio, automatically after 30, 90, 180 or 365 days |
| Admin visibility | Can an admin open everyone's recordings? | The admin console never shows recording content or titles. Admins read only what is shared with them or filed in a team they belong to |
| Sign-in | SSO, SCIM, two-factor? | Two-factor sign-in and passkeys for every account. SAML 2.0 or OIDC single sign-on, SCIM and IP allowlists on Enterprise |
| Audit | Is every admin change logged? | An audit log that cannot be edited, with CSV or JSON export. Streaming to an HTTPS endpoint or Splunk on Enterprise |
Where the recordings live
- Location: Kalima's servers are in Germany. AI and speech processing run in EU data centres.
- Training: recordings and transcripts are never used to train AI models.
- Keys: on company accounts, the keys that protect recordings are wrapped with a key per company, managed by Kalima and destroyed when the company is deleted.
- Legal hold: on Enterprise, a legal hold stops recordings from being deleted for good while a dispute or an investigation runs.
What Kalima does not have
Being clear about this saves a procurement round:
- No SOC 2 or ISO 27001 certification.
- No customer-managed keys. Keys are managed by Kalima.
- No feature that lets an admin read a member's private recordings, and no handover of a leaver's recordings to someone else. Recordings stay where they are, with the access they had.
FAQ
Does a bot join the meeting to record it?
No. Kalima records the meeting audio on your own computer, so nothing joins the call. Tell the other participants that you are recording.
Can a company limit which formats members export?
Yes. On company accounts, admins decide in the console whether members may export at all and which formats are allowed.
Which plan has which control?
Private recordings, two-factor sign-in and passkeys work on every account. Company rules for sharing and export, automatic deletion and the audit log come with company accounts on Team and Enterprise. SSO, SCIM, IP allowlists, legal hold and audit streaming are Enterprise. See pricing.
Related
- Meeting transcription tools with SSO: the sign-in side in detail.
- Who can access the meeting transcript?: the same question for Zoom, Teams, Meet, Webex and Slack.
- Trust center: data location, subprocessors and security practices.
Try Kalima on your next call.
Live transcription and translation, no bot in the meeting. Free to start.
Keep reading.
Guides5 min read
Meeting Transcription Tools With SSO and Security: What to Check
Every meeting transcription tool for companies lists SSO. What separates them is whether your admin can set it up alone, enforce it, remove leavers automatically and see every change. Here is the checklist IT works through, with Kalima's answers and the things it does not do.
Guides12 min read
MCP Servers for Meetings: How AI Assistants Search Your Transcripts
An MCP server lets Claude, ChatGPT or Cursor search your meetings without a copy and paste. Here is how the protocol works, how the vendors differ, and what to check before you connect one.
Guides5 min read
How Can I Track What My Sales Team Talks About on Calls?
You want to know what actually comes up on your team's sales calls: which objections, which competitors, which promises. The answer is a searchable record of every call in one shared place. Here is how to set it up, and where the line to monitoring individual reps runs.