Skip to content

Legal

Our sub-processors

The services Rydhm uses to run the product that process customer data on our behalf: what each one does, what it receives and where it runs.

Last updated

On this page3 sections
  1. 1Current sub-processors
  2. 2What isn’t on this list
  3. 3Changes to this list

1.Current sub-processors

Some services are used only when a workspace turns the related feature on; they are marked under the name.

Rydhm sub-processors
Service
ClerkSign-in, user accounts, workspaces and invitations.Names, email addresses, workspace membership and roles, session data.Provider-managed
RailwayHosts the Rydhm application, its database (PostgreSQL), cache (Redis), uploaded images and logs.Everything Rydhm stores: account and workspace records, expert settings, knowledge text, conversations, transcripts, summaries and uploaded images. Logs are kept for 30 days.United States
Fly.ioHosts Rydhm’s self-hosted realtime media server, which relays live call audio.Live call audio, relayed in real time and not stored.United States (San Jose)
Recall.aiRuns the meeting bot that joins Google Meet, Zoom and Microsoft Teams calls.Meeting audio and video, participant names and email addresses, the meeting chat. Produces the meeting transcript.United States (us-west-2)
DeepgramSpeech-to-text, and text-to-speech for some voices.Live call audio; the text of the expert’s replies.United States
CartesiaText-to-speech.The text of the expert’s replies.United States
Google (Gemini API)Language models, realtime speech (Gemini Live), speech-to-text and voices, when an expert is set to use them.Conversation text and live call audio for those experts; instructions and knowledge text.United States
OpenAILanguage models for voice conversations, and embeddings for knowledge search.Conversation text, instructions and knowledge text; knowledge chunks and search queries.United States
AnthropicLanguage models for text chat, meeting summaries, the Meeting Brief and building experts (including web research), and for voice when an expert is set to use them.Conversation text, transcripts, instructions and knowledge text; the business description and documents given when building an expert.United States
ResendSends post-meeting summary emails.Recipient email addresses, the meeting summary and the Meeting Brief PDF.Provider-managed
ComposioWhen a user connects a calendar or email accountConnects Google Calendar, Gmail and Outlook accounts, and runs calendar and email actions.The sign-in tokens for connected accounts (held by Composio, not by Rydhm), calendar event details and email content.Provider-managed
FirecrawlWhen web search is switched on for an expertWeb search for experts that have it switched on.Search queries and the sites a search is limited to.Provider-managed
LangfuseMonitoring of voice sessions (timings, errors, model usage).Session metadata and timings. Conversation content is redacted.United States
TypeSafeMeetings onlyA turn-taking model that helps an expert decide when to speak in a meeting.The expert’s and participants’ names, the number of participants, and the latest lines of the meeting transcript.United States
CloudflareDNS and network proxy in front of the Rydhm website.Network traffic to the website, including IP addresses and request metadata.Global network

2.What isn’t on this list

The realtime media server that carries live calls runs LiveKit’s open-source server, operated by Rydhm itself on Fly.io. LiveKit, the company, receives no customer data, so it isn’t a sub-processor.

Services that never receive customer data, such as our code host and domain registrar, aren’t listed.

3.Changes to this list

We update this page before a new sub-processor starts handling customer data. To hear about changes, or to ask about any of these services, write to [email protected]. See also our Privacy Policy and Security page.

Sub-processors · Rydhm