Sub-processors & Third Parties
Full transparency into the third-party services we use to deliver Unified DNS. We carefully vet every sub-processor and hold them to the same security and privacy standards we hold ourselves.
Our Approach to Sub-processors
How we evaluate and manage third-party relationships.
Due Diligence
Every sub-processor undergoes a thorough security assessment before onboarding, including review of their certifications, security practices, and data handling procedures.
Contractual Controls
All sub-processors are bound by Data Processing Agreements that include confidentiality, data protection obligations, breach notification, and audit rights.
Ongoing Review
Sub-processors are reviewed annually for continued compliance. We monitor for changes in their security posture and take action if standards are not maintained.
Core Infrastructure & Services
Always-active sub-processors that power the Unified DNS platform.
| Sub-processor | Purpose | Data Processed | Location | Certifications |
|---|---|---|---|---|
| Microsoft Azure | Cloud infrastructure, hosting, data storage | All service data | US, Canada | SOC 2, ISO 27001, FedRAMP |
| Azure Key Vault | Credential & secret management | DNS provider API keys, encryption keys | US, Canada | SOC 2, ISO 27001 |
| Azure DNS | DNS hosting & resolution | DNS records, zone data | Global | SOC 2, ISO 27001 |
| Stripe | Payment processing | Billing information, transaction data | US | SOC 2, PCI DSS Level 1 |
| Loops.so | Transactional email delivery | Email addresses, notification content | US | SOC 2 |
| Microsoft Graph API | Identity & organization data | User profiles, authentication data | Global | SOC 2, ISO 27001 |
| Application Insights (Azure) | Application monitoring & telemetry | Performance data, error logs (no customer PII) | US, Canada | SOC 2, ISO 27001 |
User-Configured Integrations
Third-party services accessed only when explicitly configured by the user.
The following third-party services are only accessed when a user explicitly configures the integration within their Unified DNS account. We monitor these vendor APIs for changes.
DNS Providers
Domain Registrars
| Sub-processor | Purpose | Data Processed | Location | Certifications |
|---|---|---|---|---|
| Cloudflare API v4 | DNS & domain management | DNS records, zone data, API credentials | Global | SOC 2, ISO 27001, PCI DSS |
| Namecheap API (XML) | Domain management | Domain data, API credentials | US | — |
| Synergy Wholesale API (SOAP) | Domain management | Domain data, API credentials | Australia | — |
| OpenSRS API v0.9 (XML) | Domain management | Domain data, API credentials | Canada | SOC 2 |
| NameSilo API v1 | Domain management | Domain data, API credentials | US | — |
| Porkbun API v3 | Domain management | Domain data, API credentials | US | — |
| TPP Wholesale API | Domain management | Domain data, API credentials | Australia | — |
PSA Integrations
| Sub-processor | Purpose | Data Processed | Location | Certifications |
|---|---|---|---|---|
| HaloPSA API | PSA sync & ticket management | Client data, ticket data | UK | ISO 27001 |
| Datto AutoTask API | PSA sync & ticket management | Client data, ticket data | US | SOC 2 Type II, ISO 27001 |
| Syncro PSA REST API | PSA sync & ticket management | Client data, ticket data | US | SOC 2 |
| SuperOps PSA API | PSA sync & ticket management | Client data, ticket data | US | SOC 2 Type II, ISO 27001 |
Documentation
| Sub-processor | Purpose | Data Processed | Location | Certifications |
|---|---|---|---|---|
| Hudu API | IT documentation sync | Client documentation data | US | SOC 2 Type II, ISO 27001/27701 (in progress) |
Monitoring Only Domains
These services are used only when a user adds a domain in "Monitoring Only" mode, which allows tracking domains regardless of where they are hosted.
Note: This list represents our current sub-processors as of the date shown at the bottom of this page. We will update this list whenever a sub-processor is added, removed, or materially changes its role. Customers who wish to receive notifications of sub-processor changes can contact us at support@udns.app.
Sub-processor Change Notifications
How we keep you informed about changes to our sub-processor list.
Notification Process
- 1We provide at least 30 days' advance notice before engaging a new sub-processor
- 2Notification is sent via email to designated MSP contacts and published on this page
- 3MSPs may raise objections within the notice period as outlined in their DPA
- 4We work to address concerns and, where possible, provide alternative processing options
Sub-processor Security Requirements
All sub-processors must meet the following minimum requirements:
- SOC 2 Type II or ISO 27001 certification
- Encryption of data at rest and in transit
- Incident response and breach notification capabilities
- Signed Data Processing Agreement with audit rights
- Regular security assessments and vulnerability management