Security and privacy
Your conversations are the product of your work. We treat them that way.
RecapButler is built for GDPR and KVKK from the first line. This page says plainly what we do with your data, and what we never do.
The commitments
EU data residency
Transcripts, extracted records, and audit trails are stored in the EU, in Frankfurt. Some processing steps (AI extraction, email delivery) involve providers that process data outside the EU under appropriate safeguards such as Standard Contractual Clauses; the subprocessor list below says exactly who and why.
Encrypted, at rest and in transit
TLS on the wire, AES-256 at rest. Standard, boring, and always on. Boring is what you want here.
Never used for training
Your conversations are never used to train models. Not ours, not our providers'. Transcripts are processed to serve you and for no other purpose.
A visible bot, always
When the RecapButler bot joins a call, it joins with a name and an avatar that every participant can see. There is no stealth mode, and we will not build one.
Retention you control
Transcript storage is under your control today: keep full transcripts (the default) or turn storage off in Settings, and permanently delete stored transcripts at any time. Deleting a meeting, a client, or your account removes the underlying data, not just the reference to it.
Self-host for enterprise
On the roadmap: enterprise teams will be able to run RecapButler on their own infrastructure, inside their own perimeter, so transcripts never leave their network. Not shipped yet; we will not pretend otherwise.
Subprocessors
The short and honest list of third parties that touch your data, and why:
- Supabase (EU)
- Database, auth and storage, Frankfurt region (eu-central-1)
- Vercel
- Application hosting; functions pinned to Frankfurt (fra1)
- Anthropic
- AI extraction over the API. No training on customer content under Anthropic's commercial terms.
- Resend
- Transactional email, sent from the EU region; provider account metadata is processed in the US
- Creem
- Payment processing as our Merchant of Record; billing metadata only, no full card numbers
- Recall.ai
- Meeting bot that joins calls to capture audio and produce transcripts; processes recordings in a configured region, defaulting to the US unless set to the EU
This is a summary. The full, dated subprocessor list, with data categories and locations, lives on our Subprocessors page.
Paperwork
A Data Processing Agreement is available for any customer whose data we process, including early access. Write to hello@recapbutler.com and we will send it over.
Read the Data Processing Agreement
SOC 2 Type II: on our roadmap. We do not hold the certification today, and we will not pretend otherwise.
Questions we have not answered here?
Ask us directly. Security questions get answered by the people who wrote the code.