Subprocessors

Last updated: March 19, 2026

This page lists the main subprocessors and service providers GreetAI may use to deliver the services. Some providers are used only for specific features, plans, or customer-configured workflows.

How To Read This List
Practical notes about when a provider may be used.

This is a public summary of the main subprocessors and service providers currently used or supported by GreetAI. Not every provider is used for every customer or workflow.

Some providers apply only when a feature is enabled, such as optional recording, specific AI or voice configurations, support chat, analytics, or email delivery.

Customers with specific vendor, geography, or data localization requirements should contact GreetAI before onboarding or enabling a feature that depends on a particular provider.

Core Infrastructure

Services used to host, store, and deliver core product functionality.

Google Cloud
Purpose: Cloud infrastructure, storage, background processing, and related platform operations.
Typical data scope: Application data, transcripts, optional recordings, operational metadata
Firebase
Purpose: Authentication and related account management functions.
Typical data scope: User identity and authentication data
LiveKit
Purpose: Real-time voice and media session infrastructure.
Typical data scope: Live session audio, optional media session data, connection metadata

AI And Voice Processing

Providers that may be used depending on workflow configuration and enabled features.

OpenAI
Purpose: AI-assisted language or voice features where configured.
Typical data scope: Transcript content, prompts, session context, configured AI processing inputs
Google AI (Gemini)
Purpose: AI-generated summaries, assessments, and other configured AI processing.
Typical data scope: Transcript content, optional recording-derived inputs, workflow context
Deepgram
Purpose: Speech and voice processing features where configured.
Typical data scope: Voice or transcript-related processing inputs
ElevenLabs
Purpose: Voice generation features where configured.
Typical data scope: Voice session output data and related configuration inputs
Cartesia
Purpose: Voice generation features where configured.
Typical data scope: Voice session output data and related configuration inputs

Communications And Business Operations

Services supporting billing, email delivery, and customer communications.

Stripe
Purpose: Payment processing and subscription billing.
Typical data scope: Billing and payment-related customer data
Resend
Purpose: Transactional email delivery.
Typical data scope: Email addresses and message delivery content
Crisp
Purpose: Customer support chat and related communications.
Typical data scope: Website or in-product support communications and metadata

Monitoring, Analytics, And Trust

Services used for reliability, analytics, consent tooling, and related website operations.

Sentry
Purpose: Error monitoring and operational diagnostics.
Typical data scope: Application errors, logs, and diagnostic metadata
Langfuse
Purpose: AI tracing and observability where enabled.
Typical data scope: AI interaction metadata, tracing data, and related diagnostics
Vercel Analytics
Purpose: Website and product analytics.
Typical data scope: Usage and analytics metadata
Google Analytics
Purpose: Website analytics and performance measurement.
Typical data scope: Website usage and analytics metadata
Delve
Purpose: Cookie consent and trust-related website tooling.
Typical data scope: Consent preferences and related website metadata
Questions Or Change Requests
Need a signed DPA, a narrower vendor set, or specific transfer details?
hello@greetai.co

We can discuss customer-specific privacy, procurement, and security requirements before onboarding where needed.