Sub-processors
Effective: April 27, 2026 · Last updated: April 27, 2026
This page lists the third-party sub-processors that may process Customer Data on behalf of Tangle Technologies, Inc. ("Tangle"). We update this list when a sub-processor is added, removed, or its role materially changes.
Notification of changes
Subscribe to sub-processor change notifications by emailing [email protected] with subject "Sub-processor notifications". We give at least 30 days' notice before adding a new sub-processor that processes Customer Data, except where the change is required by law or to address a security incident.
Active sub-processors
| Sub-processor | Service | Customer Data processed | Region | Legal basis |
|---|---|---|---|---|
| Hetzner Online GmbH | Cloud infrastructure (compute, storage, networking) | All Customer Data within sandboxes | Germany / Finland | SCCs |
| Cloudflare, Inc. | Edge security, DNS, DDoS, R2 object storage | Request metadata, IP addresses, audit artifacts | US / EU edge POPs | SCCs |
| Stripe, Inc. | Payment processing | Billing email, name, payment-method tokens (no full PAN) | US | DPA |
| Google LLC (Google Workspace) | Staff email, calendar, document collaboration | Customer support communications | US | DPA |
| Sentry (Functional Software, Inc.) | Error reporting, performance telemetry | Error events; credentials, PCI cardholder data, and government IDs scrubbed by the runtime redactor before send | US | DPA |
| OpenAI, L.L.C. | LLM inference (when Customer selects an OpenAI model) | Prompt + completion text. Egress filter scrubs auth credentials, PCI, and gov-IDs before transmission. store: false enforced when caller hasn't set it. | US | API DPA |
| Anthropic, PBC | LLM inference (when Customer selects an Anthropic model) | Prompt + completion text; same redaction as OpenAI. Account-level Zero Data Retention (ZDR) governs vendor retention. | US | Commercial Terms + ZDR addendum |
| Resend | Transactional email (account, billing, security) | Email addresses of account holders | US | DPA |
| GitHub, Inc. | Source hosting, CI execution, container registry | Tangle internal source; not Customer Data | US | Enterprise agreement |
Customer-selected model vendors
Customers choose their model vendor at sandbox creation. Selecting a different vendor changes which sub-processor receives prompt content. Customers requiring a specific vendor under their own DPA or BAA should contact [email protected].
Outbound data minimization
Two enforcement layers run before any Customer Data leaves a sandbox to a sub-processor:
- Internal observability redaction. Credentials, PCI cardholder data, and government identifiers are stripped from logs, error events, audit trails, and billing events before they leave the runtime.
- External egress redaction + no-retention. Outbound JSON bodies to model vendors run through the same redactor; OpenAI Chat Completions are augmented with
store: falsewhen the caller hasn't set it.
Customers can fetch the live posture from any sandbox at GET /privacy (authenticated).
Contact
For DPA copies, sub-processor change subscriptions, or SOC 2 Type II report requests: [email protected].