Subprocessors
Third-party service and support providers that may process customer information to help Autopilot provide, secure, support, and improve the service.
Autopilot uses carefully selected third-party providers to help provide, secure, support, and improve the Autopilot service. The providers listed below may process customer information in connection with service delivery, billing, support, security, maintenance, or operational activities. We group these providers into two categories so customers can distinguish between core service delivery and internal operational support.
Not every provider processes every category of customer information. Provider access depends on the enabled Autopilot features, customer configuration, support activity, and the specific data a user chooses to submit.
Service subprocessors
These providers are involved in delivering Autopilot itself. Customers will most commonly care about this category because these services can be part of the core product, infrastructure, email, billing, or customer-facing AI feature path.
| Subprocessor | Purpose | Customer information that may be processed | Vendor information |
|---|---|---|---|
| Vercel Inc. | Hosting, deployment, edge network, observability, and related infrastructure for Autopilot web properties. | Application content, usage data, IP addresses, device/browser data, logs, and diagnostic data processed through hosted services. | Vercel Trust Center and Vercel DPA |
| Supabase, Inc. | Managed database, authentication, storage, APIs, and related backend services. | Account, user, customer, dealership, workflow, and application information stored or processed by Autopilot features. | Supabase DPA and Supabase Trust Center |
| Plus Five Five, Inc. (Resend) | Transactional email delivery and email-related service operations. | Email addresses, message metadata, delivery events, and message content needed to send or process email. | Resend Subprocessors and Resend DPA |
| Stripe, Inc. | Payment processing, subscriptions, billing, tax, invoicing, and related financial operations. | Customer and billing contact details, payment identifiers, transaction metadata, tax information, invoices, and subscription status. | Stripe Service Providers, Sub-Processors & Affiliates and Stripe DPA |
| Anthropic, PBC | AI model services for user-requested assistant, analysis, drafting, or summarisation features where enabled. | Prompts, responses, and the limited application context a user or enabled Autopilot feature submits for processing. | Anthropic Trust Center and Anthropic Subprocessors |
Internal operations and support providers
These providers are not part of the core Autopilot application path, but customer information may be processed by them when we use them for support, operations, engineering, incident response, or internal administration.
| Provider | Purpose | Customer information that may be processed | Vendor information |
|---|---|---|---|
| Google Workspace | Internal email, file collaboration, customer correspondence, and business operations. | Support emails, customer correspondence, internal notes, attachments, shared documents, and contact details. | Google Workspace Subprocessors |
| Discord Inc. | Internal support coordination, customer issue triage, operational discussions, and support-related notifications. | Support tickets, customer issue reports, screenshots, logs, message excerpts, and internal discussion metadata when shared for support or operations. | Discord Privacy Policy and Discord DPA |
| Railway Corp. | Hosting and infrastructure for internal support tools, ticketing bots, webhook processing, and operational automations. | Ticket metadata, webhook payloads, diagnostic logs, and limited customer or account context needed for support workflows. | Railway DPA |
| OpenAI, L.L.C. | AI-assisted development, drafting, analysis, and operational tooling used by Autopilot staff. | Customer information, logs, support context, prompts, responses, or application data only where supplied by authorised Autopilot personnel for troubleshooting, development, analysis, or operational support. | OpenAI Trust Portal and OpenAI Sub-processor List |
AI providers
Where Autopilot uses AI service providers, customer information submitted through Autopilot is not used by Autopilot to train public AI models. AI providers are used only to provide the relevant feature, service, development, support, or operational function.
How providers are used
Autopilot limits provider access to what is needed for the relevant service or operational function. For example, hosting providers may process traffic and logging data to serve the application, email providers may process recipient and message data to deliver transactional emails, billing providers may process payment and subscription data, and AI providers may process prompts and context submitted to an enabled AI or operational workflow.
Customers are responsible for deciding what information they enter into Autopilot and for ensuring they have the rights and notices needed for that use. Autopilot remains responsible for its use of subprocessors and support providers in accordance with applicable agreements and law.
Updates
Autopilot may update this page when we add, replace, or remove service subprocessors or internal operations and support providers. If a customer has a signed agreement with different notice terms, those agreement terms apply.
For questions about this list, please contact your usual Autopilot representative.