Transcription
Transparency is central to us at Intric. When you use the Transcription feature to process and summarize recorded audio files, specific processes are in place to ensure your privacy and secure data handling.
The process from your audio upload to a finished transcription and summary occurs through a secure, SSL/TLS-encrypted interaction between the Intric platform (where your data is managed) and the LLM provider you have selected (e.g. Berget AI).
Step-by-step: How your data is handled
Section titled “Step-by-step: How your data is handled”All transfers between Intric and its sub-processors occur over secure, encrypted connections.
Step 1 — User records or selects an audio file
Section titled “Step 1 — User records or selects an audio file”For live recordings: The audio is captured and stored entirely within the user’s browser, both during and after the recording. No audio data is sent to Intric at this stage — it stays on the user’s device until the user clicks Stop and save.
For uploaded files: The user selects a pre-recorded audio file from their device.
Step 2 — Audio is saved to Intric
Section titled “Step 2 — Audio is saved to Intric”For live recordings: Clicking Stop and save sends the audio file to Intric’s servers. The recording is removed from the user’s device immediately after the upload.
For uploaded files: The user submits the selected audio file, which is sent to Intric’s servers.
Data sent to Intric’s server:
- The audio file
- File name and metadata
All content is sent over an encrypted connection from your browser to Intric’s servers.
Intric’s server receives the audio file, encrypts it, and stores it securely in Intric’s database, which is operated by a Swedish sub-processor. The file is stored until the user is ready to transcribe it.
Step 3 — User prompts the assistant
Section titled “Step 3 — User prompts the assistant”Transcription begins when the user sends a message to the assistant with the audio file attached. At this point, Intric forwards the audio to the selected transcription provider.
Before the audio is sent to the AI model, Intric removes identifying metadata. No information about who uploaded the file or which organization it belongs to is attached.
Step 4 — Transcribe (call and return in one path)
Section titled “Step 4 — Transcribe (call and return in one path)”Intric sends the audio and system instructions to the assistant’s selected transcription provider and receives the text result in the same logical step.
Data sent from Intric’s server to the provider:
- The audio file
- System instructions for transcription and summarization
Data returned to Intric:
- The generated transcription and summary text
What happens at the provider: The model produces transcription and (where configured) summary text. The provider has no user or organisation identity from Intric in this call pattern.
The transcription provider processes the request in memory — nothing is written to persistent storage on the provider’s side for that request, subject to your sub-processor terms.
Step 5 — User sees the response in the browser
Section titled “Step 5 — User sees the response in the browser”The response is displayed to the user in the browser.
Data stored on Intric’s servers:
- The generated response (transcription and summary) and the history from the user’s interaction with the assistant
- The uploaded audio file
- Metadata about who sent the request
Data sharing and privacy
Section titled “Data sharing and privacy”To protect your and your organization’s privacy, we apply the principle of data minimization. This means the sub-processor only gets access to the content absolutely necessary to perform the task — no user identity ever leaves your infrastructure.
We have strict zero data retention clauses in all our contracts with language model sub-processors. This guarantees that your audio files and the generated texts are never saved by the provider after the response is returned, nor is the information used to train their AI models.
In the table below, you can see exactly what data is sent to the sub-processor and what does not leave Intric’s servers.
| Sent to the transcription model | Not sent to the transcription model |
|---|---|
|
|
Data retention and deletion
Section titled “Data retention and deletion”Transcription history follows the same principles as other assistant interactions — depending on whether the assistant is a personal assistant or in Spaces, the Creator or Admin controls deletion.
Metadata about how users use features in Intric can be stored for longer periods and is available to administrators.