DocuSign plays two different legal roles depending on the situation: it controls your account and marketing data on its own terms, but processes document content strictly on behalf of the business that sent you the document.
This analysis describes what DocuSign's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This distinction determines which privacy protections apply to your data. For document content, your rights may depend on the business that sent you the document rather than DocuSign directly, which could limit your direct recourse with DocuSign.
If you receive a document to sign from a company using DocuSign, that company, not DocuSign, is primarily responsible for how your document data is handled. Your privacy rights for that content must be exercised with the sending organization, not necessarily with DocuSign.
How other platforms handle this
When Okta provides its products and services to its customers (e.g., organizations that use Okta to manage their workforce or Auth0 to manage their customer identity), Okta processes personal data on behalf of those customers as a data processor. In those cases, the customer is the data controller a...
When we provide the Service to our customers, we act as a data processor on behalf of those customers. Our customers are the data controllers, meaning that they determine the purposes and means of the processing of personal data that is submitted into the Service. If you are an end user of a custome...
When Zendesk processes personal data on behalf of its customers, Zendesk acts as a data processor and the customer acts as the data controller. In those cases, the customer's privacy policy and data processing agreement with Zendesk govern the processing of that data, not this Privacy Notice. If you...
Monitoring
DocuSign has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"Docusign may be a 'data controller' or a 'data processor' (or both) depending on the type of personal information and the context in which it is processed. When Docusign determines the purpose and means of processing personal information, we act as a data controller. When Docusign processes personal information on behalf of its customers pursuant to their instructions (for example, when customers use Docusign products to manage their own documents and data), we act as a data processor.— Excerpt from DocuSign's DocuSign Privacy Statement
(1) REGULATORY LANDSCAPE: The controller/processor distinction is a foundational GDPR concept governed by Articles 4, 24, and 28. Under GDPR Article 28, data processors must operate under a binding contract with controllers. CCPA similarly distinguishes service providers from businesses. The allocation of responsibility between DocuSign and its enterprise customers has direct implications for liability and data subject rights fulfillment. (2) GOVERNANCE EXPOSURE: High. Enterprises using DocuSign for document workflows bear primary accountability under GDPR and CCPA for the personal data contained in those documents. Failure to execute a compliant Data Processing Agreement with DocuSign, or to ensure DocuSign's sub-processor chain is documented, exposes enterprise customers to regulatory risk. (3) JURISDICTION FLAGS: EU and UK organizations have the most acute exposure given GDPR Article 28 requirements for written processor contracts. California organizations must classify DocuSign as a service provider under CPRA to restrict cross-context behavioral advertising from document data. (4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement and legal teams should confirm that a current, GDPR-compliant Data Processing Agreement is in place with DocuSign and that it reflects the current sub-processor list. The DPA should include restrictions on DocuSign using document content for its own business purposes. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should audit whether their internal privacy notices to employees or customers accurately reflect DocuSign's role as a processor for document data. Data mapping exercises should distinguish between DocuSign-controlled account data and processor-held document content.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
We read the privacy policies and terms of service of 38 AI platforms. Here is what they say about training, retention, arbitration, and liability.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This distinction determines which privacy protections apply to your data. For document content, your rights may depend on the business that sent you the document rather than DocuSign directly, which could limit your direct recourse with DocuSign.
If you receive a document to sign from a company using DocuSign, that company, not DocuSign, is primarily responsible for how your document data is handled. Your privacy rights for that content must be exercised with the sending organization, not necessarily with DocuSign.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DocuSign.