Sumnote: Sub-processors

Last updated: October 16, 2026

This page lists the third-party service providers (“sub-processors”) that process personal information on Sumnote’s behalf to run the Service. It supplements our Privacy Policy.

We do not sell your personal information. We share it only with sub-processors who process it on our behalf, under terms that require them to protect it and use it only for the services they provide to us. We maintain this list current and give customers advance notice (at least 30 days where practicable) before adding a new one.

Always-on sub-processors

These process data for every customer.

Provider	Purpose	What they process	Location
Amazon Web Services	Cloud infrastructure and storage	All customer data (account, meeting audio, transcripts, files)	United States
Anthropic	AI extraction of action items, decisions, summaries	Meeting transcripts and the Slack conversations you ask Sumnote to read (text only), with the project context needed to interpret them: the titles of existing tasks, meetings, and milestones, and the names of the people in your workspace	United States
OpenAI	Backup speech-to-text transcription; backup extraction	Meeting audio (transcription); for extraction, the same text and project context Anthropic receives	United States
AssemblyAI	Primary speech-to-text transcription	Meeting audio	United States
RunPod	GPU compute for training Sumnote's own models	The redacted training set only (identifiers stripped; no audio; no voiceprints)	United States
Google (Gmail SMTP)	Outbound email	Recipient email address and message content	United States
Google (Firebase Cloud Messaging)	Push notifications	Device push tokens and notification previews	United States

Amazon Web Services
Purpose
Cloud infrastructure and storage
What they process
All customer data (account, meeting audio, transcripts, files)
Location
United States
Anthropic
Purpose
AI extraction of action items, decisions, summaries
What they process
Meeting transcripts and the Slack conversations you ask Sumnote to read (text only), with the project context needed to interpret them: the titles of existing tasks, meetings, and milestones, and the names of the people in your workspace
Location
United States
OpenAI
Purpose
Backup speech-to-text transcription; backup extraction
What they process
Meeting audio (transcription); for extraction, the same text and project context Anthropic receives
Location
United States
AssemblyAI
Purpose
Primary speech-to-text transcription
What they process
Meeting audio
Location
United States
RunPod
Purpose
GPU compute for training Sumnote's own models
What they process
The redacted training set only (identifiers stripped; no audio; no voiceprints)
Location
United States
Google (Gmail SMTP)
Purpose
Outbound email
What they process
Recipient email address and message content
Location
United States
Google (Firebase Cloud Messaging)
Purpose
Push notifications
What they process
Device push tokens and notification previews
Location
United States

Conditional sub-processors

These process data only in the circumstances stated.

Provider	Activates when	What they process
Google (Workspace APIs)	You sign in with Google or connect Google Calendar / Meet	Authentication tokens; calendar events you sync; meeting metadata
Zoom	You connect your Zoom account	Authentication tokens and meeting metadata, and the sound of Zoom cloud recordings of meetings you host that Sumnote is tracking (you can turn this off). The call itself is handled by Zoom as your meeting platform, under Zoom's own terms
Fireflies	You connect your Fireflies account	Your Fireflies API key, which Sumnote uses only to read the meetings in your own Fireflies account: their details, the names of attendees and speakers, and the recording where your Fireflies plan allows it, or otherwise the transcript Fireflies produced. Sumnote sends Fireflies nothing else. Your meetings stay in Fireflies, under Fireflies' own terms
Slack	A workspace owner or admin connects Slack to your workspace	Authentication tokens, workspace and channel details, and your Slack member directory. The messages Sumnote posts into your Slack workspace: replies in a conversation it was asked to read, reminders and updates to the person holding a task, answers to /sumnote commands, and, where an admin turns them on for a channel, meeting recaps, briefs before meetings, and weekly project reports. These can include task titles, names, due dates, decisions, and open questions. The conversations themselves stay in Slack, under Slack's own terms
Stripe	We launch paid plans and you subscribe	Billing details and transaction history (card data handled by Stripe directly)

Google (Workspace APIs)
Activates when
You sign in with Google or connect Google Calendar / Meet
What they process
Authentication tokens; calendar events you sync; meeting metadata
Zoom
Activates when
You connect your Zoom account
What they process
Authentication tokens and meeting metadata, and the sound of Zoom cloud recordings of meetings you host that Sumnote is tracking (you can turn this off). The call itself is handled by Zoom as your meeting platform, under Zoom's own terms
Fireflies
Activates when
You connect your Fireflies account
What they process
Your Fireflies API key, which Sumnote uses only to read the meetings in your own Fireflies account: their details, the names of attendees and speakers, and the recording where your Fireflies plan allows it, or otherwise the transcript Fireflies produced. Sumnote sends Fireflies nothing else. Your meetings stay in Fireflies, under Fireflies' own terms
Slack
Activates when
A workspace owner or admin connects Slack to your workspace
What they process
Authentication tokens, workspace and channel details, and your Slack member directory. The messages Sumnote posts into your Slack workspace: replies in a conversation it was asked to read, reminders and updates to the person holding a task, answers to /sumnote commands, and, where an admin turns them on for a channel, meeting recaps, briefs before meetings, and weekly project reports. These can include task titles, names, due dates, decisions, and open questions. The conversations themselves stay in Slack, under Slack's own terms
Stripe
Activates when
We launch paid plans and you subscribe
What they process
Billing details and transaction history (card data handled by Stripe directly)

Note. We use AssemblyAI for speech-to-text only; voiceprints are computed within our own systems, not by AssemblyAI. We do not use any analytics provider that tracks you inside the application.