Subprocessors
The third-party service providers The One Stack uses to operate the platform.
Sub-processor disclosure updated November 5, 2026 (inventory correction of Microsoft Azure processing). This page mirrors Annex III of the Data Processing Agreement.
These are the third-party service providers ("subprocessors") that The One Stack uses to operate the platform and that may process customer data on our behalf. This list is the same list published as Annex III of our Data Processing Agreement.
| Subprocessor | Purpose | Data processed |
|---|---|---|
| OVHcloud | Hosting for the Platform and its databases, and key-management services | Customer Data hosted on the Platform |
| Microsoft Azure (Azure Key Vault) | Key and secret management | Encryption keys and secrets |
| Microsoft Azure (Azure AI Foundry) | AI inference for Platform AI features, including THEO, Voice AI, Defend, PSA, CRM, Cypher, RMM, Shield, Legal, Edge, Bridge, and related automation and operations features | Prompts, model outputs and tool payloads, including Customer Data submitted through those features. Inference requests may be processed transiently in Azure regions outside the United States. |
| Microsoft Azure (Azure Trusted Signing) | Signing The One Stack software | SHA-256 digests of The One Stack software files and related signing metadata; the files themselves are not uploaded |
| Microsoft Azure (endpoint quality-assurance systems) | Testing endpoint software | Endpoint-security and device-management telemetry from test machines operated by The One Stack, including device and user identifiers on those machines |
| Microsoft Azure (remaining infrastructure) | Voice network edge and media relay; Shield DNS; remaining storage, caching and database infrastructure during the OVHcloud migration | Voice signaling and media in transit; DNS traffic; network and security logs; cache objects; identity-issuer data; workflow state; Customer files and records still held in remaining storage and databases, including support-ticket attachments, legacy database records and their backups |
| Amazon Web Services (AWS) | Transactional email delivery, inbound email receiving, and object storage | Email addresses, email bodies and attachments; stored objects |
| Cloudflare | Network edge services: DNS, content delivery, DDoS protection, and security filtering of web traffic to the Platform; DNS resolution for the Shield product | Web traffic to and from the Platform while in transit, including IP addresses; for Shield DNS resolution, DNS query names and client IP addresses |
| DigitalOcean | Deprecated infrastructure for the Edge (SASE) product: any remaining SASE concentrator VMs pending migration to OVHcloud (new Edge deployments are hosted on OVHcloud) | For any remaining DigitalOcean-hosted concentrators only: network traffic tunneled through those concentrators and related flow records (IP addresses, ports, byte counts) |
| Cartesia | Speech recognition and speech synthesis for the Voice product | Live caller audio, call recordings and voicemail audio submitted for transcription; transcripts; text submitted for speech synthesis |
| Deepgram | Speech recognition: the fallback recognizer behind Cartesia for live Voice calls and call transcription, and the recognizer for spoken input to THEO. We send Deepgram's model-improvement opt-out with every request, so audio is not used to train Deepgram's models | Live caller audio, call recordings, voicemail and microphone audio; transcripts |
| ElevenLabs | Speech synthesis for Cypher training simulations, and speech recognition for recorded call audio in limited cases | Recorded call and voicemail audio and resulting transcripts; text submitted for synthesis |
| LiveKit | Real-time audio and video for Voice calls and incident War Room | Live audio and video streams, and recordings made with the recording feature |
| Telnyx | Communications carrier services for Voice: calling, SMS/MMS, fax, number provisioning, caller-name lookup, and E911 routing | Call audio, calling and called numbers, keypad input, message content, fax images, registered E911 addresses |
| Twilio (SendGrid) | Email delivery for voicemail-to-email, fax-to-email, field-service and Voice notifications | Recipient email addresses, message bodies, attached voicemail audio and fax images |
| Google (Firebase Cloud Messaging), Apple (APNs), Expo | Mobile and desktop push notifications | Device push tokens and notification content (for example, a caller's name and number, a ticket subject, or a voicemail alert) |
| Stripe | Payment processing, subscription billing, and identity verification where a telecom customer must complete identity checks | Billing and payment details (card numbers are tokenized by Stripe and never reach us); for identity verification, name, government ID image and selfie captured in Stripe's hosted flow |
| BNG Holdings, Inc. (BNG Payment Gateway, an NMI-based gateway; secure.bngpaymentgateway.com) | Card and ACH payment processing for MSPs that connect their BNG merchant account | Payer name and billing details, and tokenized card or bank data entered in BNG's hosted fields; The One Stack never stores raw card or account numbers. Processed in the United States. |
| CereTax | Sales and telecommunications tax calculation on The One Stack's own invoices and quotes | Billing and service addresses, invoice line items, amounts and tax codes |
| GitHub | Code repository integration (only repositories you choose to connect) | Content and metadata of connected repositories |
| Spider.cloud | Web crawling and content extraction for knowledge base and CMDB enrichment features | Publicly available web content and URLs you submit |
| SkySwitch | Telecom migration tooling, only if you are migrating from a SkySwitch platform | Phone numbers, extensions and user records being migrated |
| Enzoic | Dark-web breach-exposure monitoring of email addresses for the Cypher and Defend products | Email addresses on the monitored roster (no passwords or password hashes) |
| CrowdSec | IP reputation lookup at the API gateway before a request is served, and enrichment of security alerts | The public IP address of the client making a request; IP addresses observed in a security alert |
| AbuseIPDB | IP reputation enrichment for security alerts (Defend) | A single public IP address observed in the customer's network or alert |
| GreyNoise | IP reputation enrichment for security alerts (Defend) | A single public IP address observed in the customer's network or alert |
| urlscan.io | URL and domain reputation enrichment for security alerts (Defend) | The domain name or full URL observed in a security alert |
| emailrep.io | Sender reputation lookup in the user-reported-phishing pipeline (Defend) | The plaintext sender email address of a message a user reported as phishing |
| Have I Been Pwned (Pwned Passwords) | Breached-password check when a password is saved to or checked in the CMDB vault | Only the first five hexadecimal characters of the SHA-1 hash of the password (k-anonymity). No email address, no full hash, no plaintext |
| DNSFilter | Domain reputation and category data for the Shield product | On a cache miss, customer-observed fully-qualified domain names sent for lookup; inbound category feeds as applicable |
| AlienVault OTX | Domain reputation lookup for the Shield product | A customer-observed domain name, sent for each reputation lookup |
| Abuse.ch (URLhaus and ThreatFox) | Domain reputation lookups for the Shield product | A customer-observed domain name, sent for each reputation lookup |
Systems you choose to connect#
Separately from the subprocessors above, the platform integrates with third-party systems that you choose to connect, using credentials you supply. We read from and write to those systems at your direction, and your own agreement with each vendor governs in the first instance. They are listed in Section 6.1 of our Data Processing Agreement.
Changes to this list#
We announce additions or replacements of subprocessors by email to your organization's primary account contact, or to an address you designate, and you can object as described in Section 3.4 of the Data Processing Agreement. Questions about this list? Submit a request. You may also send written notice to [email protected].
Related: Privacy Policy · Data Processing Agreement · Trust at The One Stack
This article describes The One Stack's practices as of the "last reviewed" date below. It is provided for general information only. Where it differs from the Data Processing Agreement, the Data Processing Agreement controls. Last reviewed: November 5, 2026.
Was this article helpful?