TwinsAI captures Zoom, Google Meet, and Teams calls without a bot, then writes the recording, the transcript, and the summary to your own private S3-compatible storage. The only lasting copy of your meeting lives on storage you control.
Two independent properties, and they compound. No bot ever appears in the attendee list, and no durable copy of the meeting is retained by TwinsAI. Your bucket, your cloud account, your region, your retention policy.
TwinsAI runs on the rep's device and captures Zoom, Google Meet, and Teams audio directly. Nothing appears in the attendee list, there is no "please admit the notetaker" step, and your prospect is never asked to approve a third-party bot sitting in a customer conversation.
Point TwinsAI at any S3-compatible bucket in your own cloud account and region. The recording, the speaker-attributed transcript, and the meeting summary are all written there. You hold the credentials, you set the lifecycle rules, and you can revoke access at any time.
Audio passes through TwinsAI to be transcribed and summarized, and is removed immediately afterwards. We do not keep a durable copy of your recordings or transcripts. This is zero retention rather than on-premise processing, and we would rather be precise about the difference than oversell it.
Where the data rests, who holds the credentials, how long anything is retained, and what leaves your boundary. Those are the questions that stall a notetaker rollout, and they have concrete answers here rather than a policy page.
Self-hosted notetakers keep your data in your hands and leave every follow-up to your reps. TwinsAI keeps the storage in your hands and still finishes the post-call work in your CRM.
Private storage changes where the meeting artifacts rest. It does not change what TwinsAI does with them. Spoken action items still become CRM tasks with owners and due dates, and the deal still moves through your pipeline on its own.
TwinsAI drafts the follow-up email with the agreed next steps and the right attachments, in the tone your rep actually uses. The rep reviews and sends. This is the part every self-hosted transcription tool leaves undone.
When a next step is committed to on the call, TwinsAI checks both calendars, drafts the invite with the agreed agenda, and books it. The deal keeps moving whether or not your recordings live in our cloud.
Teams with a real data-handling requirement usually end up picking between a self-hosted tool that keeps the data but does none of the work, and a cloud notetaker that does some of the work but keeps your recordings on its own infrastructure. This is the third option.
Private storage is one property of the notetaker. These cover what it actually does with the conversation.
Yes. TwinsAI writes the recording, the speaker-attributed transcript, and the meeting summary to an S3-compatible bucket in your own cloud account and region. You hold the credentials, you set the lifecycle and retention rules, and you can revoke access at any time. It is available on the Scale and Enterprise plans.
Yes, and we would rather be direct about it. Audio is processed in TwinsAI's cloud to produce the transcript and the summary, then deleted immediately afterwards. We do not retain a durable copy. If you need the processing itself to happen entirely inside your own infrastructure, TwinsAI is not that product today, and a self-hosted transcription tool would be the honest answer.
No. Self-hosted means you run the software on your own machines and operate it yourself. TwinsAI is a hosted product with customer-owned storage: we run the service, and the recordings, transcripts, and summaries rest in your bucket rather than ours. The tradeoff is that you also get CRM writeback, follow-up drafting, and meeting booking, which self-hosted transcription tools do not do.
Any object store that speaks the S3 API, including Amazon S3, Cloudflare R2, MinIO, and Wasabi. You choose the cloud account and the region, which is what makes data-residency requirements straightforward to satisfy.
Data residency means choosing which of a vendor's regions holds your data. The data is still on the vendor's infrastructure, under the vendor's account and credentials. Customer-owned storage means the bucket is yours: your cloud account, your credentials, your retention policy, and your ability to revoke access without asking anyone.
Yes. Private storage changes where the recording, transcript, and summary rest. It does not change what TwinsAI does with the conversation. Follow-up tasks are still created in HubSpot, Salesforce, or Close, fields and deal stage still update, the follow-up email is still drafted in the rep's voice, and the next meeting is still booked.
Private storage in your own cloud is available on the Scale and Enterprise plans. Enterprise adds SAML SSO, extended audit-log retention, and a custom private LLM.
Book a 30-minute demo and we will connect TwinsAI to a bucket you control, sit in on a live meeting, and show you the recording, transcript, and summary land in your storage while the tasks and the follow-up land in your CRM.