NETRIDIUM SUBPROCESSOR LIST
Last updated: August 21, 2026
This page lists the third-party subprocessors that Netridium, LLC ("Netridium") engages to Process Customer Personal Data in connection with the Netridium Service. It is maintained under, and forms part of, Netridium's Data Processing Addendum ("DPA"). Capitalized terms used but not defined here have the meanings given in the DPA or the Terms of Service.
If this page differs from the subprocessor table in the DPA, this page controls.
1. CURRENT SUBPROCESSORS
| Subprocessor | Service provided | What it processes | Processing location |
|---|---|---|---|
| Anthropic | Model Provider — inference for Netridium-Supplied AI | Prompt text and connector responses at run time | United States |
| Supabase | Managed Postgres database, authentication, and application data hosting | Accounts, workspace data, run results, encrypted credentials | United States (US East — Ohio) |
| Render | Application, API, and background-worker compute hosting | All compute and data in transit | United States (US East — Ohio) |
| Postmark (ActiveCampaign) | Transactional and authentication email delivery | Recipient email addresses, notification content | United States |
| Stripe | Subscription billing and payment processing | Billing contact and payment data | United States |
| Cloudflare (via Render) | CDN, DNS, and edge/DDoS protection fronting the Service | Request metadata, IP addresses | Global (edge network) |
| Better Stack | Log aggregation, uptime monitoring, and operational telemetry | Pseudonymous identifiers, operational metadata | United States |
2. IMPORTANT NOTES
2.1 Bring Your Own Key (BYOK). Where a Customer supplies its own Model Provider key ("BYOK"), Prompt content and associated context are transmitted to that Model Provider under the Customer's own account and agreement with that provider. In that configuration, the Model Provider is not a Netridium subprocessor with respect to that processing, and the Customer is responsible for its own agreement and data-protection terms with that provider. See DPA Section 2.4.
2.2 Customer Systems are not subprocessors. The systems a Customer connects to the Service — for example, ERP, CRM, accounting, billing, HRIS, file storage, and data-warehouse systems such as Xero, Salesforce, QuickBooks Online, and Maxio — are the Customer's own systems and data sources, not Netridium subprocessors. The Customer is responsible for its relationship with, and the terms governing, each connected system.
2.3 No model training. Netridium contracts with its Model Provider subprocessor(s) on terms that do not permit the training of generally available foundation models on Customer inputs or outputs, consistent with Section 4.6 of the Terms of Service.
2.4 Infrastructure regions. Where a subprocessor offers multiple regions, the processing location above reflects the region(s) in which Netridium has configured the Service. Netridium may change regions within the stated country without notice; a change in processing country will be treated as a subprocessor change under Section 3.
3. CHANGES AND NOTIFICATION
Netridium may add or replace subprocessors from time to time. As described in DPA Section 5.3, Netridium will notify Customers of any intended addition or replacement of a subprocessor at least ten (10) days in advance and will update this page accordingly.
To receive advance notice of changes to this list, a Customer may subscribe by emailing legal@netridium.com with the subject line "Subprocessor Notifications." A Customer may object to a new subprocessor on reasonable, documented data-protection grounds within the notice period, in which case the process in DPA Section 5.3 applies.
Netridium, LLC · 2222 W Grand River Ave, Ste A, Okemos, MI 48864 · legal@netridium.com · privacy@netridium.com
Version: August 21, 2026