Hyperloop
Trust & Compliance

Sub-processors

Version: 2026-08-05 · Entity: HyperloopAI, Inc. · Contact: [email protected]

⚠️ DRAFT — factual scope confirmed (US hosting, customer-SMTP email, entity names, provider scope); pending legal counsel review before publishing.

HyperloopAI, Inc. ("Hyperloop") engages the third parties below to help provide the Subscription Services. Each is bound by a data-processing agreement and processes Customer Data only as needed to provide its service. This page is referenced by our Privacy Policy; we update it before adding or replacing a sub-processor.

1. Core sub-processors (all customers)

Sub-processorService providedCustomer Data processedRegion
Anthropic, PBCAI / large-language-model processing (Claude) — generates collections drafts, classifies why invoices are unpaid, dispute analysis, risk & forecast narratives, and natural-language answersAR data, invoice & customer details, and communication content included in promptsUSA
DigitalOcean, LLCCloud application hosting and managed PostgreSQL databaseAll Customer Data, at restUSA
Stripe, Inc.Subscription billing and payment processing for Hyperloop's own feesBilling contact, company name/email; payment-card data is collected and stored by Stripe, not HyperloopUSA
Plaid Inc.Bank-account data aggregation for payment capture and cash reconciliationBank-account and transaction data the Customer authorizesUSA

Email delivery: collections and notification emails are sent over SMTP — using the Customer's own mail server where the Customer configures per-organization SMTP (see §3), and simulated by default until real delivery is enabled. Hyperloop does not use a third-party transactional email provider as a sub-processor; if a central email relay is introduced, its provider will be added here.

2. Feature-dependent sub-processors (only if the Customer enables the feature)

Sub-processorService providedEnabled whenRegion
Slack Technologies, LLC (Salesforce)Slack app for notifications and natural-language AR queriesCustomer connects a Slack workspaceUSA
Merge API, Inc. (Merge.dev)Unified API for long-tail ERP connectors (e.g. NetSuite, Dynamics, Sage)Customer connects an ERP served via MergeUSA

3. Customer-connected systems (not Hyperloop sub-processors)

The following are the Customer's own systems that the Customer authorizes Hyperloop to read. Data flows from them into the Subscription Services at the Customer's direction; Hyperloop does not appoint them and they act under the Customer's own agreements with those providers:

4. Notes on AI and model training