Security & compliance

Last updated October 26, 2026

Subprocessors

The providers that may process customer data on MeetSwift's behalf, what each one does, the categories of data it receives and where it operates.

  • Optional integrations apply only when a workspace enables them.
  • Identity providers can also apply when a person chooses that provider to sign in.
  • Zoom applies only when a customer selects a Zoom meeting for capture.

Core service

ReplitPurpose: app/API hosting, PostgreSQL service, App Storage, connectors, runtime/build logs, development and platform analyticsData: Application/database content and audio, secrets authority, requests, logs, source and developer prompts; critical platformLocation: to be confirmed
OpenAI via Replit AI IntegrationsPurpose: AI transcription, transcript analysis, summaries, meeting questions and briefs via Replit's AI intermediary.Data: Audio transcription, transcript analysis, summaries, evidence for meeting questions/briefs; proxy/intermediary includedLocation: to be confirmed
Recall.ai via Replit connectorPurpose: Meeting capture through visible bots and the Replit connector.Data: Visible bots, platform links, participant information, call audio/transcript and provider copiesLocation: to be confirmed
ClerkPurpose: Authentication, account and session management, multi-factor authentication and recovery.Data: User identities, emails, session/account metadata, factors and recovery; no intentional transcript storageLocation: to be confirmed
StripePurpose: Payments, subscriptions, checkout and billing management; exclude meeting content and PHI.Data: Billing customer/contact data, checkout/subscription and entitlement/payment references; hosted payment pagesLocation: to be confirmed
ResendPurpose: transactional and action email, invitations, privacy notices and security alertsData: Recipient email, onboarding link, task reminders/digests and notice/delivery metadata; templates may disclose contentLocation: to be confirmed
Google FontsPurpose: public site and portal stylesData: Browser network/request metadata to fonts.googleapis.com/fonts.gstatic.com; not intended meeting-content processorLocation: to be confirmed

Optional integrations

Apply only when a workspace enables them, or when a person chooses that provider to sign in.

MicrosoftPurpose: identity/calendar, Graph/To Do and optional Teams channel postingData: Account identity, calendar titles/attendees/meeting links, OAuth grants, synchronized tasks and authorized channel outputsLocation: to be confirmed
GooglePurpose: identity, calendar OAuth/managed connectorData: Identity, calendars, titles, attendees, meeting links, OAuth grantsLocation: to be confirmed
SlackPurpose: optional private-channel meeting postsData: Destination/channel membership and authorized meeting summary/action content; OAuth tokensLocation: to be confirmed
ZoomPurpose: customer meeting platform joined by RecallData: Customer call content, participants and call retention when Zoom is selectedLocation: to be confirmed

Notes

  • This inventory describes service providers, integrations and external dependencies; it is not a vendor assurance or residency guarantee.
  • Optional calendar, channel and meeting-platform integrations apply only when enabled for the workspace. Microsoft and Google may also process identity data when selected for sign-in through Clerk.
  • Zoom is customer-selected: it is the customer's meeting platform joined by Recall when that capture is requested. Its contractual role depends on the selected service and arrangement.
  • Processing locations are to be confirmed; no specific residency or international-transfer guarantee is made.
  • Source hosting/CI and internal email, password-vault and evidence-repository providers remain to be confirmed in the internal register; they are not represented as confirmed providers here.