Subprocessors

Providers that host Lev's application, database, file storage, and networking. Customer data is encrypted in transit and at rest.

Provider	Purpose	Region	Customer data
AWS	Cloud compute, S3 document storage, RDS PostgreSQL database, and networking for the Lev platform.	US (us-east-1)	StoresYes ProcessesYes
MongoDB Atlas	Database for the email service, including metadata and message bodies.	US	StoresYes ProcessesYes

Identity, single sign-on, and multi-factor authentication.

Provider	Purpose	Region	Customer data
Auth0	Authentication, SSO, and MFA for every Lev user account.	US	StoresLimited to user names and email addresses ProcessesYes

Providers that support extraction, reasoning, document processing, layout parsing, and transcription.

Provider	Purpose	Region	Customer data
OpenAI	Document extraction, embeddings, and note generation.	US	StoresNo ProcessesYes AI trainingNo
Anthropic	Complex reasoning and long-context document analysis.	US	StoresNo ProcessesYes AI trainingNo
Google Gemini	Document processing and multimodal understanding.	US	StoresNo ProcessesYes AI trainingNo
Chunkr AI	Document layout analysis and structured parsing.	US	StoresNo ProcessesYes AI trainingNo
AssemblyAI	Speech-to-text transcription of recorded calls.	US	StoresNo ProcessesYes AI trainingNo

The OAuth, sync, and delivery layer that powers Lev's email, SMS, and real-time features.

Provider	Purpose	Region	Customer data
Nylas	Email API middleware: OAuth, sync, and inbox event webhooks.	US	StoresNo ProcessesYes
SendGrid	Transactional email delivery for deal, document, and lender notifications.	US	StoresLimited to email notification logs ProcessesLimited to email notification logs
Resend	Transactional email for invitations and account verification.	US	StoresLimited to email notification logs ProcessesLimited to email notification logs
Twilio	SMS and voice communication.	US	StoresLimited to notification logs ProcessesYes
Pusher	Real-time WebSocket messaging for live in-app updates and notifications.	US	StoresNo ProcessesNo

Payment processing and usage-based billing. Lev does not store full payment card numbers.

Provider	Purpose	Region	Customer data
Stripe	Payment processing and subscription billing. Lev does not handle full card numbers; Stripe tokenizes payment data.	US	StoresLimited to billing details for billing contact ProcessesYes
Metronome	Usage-based billing and metering.	US	StoresLimited to billing details for billing contact ProcessesYes

Observability providers that keep the platform healthy. Logs and traces may include fragments of customer data from error contexts, and are retained for a limited period.

Provider	Purpose	Region	Customer data
Datadog	Application monitoring, structured logs, and APM traces.	US	StoresYes, logs/traces for 30 days ProcessesYes
Sentry	Error tracking with grouped stack traces and breadcrumbs.	US	StoresYes, error events ProcessesYes

Product analytics and customer-lifecycle tooling. Sensitive fields are masked or excluded from ingestion before being sent to these providers.

Provider	Purpose	Region	Customer data
PostHog	Product analytics: events, funnels, and feature usage.	US	StoresYes, analytics events ProcessesYes AI trainingNo
HubSpot	Marketing CRM, sales pipeline, and contact engagement.	US	StoresNo ProcessesNo

Tools we use internally that may incidentally handle customer communications or operational alerts.

Provider	Purpose	Region	Customer data
Google Workspace	Internal email, calendar, and collaboration — inbox for support.	US	StoresNo ProcessesNo
Slack	Internal messaging and on-call alerting for production errors.	US	StoresNo ProcessesNo

Changes to this list