Home/Use Cases/Compliance recording
// Compliance recording

Compliance recording for meetings in regulated industries

Compliance recording for meetings covers Zoom, Google Meet and Teams through one API. You get the whole record, in storage you control.

Your own S3 bucketThe whole recordBooks from a calendarISO 27001 certified
Overview

Why video calls now need a record

The real talks happen on video calls. Teams in finance and legal are expected to keep records of them.

One request returns an MP4 recording, per-participant audio and video, and a transcript
Send a meeting link, and when the call ends you get all three.
The whole meeting

MP4 of the call, plus one audio file per person.

Transcripts either way

Speaker labels, in real time and after the call.

Who was present

When each person came and went, who hosted, and which platform.

The chat too

In-meeting messages are part of the talk and belong in the record.

An audit asks for full coverage and a whole record. That is more than audio.

Quickstart

Start capture with one API call

One request with the meeting URL puts a visible bot in the call, which supports your disclosure obligations.

  • Any host plan
    Google Meet and Teams admit it like any guest, and Zoom asks the host for recording consent.
  • Plugs into what you run
    Your archive platform, your surveillance tools, your case management stack.
  • A trail of the capture
    The bot joined. Recording started. The meeting ended. The media was filed.
Meeting linkcreate_botone requestBot in the callrecords and streamsWebhookbot.doneYour archiveretention you control
The same five steps on every platform. Only the last box is yours.
Calendar

Full coverage from the calendar

Full coverage means every client call is on the record. So it follows the calendar, not memory.

  • Three months ahead
    Calendar integration with Google and Outlook books bots that far out.
  • Changes tracked
    Reschedules and cancellations move the bot with the meeting.
  • Every call in scope
    Auto-schedule books a bot on every meeting that carries a link.
CalendarGoogle or OutlookSyncevents and linksSchedule1 min beforeBot joinsautomatically
Calendar, sync, schedule, and the bot joins.

Storage and retention on your terms

With bring-your-own S3, recordings and media are written straight to your bucket, in your region.

Your retention and deletion rules apply from the moment they exist.

A record that needs a better transcript years later can be run again from the stored file. The first one is untouched.

Detail

What are the storage defaults and limits?

Without your own bucket, recordings live in MeetStream storage in the US by default.

  • Regions you choose
    EU, Australia, Japan and the Middle East are available, and other regions on request.
  • Thirty days by default
    Kept at no charge, and adjustable per bot.
  • Or nothing in ours
    With your own storage, your Object Lock and lifecycle rules govern from the first object.

Security your auditors can check

ISO 27001certified. SOC 2 Type 2 is under audit
GDPRcompliant, with data encrypted in transit and at rest
Write-only modekeeps reads on your side alone
Slack supporttakes your questions to engineers

This fits finance and legal work that turns on retention and consent.

The healthcare page sets out the scope for clinical settings.

MEETSTREAM DASHBOARDThe MeetStream API Playground with a bot request and its live JSON request body
Configure a bot in the API Playground. Watch the request build itself, field by field.
Security

Enterprise-level security, keep your data private.

The certificate, the audit status and the Trust Center are all on the security page.

Robust and reliable

MeetStream is ISO 27001 certified. SOC 2 Type 2 is under audit rather than complete.

GDPR compliant

MeetStream is GDPR compliant, and bots run in the United States by default.

Records inside your own estate

Bring-your-own S3 writes recordings straight to your bucket, in your region.

SOC 2Type 2 (Under Audit)
ISO 27001Certified
GDPRCompliant

Capture limits and defaults

4 hoursdefault session, five when you raise it
No capconcurrent bots, and no limit to raise
30 daysstorage, or your own S3 bucket
$0.35per bot-hour, and $0.45 with transcription
United StatesThe default regionEU, Australia, JapanAnd the Middle EastOther regionsAvailable on request
Bots run in the United States by default.

Security documents are on the security page.

FAQ

Got a question? We got the answer.

Common questions about the record. Where it lives, what MeetStream gives you, and which certificates it holds.

Can recordings stay entirely in our environment?

Yes. Bring-your-own S3 writes recordings and media straight to your bucket, in your region of choice. Retention, access control, and deletion stay under your rules, not a vendor's.

Does using MeetStream make us compliant?

No. MeetStream gives you the capture layer. That means full recordings, transcripts, metadata, and audit events. Your compliance programme sets scope, retention, and review. We just feed it solid raw material.

Do meeting participants know they are being recorded?

The bot joins as a visible, named guest on Zoom, Google Meet, and Microsoft Teams. Everyone on the call can see it. Most firms pair this with their standard disclosure language in invitations.

What certifications does MeetStream hold?

ISO 27001 certified and GDPR compliant, with SOC 2 Type 2 under audit. All data is encrypted in transit and at rest.

A complete record of every client call.

Recording, transcript, chat and attendance from one API, written to storage you own.

Your own S3 bucket
Object Lock
Full metadata
Calendar coverage
Audit trail

Build it on MeetStream

One API call, $5 of free credit, no card. One API joins, records, streams, and transcribes across Zoom, Google Meet, and Microsoft Teams.