DREFLYSub-processors
Last updated October 2026
A sub-processor is a third party we rely on to run Drefly's infrastructure or to process a piece of data on our behalf. This page lists the sub-processors Drefly and Drefly for Slack currently use, what each one is used for, and where relevant, where it is hosted. For what we store in the first place, see our Privacy Policy, in particular the Drefly for Slack section.
Infrastructure
| Sub-processor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Serves the drefly.pro website and static assets (Cloudflare Workers), and temporary object storage for files being processed (Cloudflare R2), auto-deleted on the schedule described in our Privacy Policy. | Global edge network |
| Google LLC (Google Cloud) | Runs the API that powers file processing tools and the Drefly for Slack backend (Google Cloud Run). | Google Cloud |
| Supabase, Inc. | Hosts the Postgres database that stores account records, Slack workspace and connection metadata (encrypted access tokens), and feedback submissions. | AWS us-east-2 (Ohio) |
Analytics
| Sub-processor | Purpose |
|---|---|
| Google Analytics (Google LLC) | Aggregate traffic and usage analytics, opt-in only. See "Cookies and analytics" in our Privacy Policy for how consent is enforced. |
| Microsoft Clarity (Microsoft Corporation) | Session usage insights such as clicks, scrolling and heatmaps, used only to enhance the user experience of our tools, opt-in only. See "Cookies and analytics" in our Privacy Policy. |
Optional, user-initiated connections
These are only involved if a user chooses to use them. They process data because the user directed that specific action, not automatically, and Drefly doesn't have a standing sub-processor relationship covering data it never touches.
| Service | When it's involved |
|---|---|
| Google Drive, Dropbox, OneDrive | Only if a user chooses "Save to your Drive" for a recording. The file goes to the user's own connected drive, not to Drefly's infrastructure. |
| Anthropic, OpenAI, Google Gemini, Groq, OpenRouter, Mistral, DeepSeek, Cohere | Only for AI tools, and only when a user supplies their own API key (BYOK) or uses the small free daily quota on tools that support it. The request goes directly to that provider. |
| AssemblyAI, ElevenLabs | Only if a user pastes their own key into the Record tool for cloud transcription instead of the default on-device transcription. |
What this means for Drefly for Slack specifically
Installing Drefly for Slack stores a workspace's team ID and an encrypted bot access token in the
Supabase database above, so the /drefly command, shortcuts, and link unfurling keep
working. If a member connects their own Drefly account, we also store their Slack user ID and, if
the profile scope is granted, their display name and email, in the same database. None of that data
is shared with a sub-processor beyond the infrastructure providers listed here, and Drefly does not
read or store Slack message or channel content.
Changes to this list
We'll update this page if we add or remove a sub-processor. For material changes affecting Drefly for Slack, we'll also note it in our Privacy Policy.
Contact us
Questions about a specific sub-processor or how data flows to it: email support@drefly.pro.