Subprocessors

These providers touch data while RT²M runs. For each one we say what it does for us, and where it runs. What data we process and how long we keep it is set out in the privacy notice.

  • LiveKit

    What it does for us
    Relays the audio and data connection of the meeting. The name, email address and language you give when joining reach it inside the join token.
    Where it runs
    Does not run on our infrastructure; we do not choose where it is located.

  • Google

    What it does for us
    The Gemini API is the primary translation engine: your speech and its text go there. Meeting summaries are also sent out through a Google SMTP mailbox.
    Where it runs
    A cloud API, not on our infrastructure; we do not choose where it is located.

  • OpenAI

    What it does for us
    Fallback translation engine and speech recognition; the text of the meeting summary is written by their model from the transcript.
    Where it runs
    A cloud API, not on our infrastructure; we do not choose where it is located.

  • Supabase

    What it does for us
    Database and authentication: it stores accounts, sign-in and organisation data.
    Where it runs
    Germany, Frankfurt (eu-central-1).

  • Resend

    What it does for us
    Delivers account email — signup confirmation, password reset, invitation — through the Supabase mail sender. This is what the Supabase documentation describes; our own code contains no direct call to it.
    Where it runs
    An email delivery service; we do not choose where it runs.

  • Vercel

    What it does for us
    Serves the website, and provides page-view analytics.
    Where it runs
    The application runs on EU servers.

  • Microsoft

    What it does for us
    Signing in with a Microsoft account, fallback email delivery over the Graph API, and Clarity visitor analytics — the last one only if you accepted it on the cookie banner.
    Where it runs
    A cloud service, not on our infrastructure; we do not choose where it is located.

  • Our own server

    What it does for us
    Runs the translation agent and the dispatcher. Not an external provider — it is on the list for completeness.
    Where it runs
    Germany, Nuremberg.

This list can change. When it does, we update it here, and we also update the effective date of the privacy notice. If you have a question, write to hello@rt2m.app.

Back to the privacy notice

Subprocessors — RT²M