Subprocessors
Who processes your data to run meetingRudder · last updated 23 October 2026
| Provider | What for | Data | Location |
|---|---|---|---|
| Fly.io | Hosting the application and its database (Postgres) | Accounts, meetings, transcripts, notes, audit and usage records; encrypted daily backups kept for 5 days | Sydney, Australia |
| Tigris (via Fly.io) | Object storage | Meeting recordings | Global: stored and cached across Tigris regions (United States, Europe, Asia) |
| Clerk | Sign-in and organisations | Name, email, profile picture, organisation membership | United States |
| "Sign in with Google"; Calendar and Drive only if you connect them | Your Google profile for sign-in; your events, attachments and the notes you publish if connected | Global | |
| AssemblyAI | Speech to text | Meeting audio while live | United States |
| Inception Labs (Mercury) | Language model: notes, actions, summaries | Transcript text | United States |
| Baseten | Live judgments about the meeting (decision model mammoth-1) | Transcript text while live; zero data retention, not used for training | United States |
We add to this list before a new provider receives your data.