Subprocessors

Initial public list of subprocessors and operating purposes.

This list summarizes the subprocessors and infrastructure categories most likely to be involved in product operations. The final list may vary by environment, contract, region and selected operating stack.

Effective date: 2026-04-13Last reviewed by: Security, Privacy and OperationsStatus: initial list subject to contractual review

Neon

Purposemanaged PostgreSQL database, operational storage and pooled production connections

Data involvedaccount, tenant, billing, technical diagnostics, audit, queue and data operation records

Locationregion configured in the Neon project

Notesdefault managed production database; requires TLS connections and backups/restore through Neon

Sentry

Purposeerror monitoring, traces, technical alerts and runtime failure investigation

Data involvederrors, stack traces, operational metadata, release, environment and minimum technical identifiers

Locationaccording to the Sentry project configuration

Notesenabled when SENTRY_DSN is configured in services

Stripe

Purposebilling, checkout, customer portal and subscription webhooks

Data involvedbilling data, subscription references and customer identifiers

Locationaccording to the provider configuration

Notesused when self-service billing or subscriptions are enabled

Customer or operator SMTP provider

Purposetransactional email such as verification, recovery and alerts

Data involvedemail address, name and minimum authentication or notification context

Locationaccording to the environment configuration

Notesmay vary depending on the outbound infrastructure selected

Application hosting and PostgreSQL

Purposeproduct execution, operational persistence and queues

Data involvedaccount data, technical diagnostics, audit trail, billing and operational metadata

Locationaccording to the deployed environment

Notesincludes application runtime, relational persistence and internal queues