What is left after processing, and where
Most software services pack as many customers as possible onto as few machines as possible. This one is arranged the other way round: each meeting is processed by a worker with its own compute, and that worker keeps nothing once it is finished. It costs more. It is also why an hour-long meeting comes back in minutes and why your recording does not wander between machines.
A worker per meeting
Every transcription request joins the queue for its tier — free, Pro or business — and is picked up by a processing worker with a GPU of its own. That worker runs our Hebrew speech model and the speaker separation, returns a transcript with word-level timestamps, and then goes away. When there is no queue, workers shut down; when there is one, more start. The speed consequences are described in why an hour comes back in minutes.
What survives, and where
| Where | What stays there | For how long |
|---|---|---|
| The processing worker | Nothing | It releases everything when the job ends |
| Your organization’s account | The recording and the transcript, so you can re-read, edit, search and export | Until you delete them |
| Model training | Nothing from registered users’ meetings | — |
| The language model | Transcript text for the summary, on routing that does not retain it; never the audio | — |
| Voiceprints | Only for speakers who consented, and only if the organization enabled recognition | Unconsented: 30 days · unused: 365 days |
The recording is not forwarded to an external transcription service, and the summary is written from text alone. What exactly is stored, by whom and for how long is set out in the privacy policy in sentences rather than slogans.
A preview link that actually withholds the rest
There is a common pattern where a "preview" loads the entire document and then hides most of it behind a paywall overlay: anyone who opens the developer tools has the whole thing. A public preview link here serves only the first 20% of the transcript because the server sends only that much. The remainder is not in the page, not in a JavaScript variable, and not in a network response. It is not there.
A full share link — which can include the summary, and optionally the transcript — is a deliberate act by the meeting's owner, and it can be revoked. Those are the only two ways a meeting leaves your organization.
Deletion means deletion
Why say any of this out loud
A service that processes your meetings ought to be able to describe, in one paragraph, what happens to them. Here it is: a worker per meeting, nothing kept by the worker, everything kept in your account until you remove it, no training on your meetings, and no audio sent to a language model. That is the whole arrangement, and there is nothing in it that needs hiding.
The free plan covers 7 meetings and 120 minutes per organization per calendar month, which is enough to check all of the above for yourself.
Frequently asked questions
Does the processing worker keep my recording?
No. It receives the file, returns the transcript and releases. It does not hold recordings between jobs.
How long do you keep my meeting?
Until you delete it. Deleting a meeting, a speaker or the whole account removes the stored files with it.
What does a preview link show?
Only the first 20% of the transcript — and that limit is applied on the server, so the rest is never sent to the browser at all.
Can I stop sharing something I shared?
Yes. A share link belongs to the meeting's owner and can be revoked at any time.
Try it on your own recording
IvreetMeet transcribes and summarizes Hebrew meetings. The free plan covers 7 meetings and 120 minutes per organization each month.
Start free