EU region
Hosting
Servers, database and cache are configured in Render's Frankfurt region.
Loading...
ReVoice uses EU regions for hosting, meeting capture, transcription and AI analysis. Meeting bots run in Recall.ai's Frankfurt region, and transcription through Recall uses Deepgram's EU endpoint. Provider access and transfer safeguards are described separately in our sub-processor list and DPA.
Every stage of a meeting and its processing region. Meeting capture uses Recall.ai's EU deployment in Frankfurt, with Deepgram transcription through its EU endpoint. Provider jurisdiction and transfer safeguards are listed separately on the sub-processors page.
Servers, database and cache are configured in Render's Frankfurt region.
Meeting capture runs in Recall.ai's EU region in Frankfurt. Transcription through Recall uses Deepgram's EU endpoint.
Imports and direct recordings are transcribed against Deepgram's and Microsoft's EU endpoints, with Deepgram's model improvement program opted out. During meetings with the meeting bot, Deepgram transcribes through Recall.ai using its EU endpoint (api.eu.deepgram.com).
Summaries, insights and search are configured against Azure OpenAI in Microsoft's EU Data Zone. A fallback route to OpenAI in the United States and optional web search process data outside the EU if they are switched on, as described in the privacy policy.
Recordings, media and documents are stored in Cloudflare R2 under EU jurisdiction; the storage client refuses other storage addresses.
Matilda's voice is configured against Microsoft's EU regions, with Azure AI Speech and Azure OpenAI.
We do not use your meetings, audio, transcripts or documents to train, fine-tune or improve AI models, whether our own or anyone else's.
Meeting capture runs in Recall.ai's EU region in Frankfurt. Transcription through Recall uses Deepgram's EU endpoint. See the sub-processor list, privacy policy and DPA for provider-specific data handling and transfer terms.
Traffic between the browser and re-voice.io is encrypted with TLS. The database and file storage are encrypted at rest by our hosting providers, as their documentation states. Stored sign-in credentials, such as OAuth tokens, are additionally encrypted in the application with AES-256-GCM. Not every internal connection within the hosting provider's private network is encrypted.
AI requests in ReVoice pass through one of two checks before any model is called. Questions that can retrieve or combine knowledge from meetings, documents and Company Knowledge pass through the Gatekeeper, which decides what the assistant may see and say. Processing of a single meeting, such as summaries, translation and sentiment analysis, passes through a scoped check that may not retrieve any other content. Both refuse the request if a check cannot be completed.
When ReVoice sees that someone outside your organization is in the meeting, the assistant automatically withholds internal knowledge, such as Company Knowledge and previous meetings, from its answers.
Known attempts to jailbreak or hijack the assistant through meeting text, transcripts or documents are detected and blocked before they influence an answer.
Allowed and blocked decisions from both checks are written to the same audit log, so you can follow what the AI did and why.
Processing of a single meeting may read only that meeting. Workspace, company and owner are re-read from the database on every call, and no retrieval of other content is allowed.
Every sub-processor is listed on the sub-processors page, with its purpose, where data is stored and processed and the transfer mechanism that applies.