How we handle your data

Accounts, sessions and workspace invitations run on Clerk. Every request to the Rydhm API carries a Clerk session token, which the API verifies (signature, expiry, issuer and the site it was issued for) before doing anything, and every request must belong to a workspace.

Within a workspace, roles decide what people can do. Owners and admins create, publish and delete experts, edit knowledge, manage tools and see analytics. Members use experts and can delete only what they created.

Experts, knowledge, conversations, meetings, tools and connected accounts each belong to one workspace. Every database query is limited to the workspace of the person asking, and automated tests check that one workspace can’t read another’s records.

Visitors who talk to a published expert on your website or its public page don’t sign in. They reach an expert that answers from its knowledge only, without your workspace’s tools, and public endpoints are rate-limited. Public links end in a random code, so they can’t be guessed.

In transit. The website and API are served over HTTPS only, with HTTP Strict Transport Security. Live call audio is encrypted by WebRTC (DTLS-SRTP) between the caller and our media server.

Secrets at rest. Tokens for MCP servers and webhook headers you mark as secret are encrypted with AES-256-GCM before they are stored, and they are never sent back to the browser.

Connected accounts. When you connect Google Calendar, Gmail or Outlook, the sign-in tokens are held by our integration provider, Composio. Rydhm stores only a reference to the connection.

Rydhm keeps what an expert needs to work and what you need to review its work:

Account and workspace

Names, email addresses, workspace membership and roles, copied from Clerk.

Experts

Instructions, greeting, voice and tool settings, widget settings, and the avatar and background images you upload.

Knowledge

The text extracted from your documents and web research, split into passages with search embeddings. The original files aren’t kept.

Conversations

Chat messages and the transcripts of voice calls with your experts.

Meetings

Title, the brief you gave the expert, the join link, the transcript (speaker names and, where the meeting platform provides them, email addresses), meeting chat, the summary and a record of the summary emails sent.

Usage

Call minutes, a record of each tool run (its name, status and timing, not its contents) and an audit log of who changed what.

Expert avatars and backgrounds are served as public images, because they appear on your website and in meetings. Don’t upload anything private as an avatar.

Rydhm doesn’t store the audio or video of calls or meetings. Live audio travels through our media server to the speech-to-text provider and the expert, in real time, and is turned into a transcript. What we keep is the text.

In meetings, the bot that joins the call is run by Recall.ai, which receives the meeting’s audio and video in order to produce the transcript. Recall.ai handles that media under its own retention settings; see Sub-processors.

Voice previews you play while choosing a voice are cached for up to 30 days. They contain sample lines, not conversations.

Voice calls and meeting audio run through a realtime media server that Rydhm operates itself, built on LiveKit’s open-source server and hosted on Fly.io in the United States. It relays audio between the caller and the expert; it has no recording feature turned on.

To answer, an expert sends the conversation, its instructions and the relevant knowledge to the AI providers that power it: language models, speech-to-text and text-to-speech. Each provider and what it receives is on the sub-processor list.

Rydhm doesn’t train or fine-tune AI models on your data. Your knowledge is used only to answer questions for your own experts. Our policy is to use provider plans whose terms don’t allow the provider to train its models on the data we send.

Our monitoring of voice sessions records timings and errors with conversation content redacted, and our application logs replace what was said with a length and a fingerprint.

• Webhook tools can’t reach private or internal network addresses, so an expert can’t be used to probe our infrastructure.
• Events from the meeting bot provider are accepted only with a valid signature.
• The page the meeting bot uses to speak in a call is opened with a signed, expiring link.
• Pages in the Rydhm app can’t be framed by other sites. Only the website widget is designed to be embedded.
• Actions that change something, like booking a meeting or sending an email, ask for confirmation by default.

We keep your data while your workspace is active. You can delete conversations and meetings at any time: deleting a meeting removes its transcript, summary and email records. Deleting an expert removes its knowledge and chats.

Application logs are kept for 30 days and the audit log for a year. To delete a whole workspace, write to [email protected].

If you find a security issue, email [email protected] with the steps to reproduce it. We’ll confirm we received it, keep you updated while we fix it, and ask that you give us reasonable time before sharing it publicly.