1. Overview
The Zoom integration brings authorized account, meeting, participant, recording, transcript, and meeting-summary information into a Seedling workspace. Seedling uses that information to provide source-backed search, operating context, verification, and customer-approved workflows.
A current Seedling workspace administrator must establish an organization-level Zoom connection. Seedling supports both a Seedling-managed Marketplace app and a customer-managed Zoom app; both modes use the same workspace-scoped data, permissions, synchronization, and deletion controls after authorization.
2. Connection options
The customer-managed option remains available even when the Marketplace app is available. Changing credential ownership requires a deliberate reconnect; Seedling does not silently convert one mode into the other.
- Seedling Marketplace app
- A Zoom account administrator authorizes Seedling’s admin-managed Zoom app. Seedling manages the app credentials and encrypted access and refresh tokens.
- Customer-managed app
- Your organization creates and controls a Zoom Server-to-Server OAuth app and supplies its account ID, client ID, and client secret to Seedling.
3. Zoom data Seedling accesses
Seedling does not currently request access to Zoom calendar, contacts, meeting chat, invitations, recording analytics, or master-account data. Seedling does not use Zoom data for advertising, surveillance, unrelated profiling, or training shared Seedling or third-party models.
- Account users
- User identity and account metadata needed to enumerate the meetings and recordings authorized for the connected Zoom account.
- Meetings
- Scheduled and past meeting metadata, meeting details, and past meeting instances.
- Participants
- Past meeting participant records used to understand attendance and collaboration context.
- Recordings and transcripts
- Cloud-recording metadata, authorized recording files, and transcript text when available for the connected account.
- Meeting summaries
- AI Companion meeting summaries when the connected Zoom account makes them available.
- Authorization and delivery
- Granted scopes, encrypted OAuth credentials, account-level routing identifiers, synchronization state, and signed webhook delivery records needed to operate and secure the integration.
4. Read-only permissions
Seedling requests only the granular Zoom scopes used by the production integration. All requested scopes are read-only; Seedling does not create, update, delete, start, or end Zoom meetings and does not send Zoom Chat messages.
- Account users
- user:read:list_users:admin and user:read:user:admin
- Meeting lists and details
- meeting:read:list_meetings:admin and meeting:read:meeting:admin
- Past instances
- meeting:read:list_past_instances:admin
- Past participants
- meeting:read:list_past_participants:admin
- Meeting summaries
- meeting:read:summary:admin
- Cloud recordings
- cloud_recording:read:list_user_recordings:admin, cloud_recording:read:recording:admin, and cloud_recording:read:list_recording_files:admin
5. Security and workspace access
- Marketplace access and refresh tokens are envelope-encrypted and stored in the workspace’s tenant data plane; they are never returned to the browser.
- Seedling verifies Zoom webhook signatures against the original request body and rejects deliveries outside the replay window.
- Connected Zoom content follows Seedling workspace roles, source entitlements, and restricted-by-default source access.
- Provider credentials, raw webhook bodies, recording content, transcripts, and authorization codes are excluded from application logs.
- Generated operating configuration remains subject to Seedling’s human review and approval controls.
6. Zoom-specific retention
- Authorization sessions
- Marketplace authorization sessions expire after ten minutes, are single-use, contain no Zoom tokens, and are deleted within one day after expiry or use.
- Processed webhooks
- The raw payload is erased immediately after successful processing. Bounded delivery metadata is retained for no more than 30 days.
- Pending or failed webhooks
- Payloads remain available for durable recovery but are subject to the same 30-day maximum receipt lifetime.
- Synchronized Zoom data
- Workspace data remains while the connection is active and is removed through the integration purge when Zoom is disconnected or deauthorized.
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.