Legal
Subprocessors
Last updated: 25 July 2026
RecapButler uses a small number of vetted subprocessors to operate the Service. This page is the current, dated source of truth; the shorter summary on our Security page links back here.
Current Subprocessors
| Provider | Data | Purpose | Location |
|---|---|---|---|
| Supabase | Account data, workspace and audit-trail records, meeting metadata, file storage | Core database, authentication and storage | European Union (Frankfurt, eu-central-1) |
| Vercel | Application traffic, technical/server logs | Application hosting and delivery; functions pinned to Frankfurt (fra1) | European Union (Frankfurt) primary region; Vercel's global edge network may cache non-personal static assets elsewhere |
| Anthropic | Meeting transcripts and metadata sent for AI extraction and drafting | Drafts proposed CRM/task updates from meeting content; no training on customer content under Anthropic's commercial API terms | United States |
| Resend | Email address, transactional email content | Transactional email delivery | United States (provider account metadata); messages sent from an EU-configured sending domain |
| Creem | Billing metadata (billing email, plan, subscription status, renewal date, customer/subscription reference); full card data is held by Creem and its own processors, not by us | Payment processing, acting as our Merchant of Record | United States / European Union |
| Recall.ai | Meeting audio and video, generated recordings, transcripts, and participant metadata for the meetings your organization connects | Meeting bot: joins your calls, with a visible name and avatar, to capture and transcribe them | The region configured via our RECALL_REGION setting; defaults to the United States (us-west-2) unless set to an EU region |
What this means for meeting audio specifically: unlike our other infrastructure, which is pinned to the EU, the meeting-bot vendor (Recall.ai) processes raw recordings in the region we configure for it, which today defaults to the United States absent a specific EU-region configuration. We are evaluating pinning this to an EU region as we move toward general availability. If your organization requires meeting audio to stay in the EU, contact us before connecting the bot so we can confirm current configuration.
International Transfers
Where a subprocessor processes personal data outside the EU/EEA, we rely on that provider's Standard Contractual Clauses (or a successor mechanism recognized under GDPR Chapter V) or another adequacy mechanism where available. For transfers governed by KVKK, we rely on the statutory transfer mechanisms available under KVKK Article 9. Details are in our Data Processing Agreement.
Changes to This List
If we add, remove, or replace a subprocessor in a way that affects the categories of data described here, we will update this page and notify customers under an active Data Processing Agreement in advance so they can object under the terms of that agreement.
Contact
Questions about this list: hello@recapbutler.com
Questions about this document: hello@recapbutler.com