Skip to main content

Legal center · Registry

Subprocessors

A data-driven view of providers in the current application configuration. Status is deliberately narrower than a vendor logo or an environment variable.

Current configuration registryLast updated September 4, 2026

Current registry

QuoteCortex subprocessor registry
ProviderPurpose / componentData categoryStatusSource
VercelWeb hosting, deployment, and edge delivery for the application.
Web runtime
Application requests, deployment metadata, and data routed by the application.
Region depends on the deployment configuration; not published here.
Active for configured web deploymentsPrivacy / security page
SupabaseAuthentication, Postgres database, row-level access, and private storage used by configured environments.
Auth, database, and storage
Account, organization, survey, inventory, evidence metadata, and media objects handled by configured environments.
Region is selected per project and is not published here.
Active when the deployment environment is configuredPrivacy / security page
RenderWorker hosting path for durable processing when a worker is separately configured and enabled.
Processing worker
Versioned processing inputs and operational job data routed by the worker.
Not published here.
Conditional: separate worker configuration requiredPrivacy / security page
AnthropicAI-assisted room and inventory extraction when the production provider path is explicitly enabled.
Intelligence provider
Prepared evidence frames and bounded versioned extraction input; not original video or CRM credentials.
Provider processing location and retention terms require account review.
Conditional: worker configuration and explicit authorization requiredPrivacy / security page
ResendTransactional email delivery and verified sending-domain events when email provider mode is enabled.
Email delivery
Recipient and message delivery metadata needed for the configured email workflow.
Not published here.
Conditional: email provider mode requiredPrivacy / security page
TwilioManaged SMS path only when tenant credentials, compliance gates, and worker delivery are separately enabled.
SMS delivery
Phone numbers, consent evidence, message state, and provider delivery metadata when enabled.
Not published here.
Not activePrivacy / security page
StripeBilling path when a business account and the guarded billing mode are enabled.
Billing
Billing identifiers and payment status handled by the configured billing workflow.
Not published here.
Not activePrivacy / security page
Google WorkspaceNo application processing path is configured.
None
None through the configured QuoteCortex application.
Not applicable to the current application path.
Not configuredPrivacy / security page

Verification rule

This registry is not a contract or a guarantee that every path is active. Before enabling a provider for an account, the owner must verify the exact enabled provider, data flow, region, agreement status, and effective date.

This page describes the current product boundary. It is not a signed agreement, legal advice, or a certification. Questions and privacy requests can use the structured contact route.