Skip to main content
Subprocessors

Who may handle Customer Data.

Service categories used in the current pilot that may process Customer Data while providing the Acorn service. This page supports the DPA list and notice claims. It is not a full legal entity schedule and does not expand geography, retention, or controller/processor roles beyond the DPA and Privacy Policy.

Pilot list Subject to review 30-day change notice
Scope
Verified pilot service categories only. Conditional or optional infrastructure is omitted until it is part of the standard path for Customer Data.
Notice
The DPA states at least 30 days notice before a new sub-processor begins handling Customer Data. This page is the public list only—not a notice-delivery system or activation gate.
Related
See the DPA for processor terms and the Privacy Policy for retention and rights language.

1. Coordinator hosting

The hosted coordinator runs on Fly.io infrastructure for the current pilot. It stores and transmits job metadata, account and authentication data, billing and audit records, and Customer content needed to accept, shard, dispatch, and return transcription work. The hosted pilot currently uses a single US coordinator region. Region pinning and data-residency guarantees are not available.

2. Distributed worker operators

Enrolled Apple Silicon hosts run the Acorn worker software, claim shard-scoped jobs, fetch the assigned audio clip plus task metadata, perform transcription locally, and return text. Workers receive fragment-scoped inputs; they do not receive the full merged transcript or other workers' rows. Once a clip is fetched, local retention is limited by application design and the Worker Agreement, not by a cryptographic guarantee.

3. Customer-directed recipients

Customer-configured webhook endpoints receive transcript-bearing results at destinations the Customer selects. Those endpoints are ordinarily Customer-directed recipients rather than Acorn-selected sub-processors.

4. Change notification

Acorn maintains this current list at /subprocessors and updates it when the pilot set of categories changes. The DPA states: at least 30 days notice before a new sub-processor begins handling Customer Data. That commitment is contractual under the DPA for customers that execute it; this page is not a notice-delivery channel, does not timestamp notice events, and does not gate enabling conditional infrastructure (for example optional object-storage backends). Counterparties with a signed DPA should use the notice process in that agreement, or contact legal@acorncompute.com.

5. What this page does not claim

This list does not certify SOC 2/ISO status, multi-region residency, encryption-at-rest warranties, or regulated-workload suitability. Conditional adapters (for example optional object-storage backends or email delivery providers) are not listed as standard Customer Data sub-processors until they are part of the verified pilot path. Questions: legal@acorncompute.com.

DPA

Need the executable processor terms?

See the public Data Processing Addendum cover sheet, or email legal@acorncompute.com for a signed copy.