Data Processing Agreement
The Data Processing Agreement for The One Stack.
Effective date: November 6, 2026 · Version 1.14 · Last updated: November 5, 2026
The One Stack LLC, 156 S Park Blvd, Greenwood, IN 46143, United States.
Sub-processor disclosure updated November 5, 2026. This update corrects the published inventory of current Microsoft Azure processing. It does not by itself constitute notice under Section 3.4, complete an objection opportunity, or authorize processing beyond what applicable agreements provide.
This Data Processing Agreement ("DPA") forms part of the Subscription Agreement (Terms of Service) between The One Stack LLC and the Customer.
1. Definitions#
- "Controller" means the Customer: the natural or legal person, public authority, agency, or other body that determines the purposes and means of processing Personal Data.
- "Processor" means The One Stack LLC, an Indiana limited liability company, which processes Personal Data on behalf of the Controller.
- "Personal Data" means any information relating to an identified or identifiable natural person ("Data Subject"), as defined in applicable data protection law, including GDPR Article 4(1).
- "Processing" means any operation or set of operations performed on Personal Data, including collection, recording, organization, structuring, storage, adaptation, retrieval, consultation, use, disclosure, dissemination, restriction, erasure, or destruction.
- "Data Subject" means the identified or identifiable natural person to whom Personal Data relates.
- "Sub-Processor" means any third party engaged by the Processor to carry out specific processing activities on behalf of the Controller.
- "GDPR" means the General Data Protection Regulation (EU) 2016/679.
- "CCPA" means the California Consumer Privacy Act (Cal. Civ. Code § 1798.100 et seq.) as amended by the CPRA.
- "Services" means the cloud-based software platform and all associated products operated by The One Stack LLC, as described in the applicable Subscription Agreement or Order Form.
- "Customer Data" means all Personal Data submitted, uploaded, stored, or transmitted by or on behalf of the Controller through the Services.
2. Scope and nature of processing#
The Processor processes Personal Data solely to provide the Services to the Controller under the Subscription Agreement. The nature, purpose, subject matter, duration, and categories of Personal Data processed are as follows:
- Nature: storage, retrieval, transmission, analysis, display, and deletion of Personal Data as necessary to operate the Services.
- Purpose: delivery of cloud-based software services including professional services automation, CRM, remote monitoring and management, communications, AI-assisted features, billing, and related products as subscribed to by the Controller.
- Duration: for the term of the Subscription Agreement, plus the 90-day post-termination export window, plus any additional retention required by applicable law (for example, 7-year financial record retention).
- Categories of Data Subjects: the Controller's employees, contractors, end customers, and other individuals whose data the Controller submits to the Services.
- Categories of Personal Data: name, email address, telephone number, organizational role, IP address, usage data, device data, voice recordings and transcripts (where applicable), and other data submitted by the Controller.
- Instructions: the Processor processes Personal Data only on documented instructions from the Controller, as set out in this DPA and the Subscription Agreement.
3. Processor obligations (GDPR Article 28(3))#
The Processor shall:
3.1 Documented instructions. Process Personal Data only on documented instructions from the Controller, including with regard to transfers of Personal Data to a third country or international organization, unless required to do so by applicable law. In such case, the Processor shall inform the Controller of that legal requirement before processing, unless prohibited by law on grounds of public interest.
3.2 Confidentiality. Ensure that all persons authorized to process Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
3.3 Security measures. Implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, in accordance with GDPR Article 32 and as further described in Annex II (Security Measures) of this DPA.
3.4 Sub-Processors. Not engage another processor (Sub-Processor) without prior specific or general written authorization from the Controller. The Controller hereby provides general written authorization for the Processor to engage the Sub-Processors listed in Annex III. The Processor shall inform the Controller of any intended changes concerning the addition or replacement of Sub-Processors by email to the Controller's primary account contact, or to an address the Controller designates, and shall give the Controller the opportunity to object. The Controller may object in writing within 30 days after the notice email is sent. If the parties cannot resolve the objection, the Controller may terminate the affected Service without penalty. Termination under this Section does not entitle the Controller to a refund. Nothing in this DPA limits rights or remedies that cannot lawfully be excluded. Questions about that notice may be raised by submitting a request; written notice may also be sent to [email protected]. The Processor shall impose data protection obligations equivalent to those in this DPA on any Sub-Processor by written contract.
3.5 Data Subject rights assistance. Taking into account the nature of the processing, assist the Controller by appropriate technical and organizational measures, insofar as possible, in fulfilling the Controller's obligation to respond to requests for exercising Data Subject rights under Chapter III of the GDPR (including rights of access, rectification, erasure, restriction, portability, and objection). The Processor shall forward any Data Subject request received directly by the Processor to the Controller without undue delay and no later than 5 business days after receipt.
3.6 Security and breach notification assistance. Assist the Controller in ensuring compliance with obligations under GDPR Articles 32 through 36, taking into account the nature of the processing and the information available to the Processor, including obligations regarding security of processing, notification of Personal Data breaches, data protection impact assessments, and prior consultation with supervisory authorities.
3.7 Deletion and return. At the choice of the Controller, delete or return all Customer Data to the Controller upon termination of the Subscription Agreement, and delete existing copies unless applicable law requires storage of the Personal Data. Upon account cancellation or termination, Customer Data is retained for a 90-day export window so the Controller can request export, after which Customer Data is permanently deleted from production systems. Backup copies containing Customer Data are retained only until the applicable backup retention period or storage lock expires (currently up to 12 months for database long-term backups and up to 365 days for write-once backup storage), are restricted from normal use during that period, and are then deleted on the applicable cycle. Financial records subject to statutory retention (7 years) are retained only to the extent required by law.
3.8 Audit and compliance demonstration. Make available to the Controller all information necessary to demonstrate compliance with the obligations set out in GDPR Article 28, and allow for and contribute to audits, including inspections, conducted by the Controller or an auditor mandated by the Controller, subject to Section 10 (Audit Rights) of this DPA.
4. Controller obligations#
The Controller shall:
- Ensure that it has a lawful basis for processing Personal Data and for instructing the Processor to process Personal Data on its behalf.
- Ensure the accuracy, quality, and legality of Personal Data submitted to the Services.
- Comply with all applicable data protection laws, including providing required notices to Data Subjects and obtaining any necessary consents.
- Ensure that it has provided all appropriate privacy notices and, where required, obtained all necessary consents from Data Subjects before submitting Personal Data to the Services.
- Promptly notify the Processor of any changes to the Controller's processing instructions that may affect the Processor's obligations under this DPA.
5. Security measures (Annex II)#
The Processor implements the following technical and organizational measures in accordance with GDPR Article 32:
5.1 Encryption.
- At rest: industry-standard encryption of the Platform's primary datastore and of backups.
- In transit: current TLS encryption on all Platform endpoints.
- Credential vault: credentials stored in the credential vault receive additional field-level encryption. This DPA does not claim field-level encryption for health records; protection at rest for stored records is the encryption described above.
5.2 Access controls.
- Platform secrets and encryption keys are held in dedicated key-management services.
- Access to production systems requires multi-factor authentication (MFA) and is controlled by role-based access controls (RBAC).
- Administrative actions on designated platform administration surfaces are logged with the acting user, the action, a timestamp, and the affected resource.
- Customer Data is logically separated by tenant, and access controls are designed to prevent cross-tenant access. The Processor does not warrant that these controls cannot fail.
5.3 Audit logging.
- The Processor commits to retain security and audit logs for a minimum of 2 years. Operational log streams used for monitoring are kept for a shorter period (currently 90 days).
- Where HIPAA applies, the Processor commits to retain PHI audit logs (read and write access) for 6 years.
5.4 Incident response.
- The Processor maintains a formal incident response process covering detection, triage, containment, investigation, notification, remediation, and post-incident review.
- Personal Data breaches are reported to the Controller without undue delay after the Processor becomes aware of them, as described in Section 9.
5.5 Vulnerability management. The Processor maintains vulnerability management practices for the Platform, including automated dependency scanning and application security testing.
5.6 Business continuity.
- The Processor maintains encrypted, write-once (object-locked) disaster-recovery backups and tests restoration from them.
- Customer backup data for the Backups product (endpoint and server file backups) is stored in The One Stack-operated, write-once object storage in the United States, encrypted with client-side keys before upload.
- Recovery objectives are set per recovery path. Recovery objectives for Customer backup data follow the backup policy configured for each protected workload.
6. Sub-Processors (Annex III)#
The following Sub-Processors are currently engaged by the Processor to process Customer Data. All Sub-Processors are contractually bound to maintain security standards equivalent to those in this DPA. The same list is published in our Subprocessors article.
| 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 |
6.1 Systems the Controller connects
Separately from the Sub-Processors above, the Platform integrates with third-party systems that the Controller chooses to connect using credentials the Controller supplies. The Processor reads from and writes to those systems at the Controller's direction, so the Controller's own agreement with each vendor governs in the first instance. They are disclosed here so the full set of destinations for Customer Data is visible.
| System | Direction | Data that moves |
|---|---|---|
| Microsoft 365 | Read and write | Mail, files, calendars, directory users and groups; sending mail from a connected mailbox; group membership changes |
| Google Workspace | Read and write | Mail and attachments, Drive files, directory users and groups |
| Autotask / Datto PSA, ConnectWise Manage | Read and write | Tickets and notes, time entries, companies and contacts, contracts, SLAs, surveys |
| Datto RMM, NinjaOne | Read | Device names, operating systems, patch state, alerts, site mapping |
| Mosyle (Apple device management) | Read and commands | Device identifiers and assigned-user email addresses; device management commands you initiate |
| Cove (N-able), Veeam, Acronis | Read | Device names, backup job status and history |
| Datto BCDR | Read | BCDR-appliance status only. Datto Backup endpoint-asset import is not connected, so this row is not a read of Datto Backup job status. |
| IT Glue | Read | Organizations, configurations, documents and password records you choose to sync |
| Hudu, Snipe-IT | Read (Hudu also write) | Documentation, company records, asset inventory |
| Pax8 | Read | Companies, subscriptions, license quantities, billing line items |
| QuickBooks Online | Read and write | Customers, invoices, items and payment records |
| Xero | Read | Contacts, invoices, payments |
| HubSpot, Salesforce | Read and write | Contact lookup by phone number, contact details, and call-log entries |
| Planning Center Online | Read | Member names, email addresses and giving records, on an import you start |
| Slack, Microsoft Teams, PagerDuty | Write | Alert titles and summaries sent to a webhook you supply; these can include device and user names |
| Storage you nominate (for example Amazon S3, Google Cloud Storage, Cloudflare R2, Wasabi, MinIO, SharePoint) | Write | Migrated mail and files, written to your own storage account |
Changes to Sub-Processors will be announced by email to the Controller's primary account contact, or to an address the Controller designates. Questions? Submit a request. Written notice may also be sent to [email protected].
7. International data transfers#
The Processor is based in the United States. Customer Data held in the Platform's own hosting, database and backup storage is stored at rest in the United States; this commitment is stated at country level. Sub-Processors listed in Annex III may process data elsewhere as described there; in particular, AI inference requests sent to Azure AI Foundry may be processed transiently in Azure regions outside the United States.
Voice. Where the Controller uses Voice features, live call audio and derived transcripts pass through the real-time media, speech-recognition, speech-synthesis, and carrier Sub-Processors listed in Annex III above.
For Controllers in the European Economic Area (EEA) or United Kingdom who transfer Personal Data to the Processor in the United States, the applicable transfer mechanism is Standard Contractual Clauses (SCCs) as approved by the European Commission. Where a specific Controller requires executed SCCs or an addendum to this DPA, please submit a request; written notice may also be sent to [email protected]. Requests are reviewed case by case.
8. Data Subject rights assistance#
The Processor shall assist the Controller in responding to Data Subject rights requests. Upon receiving a Data Subject request directly, the Processor will forward it to the Controller within 5 business days.
The Platform includes a self-service data export and deletion facility available through account settings. The Processor provides technical capabilities to support the following rights:
- Right of access: data export in JSON format through account settings
- Right to rectification: data correction through the Platform interface
- Right to erasure: deletion requests honored within 30 days of a verified request
- Right to data portability: JSON export available
- Right to restriction of processing: submit a request; written notice may also be sent to [email protected]
9. Breach notification#
In the event of a Personal Data breach, the Processor shall notify the Controller without undue delay and, where feasible, within 72 hours of becoming aware of the breach. Notification shall be sent to the primary email address associated with the Controller's account and shall include, to the extent available at the time:
- A description of the nature of the breach, including the categories and approximate number of Data Subjects and Personal Data records concerned
- The name and contact details of the Processor's data protection contact
- A description of the likely consequences of the Personal Data breach
- A description of the measures taken or proposed to address the breach and mitigate its effects
If full information is not available within 72 hours, the Processor shall provide available information promptly and supplement it as more becomes available.
10. Audit rights#
The Processor shall make available to the Controller all information necessary to demonstrate compliance with GDPR Article 28 and allow for audits, subject to the following conditions:
- The Controller shall provide at least 30 days' written notice of an intended audit to [email protected], and should also submit a request so the notice is tracked.
- Audits may be conducted no more than once per year unless required by a supervisory authority or following a confirmed Personal Data breach.
- The Processor will provide security certifications, third-party assessments, and compliance documentation upon request to satisfy audit obligations.
- Audits shall be conducted during normal business hours, shall not unreasonably interfere with the Processor's operations, and shall not involve access to other customers' data.
- The Controller shall bear all costs of audits conducted by or on behalf of the Controller.
11. Term and termination#
This DPA is effective for the duration of the Subscription Agreement between the parties and terminates automatically upon termination or expiration of the Subscription Agreement.
Upon termination, the Processor shall, at the Controller's election, delete or return Customer Data as described in Section 3.7 (Deletion and Return). Customer Data is available for export during the 90-day export window following termination. After the export window, Customer Data is permanently deleted from production systems. Backup copies are retained only until the applicable backup retention period or storage lock expires (currently up to 12 months for database long-term backups and up to 365 days for write-once backup storage), are restricted from normal use during that period, and are then deleted on the applicable cycle. Financial records are retained for 7 years as required by applicable law.
Sections 3.8 (Audit), 5 (Security Measures), 9 (Breach Notification), 10 (Audit Rights), 13 (Liability), and 14 (Governing Law) survive termination of this DPA.
12. CCPA service provider obligations#
To the extent that the CCPA applies, the Processor shall act as a "Service Provider" as defined under the CCPA. The Processor:
- Shall not sell or share (as those terms are defined under the CCPA) Personal Information received from the Controller.
- Shall not retain, use, or disclose Personal Information for any purpose other than performing the Services specified in the Subscription Agreement, or as permitted by the CCPA.
- Shall not retain, use, or disclose Personal Information for any commercial purpose other than providing the Services.
- Shall not combine Personal Information received from the Controller with Personal Information received from or collected from other sources, except as permitted by applicable law.
- Shall comply with applicable sections of the CCPA and shall provide the same level of privacy protection as required by the CCPA.
13. Liability#
Each party's liability under this DPA is subject to the limitations and exclusions set out in the Subscription Agreement (Terms of Service), including the aggregate liability cap in the Limitation of Liability section of those Terms. Nothing in this DPA limits either party's liability for: (a) death or personal injury caused by negligence; (b) fraud or fraudulent misrepresentation; or (c) any liability that cannot be limited or excluded under applicable law.
14. Governing law#
This DPA and any disputes arising out of or related to it shall be governed by and construed in accordance with the laws of the State of Indiana, United States, without regard to conflict of laws principles, consistent with the governing law provisions of the Subscription Agreement.
15. Changes to this DPA#
The Processor may modify, update, or replace this DPA at any time, at its sole discretion, to reflect the fast-evolving nature of the Services, changes in applicable data protection law, or changes in the Processor's practices. The current version is published online as this Help Center article and, except as provided below, takes effect upon posting; the Processor is not obligated to provide individual or advance notice of general updates. The version published in this Help Center article is always the current, governing version and supersedes all prior versions, and the Processor will update the "Effective date" and version number above whenever it makes a change. It is the Controller's responsibility to review this DPA periodically, and continued use of the Services after an updated DPA is posted constitutes acceptance of it.
Preservation of notice commitments. This general right to update the DPA does not override, waive, or reduce the specific notice and objection commitments made elsewhere in this DPA, which continue to apply on their stated terms, including, without limitation, the Processor's obligation under Section 3.4 and Section 6 (Annex III) to inform the Controller of any addition or replacement of a Sub-Processor and to give the Controller an opportunity to object, the 72-hour personal-data-breach notification under Section 9, and the audit rights under Section 10. Where an individual Controller has executed a countersigned or negotiated version of this DPA (or Standard Contractual Clauses) as a standalone agreement, that executed version governs the relationship between the parties and controls over this online version to the extent of any conflict, and it will not be amended except in accordance with its own terms.
16. Acceptance and incorporation#
This DPA is incorporated by reference into, and forms part of, the Subscription Agreement (Terms of Service). By accepting the Terms of Service and using the Services, the Controller accepts and agrees to be bound by this DPA. Consistent with GDPR Article 28, no separate signature or countersignature is required for this DPA to be binding. The version posted in this Help Center article is the operative agreement and governs the parties' relationship, as updated from time to time in accordance with Section 15 and the Sub-Processor notice provisions above. The page at theonestack.com/legal/dpa redirects or will redirect to this article and is not the governing copy; if any other copy of this DPA differs from this Help Center article, this article controls (subject to any separately executed version as described in Section 15).
Keeping a copy for your records. Because this posted DPA is the operative agreement, you do not need a countersigned copy for it to apply to your account. Use your browser's print or save-as-PDF function to keep a copy for your compliance records.
Signed copies. If your procurement process requires a signed DPA or executed Standard Contractual Clauses, submit a request (written notice may also be sent to [email protected]). We review these requests case by case. This posted DPA is not an offer to countersign, and a request does not create a separately signed agreement unless both parties execute one.
Related: Privacy Policy · Terms of Service · Acceptable Use Policy · Subprocessors · Trust at The One Stack
The email addresses on this page are for written and legal notices. For the most reliable response, please also submit a request; for security vulnerabilities, report a security issue.
Was this article helpful?