Sub-processors
A sub-processor is a third party that handles data on our behalf in order to run the service. We keep the list deliberately short, because every name on it is another party your data depends on. This page names all of them, says what each one does, and says what each one can see.
The current list
These are the third parties that process data for us today:
| Sub-processor | What it does and what it sees |
|---|---|
| Railway | Cloud infrastructure. Runs the application, the managed PostgreSQL databases, and the Redis queues, so encrypted data at rest sits on their infrastructure. They do not hold the encryption keys. |
| Stripe | Payment processing for paid plans. Receives your billing contact details and card data directly from your browser. Card numbers never reach our servers, so they are out of scope for us entirely. |
| Resend | Transactional email. Receives the recipient address and message content for the emails the product sends, such as failure alerts and password resets. |
The systems you connect are not sub-processors
When a flow writes an invoice into your ERP, that is your own system, under your control, acting on an instruction you configured. We are not appointing it as a processor on your behalf, and it is not on this list. The same applies in reverse when we read from a system you own.
What none of them can see
No sub-processor receives your decrypted system credentials. Credentials are encrypted before they are stored and decrypted only in memory, inside your own environment, at the moment a flow uses them. A cloud host holding an encrypted database holds ciphertext, not logins.
The storefront assistant
The chat widget on our public site sends the message a visitor types to Anthropic in order to generate a reply. That is the entire scope of what it receives. It has no access to any workspace, any credential, or any integration data, and it is not part of the product you sign in to.
Where your data physically sits
Your application, your database, and your queue all run on Railway's cloud infrastructure. Because each paying customer gets a dedicated environment rather than a slice of a shared one, the question of where your data lives has a single specific answer rather than a diffuse one, which is usually what a vendor review is actually trying to establish. If a particular region is a hard requirement for you, raise it before you sign rather than after.
Changes to this list
We update this page whenever the list changes, and material changes are reflected in the date on our privacy policy. If you need to be notified of changes in advance for your own vendor process, tell us and we will arrange it. We would rather tell you about a new sub-processor than have you discover one.
Common questions
- Do you sell my data?
- No. We do not sell your data, and we do not share it with anyone beyond the sub-processors listed on this page and the systems you yourself connect.
- Does ml-connector store my card number?
- No. Card details go directly from your browser to Stripe, a PCI DSS Level 1 service provider. We keep a customer reference and a subscription status, never a card number.
- Where is my data physically hosted?
- On Railway's cloud infrastructure, which runs both the application and the managed databases behind it.
- Do your sub-processors have my system credentials?
- No. Credentials are encrypted before storage with a key held separately from the database, and are only ever decrypted in memory inside your own environment.
- We are running a vendor security review. Is this enough?
- This page is the sub-processor list your review will ask for. Send us the rest of the questionnaire and we will map our controls to your requirements in detail.
Keep reading
Still have a question?
Start a chat and a real person will answer it. No ticket queue.