The subprocessors we rely on, and how to put a data processing agreement in place. If your diligence requires a signed DPA, we will provide one.
If your organization requires a data processing agreement (DPA), including Standard Contractual Clauses for cross-border transfer, email security@nolte.io and we will provide a copy for signature. A self-serve downloadable template is being prepared and will be linked here when ready.
We use the following subprocessors to operate nolte.io and the NolteOS delivery platform. Each maintains its own security program and attestations, and encrypts data at rest under its own controls.
| Subprocessor | Purpose | Data categories | Region |
|---|---|---|---|
| Netlify | Hosting, form handling, serverless functions | Site traffic; form submissions (name, email, company) | United States |
| Clarify | CRM for inbound conversations and delivery forecasting | Contact details of people who opt in as a lead; deal/forecast data | United States |
| Postmark | Transactional email (readiness summary, client invitations) | Email address and the message content we send | United States |
| PostHog | Product analytics | Usage data (page views, scroll depth, session duration) | United States |
| Anthropic | Generates the readiness memo; drafts delivery items from meeting notes (data not used to train models) | Readiness answers; meeting notes and delivery context | United States |
| Slack | Internal notifications (new lead; delivery updates) | Lead name/email/domain; delivery summaries | United States |
| Supabase | Database and file storage for the NolteOS delivery platform | Project/delivery records, team capacity, delivery evidence, invited client contact details | United States |
| Atlassian (Jira) | Project and issue tracking (delivery data source) | Delivery and project metadata | United States |
| Tempo | Worklog and capacity tracking on top of Jira | Worklog and time-tracking data | United States |
| Google (Meet) | Meeting records used to draft delivery items | Meeting recordings/transcripts and metadata | United States |
| Sentry | Application error monitoring for NolteOS and uptime monitoring for nolte.io | Application error and diagnostic data | United States |
Nolte operates across the United States and Mexico, and the subprocessors above are US-based. Where personal data of individuals in other regions is involved, transfers are covered by Standard Contractual Clauses or an equivalent mechanism, available as part of the DPA above.
We update this list when a subprocessor is added or removed. To be notified of changes, email security@nolte.io.
Last reviewed: October 13, 2026.