Meetings that stay findable
Most of what an organization knows is said out loud and then lost. Transcripts, summaries, decisions and action items across every meeting, in one searchable place — with an API when you want it inside your own systems.
One searchable record
Every meeting in the organization becomes text you can search. A result points at the passage and the minute it was said, so "what did we agree about the renewal?" takes seconds.
Privacy in writing
Meetings of registered users are not used to train models, personal data is not sold, and language-model routing does not retain data. The details are in the privacy policy, not in a slogan.
Shared, not scattered
Summaries and transcripts live in the organization's account, with share links for anything that needs to leave it — and a public preview that serves only the first 20% of a transcript.
Where it earns its place
- Customer conversations. What was promised, in the words it was promised in, available to whoever handles the account next.
- Internal decisions. The decision and the reasoning, so the question does not reopen in six weeks.
- Handover and onboarding. A new person can read what happened instead of asking six people.
- Cross-team visibility. One archive rather than notes in four private documents.
Putting it inside your own systems
There are two programmatic routes, both scoped to your organization and nothing else. A REST API with a personal key lets your code upload recordings and read transcripts, summaries, decisions and action items. An MCP server connects the same material to AI assistants — Claude, ChatGPT, Cursor, VS Code, the CLIs — so someone can ask a question about last quarter's meetings in the tool they already have open. Both are described on the API and MCP page.
The governance questions, answered
- Who sees a meeting? Members of your organization, plus anyone given a share link, which is revocable.
- How long is it kept? Until you delete it. Deleting removes the stored files.
- Is voice used to identify people? Only if you switch it on, and only for speakers whose consent was recorded — voiceprints are biometric data. Unconsented ones are deleted after 30 days, unused ones after 365.
- Are per-speaker statistics visible? Not unless the organization deliberately enables them.
- Where does the audio go? To our own transcription infrastructure — not to an external speech service, and never to a language-model provider.
How to start without a project plan
Pick one recurring meeting, record it for a month, and send the summary to everyone including the people who did not attend. The free plan covers 7 meetings and 120 minutes per organization per calendar month, which is roughly that trial. If it works, Pro is ₪99 per month and cancellable at any time.
Frequently asked questions
Does a bot join our calls?
No. You record where you already meet and upload the recording. An optional bot exists for teams that want one, but it is not how the product normally works.
Can we get the data out?
Yes — exports to PDF, Word and PowerPoint, share links, and a REST API for anything programmatic.
What about employees who do not want to be recorded?
Say at the start of the meeting that it is being recorded and summarized, and delete the meeting if a participant withdraws. Recognising a person by voice across meetings is off by default and applies only to speakers who consented.
Is there a business tier?
Processing capacity runs in three tiers — free, Pro and business. For the business tier and anything involving a contract, get in touch through the link in the footer.