---
title: "Docusign IAM / CLM (Iris) (Docusign, Inc.)"
url: "https://ailawframework.com/software/docusign"
type: "software_profile"
site: "AI Law Framework"
id: "docusign"
vendor: "Docusign, Inc."
category: "Legal-specific"
segment: "Contract review and CLM"
confidence: "high"
last_reviewed: "2026-10-10"
---

# Docusign IAM / CLM (Iris) (Docusign, Inc.)

> Public-company agreement platform: create, sign, store and analyse contracts with Iris AI, CLM workflows and optional agents, including an Australian data-centre region.

Canonical page: https://ailawframework.com/software/docusign  
Last reviewed: 2026-10-10

Site index for agents: https://ailawframework.com/llms.txt

Plan covered: Docusign IAM and CLM with Iris AI, including Lexion-derived review/insights. Review eSignature-only, Notary, FedRAMP/GovRAMP, IAM Starter/Standard self-serve and any signed Order Form separately.

## Capabilities

- Contract drafting
- Contract review and redlining
- Clause libraries and playbooks
- Document automation
- Agentic workflows

## Key facts

| Fact | Value |
| --- | --- |
| Deployment | SaaS |
| Hosting regions | Australia, United States, European Union / EEA, Canada, Another named location |
| Australian region | Australian region available |
| Model providers | Microsoft Azure OpenAI, Google Vertex AI (Gemini), in-house models |
| Assurance | SOC 2 Type II, ISO 27001, PCI DSS |
| Training on customer content | Opt-out |
| Retention | Agreement Data stays in the provisioned region. MSA allows de-identified Usage Data for product improvement. AI training of Docusign models requires MSA consent plus an account-level AI data controls setting (default on if consented; 30-day wait; FedRAMP/GovRAMP excluded). Third-party LLMs: no persistent storage, no training of those providers' models for other customers. |
| Integrations | SSO, Microsoft Word, Salesforce, API, MCP, 1000+ App Center integrations |
| Legal content coverage | Iris and CLM analyse the customer's agreements. They are not a licensed primary-law research database. Lexion AI was acquired to deepen contract understanding inside IAM. |
| Pricing | Public IAM + eSignature list: Starter USD 45/user/month (annual); Standard USD 50/user/month with 3-user minimum. CLM and enterprise IAM are Order Form. AU data residency is available for eSign, IAM and CLM. |
| Australian presence | Yes. Data residency table: Australia is available for eSign, IAM and CLM. Trust Centre lists Azure Australia production. MSA for AU ship-to addresses: NSW law, non-exclusive NSW courts. Microsoft Azure AI Services include a North Sydney entity on the subprocessor PDF. Checked 2026-10-10. Vendor page: “Docusign stores your Agreement Data in one of five geographically distinct data center regions (U.S., Canada, Europe, Australia, or Japan).” (https://www.docusign.com/trust/privacy/data-mgmt-privacy). Recorded as Australian region available. |
| Website | https://www.docusign.com/ |

## What the research found

| Topic | Status | Finding | Open question | Sources |
| --- | --- | --- | --- | --- |
| IAM and CLM versus eSign-only | Public claim only | This profile covers Docusign IAM and CLM with Iris AI (including Lexion-derived review, extraction and Q&A). eSignature-only, Notary, IAM Starter/Standard self-serve, FedRAMP/GovRAMP and Professional Services have different schedules. Public MSA, DPA, Security Attachment and AI Attachment apply unless an Order Form says otherwise. Existing eSign/CLM customers are told nothing changes until they take an IAM plan in their region. | Confirm the Order Form SKUs (IAM versus CLM versus eSign), Australia region, whether Iris/Agents/MCP are in scope, and whether FedRAMP-style AI-training exclusion applies. | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign completes acquisition of Lexion](https://www.docusign.com/company/news-center/docusign-completes-acquisition-of-lexion-to-accelerate-intelligent-agreement-management) |
| Five regions including Australia; Azure migration | Public claim only | Agreement Data is stored in one of five regions: US, Canada, Europe, Australia, Japan. eSign, IAM and CLM are all available in Australia; CLM is not in Canada or Japan. Region is chosen at provisioning (or by billing address for web signup) and cannot later be moved except by cloning via Admin API. Traffic is migrating from on-prem servers to Microsoft Azure without changing residency of Agreement Data. Checked 2026-10-10. Vendor page: “Docusign stores your Agreement Data in one of five geographically distinct data center regions (U.S., Canada, Europe, Australia, or Japan).” (https://www.docusign.com/trust/privacy/data-mgmt-privacy). Recorded as Australian region available. | Confirm our production, backup and Iris inference region is Australia, including Azure OpenAI and Vertex, before we send the first envelope. | [Docusign data residency](https://www.docusign.com/privacy/data-residency); [Docusign Trust Centre](https://www.docusign.com/trust); [Docusign IAM / CLM (Iris) hosting statement checked 2026-10-10](https://www.docusign.com/trust/privacy/data-mgmt-privacy) |
| Iris, CLM, Agents, MCP | Public claim only | IAM: create, commit and manage agreements. CLM: lifecycle automation, 100+ pre-trained extraction models, AI-assisted review and generative Q&A via Iris. Agents draft, review and orchestrate agreements. An MCP product page describes connecting Docusign to external AI tools. Lexion was acquired (31 May 2024) for document understanding inside IAM. | Which of Iris Q&A, AI-assisted review, Agents and MCP will be enabled on our AU tenancy, and which remain preview? | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm); [Docusign Agents](https://www.docusign.com/products/agents); [Docusign MCP](https://www.docusign.com/products/mcp); [Docusign completes acquisition of Lexion](https://www.docusign.com/company/news-center/docusign-completes-acquisition-of-lexion-to-accelerate-intelligent-agreement-management) |
| Australian region; NSW law for AU orders | Public claim only | AU data centre is listed for eSign, IAM and CLM. MSA 12.1(b): if the Order Form ship-to address is Australia, NSW law and non-exclusive NSW courts apply; claims within two years. Limited Transaction Data and login may still be processed outside the region. Gemini 'global endpoints' are listed for AI-assisted web form creation. | Will Iris inference, Azure OpenAI, Vertex Gemini and support access stay in Australia for our account, and is the Gemini global endpoint off? | [Docusign data residency](https://www.docusign.com/privacy/data-residency); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| IAM Starter from USD 45/user/month; CLM on Order Form | Public claim only | Public IAM + eSignature: Starter USD 45/user/month annual (100 envelopes/user/year, AI search/management/analysis); Standard USD 50/user/month with 3-user minimum and unlimited web envelopes. CLM and larger IAM are enterprise. MSA: unpaid fees remain due; taxes extra. | Provide an AU-region quote for our users, CLM, Iris/Agents and envelope volume, including GST, auto-renewal and overage. | [Docusign IAM plans and pricing](https://ecom.docusign.com/plans-and-pricing/iam); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa) |
| SSO, Word, App Center, MCP, API | Public claim only | IAM/App Center: 1000+ pre-built integrations, APIs, mobile app. Security Attachment covers identity and access management. MCP is a published product path to external AI tools. Third-Party Services in the MSA are the customer's risk unless the Order Form says otherwise. | Demonstrate SAML/OIDC SSO-only, Word/CLM round-trip, and whether MCP is off until we enable it. | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign MCP](https://www.docusign.com/products/mcp); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services) |
| Follow-the-sun; eDocuments encrypted to staff | Public claim only | Subprocessor page: follow-the-sun support from any Docusign Group Member; authorised employees may access limited Personal Information but not the contents of eDocuments, which remain encrypted and stored in the sending account's region. Support access to Transaction Data is called out on the residency page. | What are severity response times for our AU IAM/CLM tenancy, and can support staff ever decrypt Agreement Data? | [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list); [Docusign data residency](https://www.docusign.com/privacy/data-residency) |
| IDC MarketScape; no independent hallucination study found | Public claim only | Homepage banner: Leader in 2026 IDC MarketScape for Signing Workflows. Iris is described as trained on decades of contract data. No Stanford RegLab or Vals AI result for Iris/Lexion review was found in this pass. | Provide measured accuracy for Iris extraction/Q&A on a hold-out set of our contracts, separate from IDC signing-workflow rankings. | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm) |
| Agreements, CLM and AI review — not court filings | Public claim only | IAM/CLM are for creating, negotiating, signing and managing commercial agreements, with AI review and Q&A over the repository. They are not a court e-filing or primary-law research product. Outputs used as legal advice remain the customer's responsibility under the MSA. | Which of our playbook review, extraction and repository Q&A tasks will use Iris, and which (advice, deeds, court filings) stay out of scope? | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm) |
| Agreement Data; optional AI training and MCP | Not confirmed | Docusign holds confidential agreements. AI training of Docusign models requires MSA consent and an account toggle. MCP and third-party integrations send data outside the region as those providers determine. Recipients outside the region still leave Agreement Data stored in the sender's region. | Confirm AI data controls are off for our AU accounts, MCP is disabled, and what region/subprocessor description we can give clients. | [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html); [Docusign MCP](https://www.docusign.com/products/mcp); [Docusign data residency](https://www.docusign.com/privacy/data-residency) |
| Hybrid in-house plus Azure OpenAI and Vertex Gemini | Public claim only | AI FAQs: hybrid proprietary/open-source models plus third-party LLMs via API — Microsoft Azure OpenAI Service and Google Vertex AI including Gemini. Subprocessor PDF (IAM/CLM): Azure OpenAI and Azure Document Intelligence follow the provisioning location including Australia; Gemini also listed for AU among others; Gemini global endpoints for AI-assisted web form creation. Third-party providers: no persistent storage; no training of those providers' models for other customers; anonymised data may customise Docusign-only models. | Which Azure OpenAI and Gemini models/regions process our AU IAM and CLM tenancy, and is the Gemini global endpoint excluded? | [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| Published list dated 18 September 2026 | Public claim only | Public list last updated 18 September 2026, split by data-centre location, purchased services and optional features. Group members provide follow-the-sun support. Azure and Equinix are example EU infrastructure subprocessors. IAM/CLM PDF rows name Azure AI Services and Google Vertex AI by provisioning location including Australia. SMS/ID-verification vendors apply only if those features are used. | Provide the AU-region subprocessor extract for IAM+CLM+Iris, with 30-day notice/objection, including Azure OpenAI and Vertex. | [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| MSA consent plus account toggle; third-party LLMs not trained for others | Public claim only | Docusign will not use account data to improve its AI models unless the organisation agreed in the service agreement and the AI data controls setting is on (default on after consent; 30-day wait; turn off per account to withdraw). Previously anonymised data is retained because it cannot be unlinked. FedRAMP/GovRAMP do not share data for AI training. Third-party LLMs: customer data is not used to train those providers' models for other customers. MSA 4.3: de-identified Usage Data may be used to train and improve products. | Confirm in the Order Form that AI data controls start off for every AU account, that Lexion-era data is not in training corpora, and that Usage Data is not our Agreement Data. | [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html); [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa) |
| Usage Data and bug-reporting FAQs | Public claim only | MSA 4.3: Usage Data, after de-identification, may be used for analytics, marketing and training/improving products, disclosed only in aggregate. Support FAQs cover reporting bugs and unexpected AI issues. In-product thumbs-up/down for Iris was not specified in the pages reviewed. | Is any in-product Iris feedback used to train models, and can we disable it without turning off the feature? | [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html) |
| Region-bound Agreement Data; no public day count | Not confirmed | Residency page describes where Agreement Data and CLM documents/metadata sit, not how many days they are kept after a matter closes. Transaction Data may be hashed and copied across regions. AI-training wait is 30 days after consent, not a live-matter retention schedule. | Provide a numbered retention schedule for envelopes, CLM documents, Iris prompts/outputs, logs and backups in the AU region. | [Docusign data residency](https://www.docusign.com/privacy/data-residency); [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html) |
| Admin controls; training anonymisation is irreversible | Public claim only | Customers manage Agreement Data in-product. Turning off AI data controls stops new ingestion; previously aggregated anonymised training data is retained because it cannot be linked back. No public post-termination deletion certificate or LLM-purge day count was found beyond third-party 'no persistent storage'. | On exit, what is deleted from the AU region, backups and Azure OpenAI/Vertex, within how many days, with what certificate? | [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html); [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html); [Docusign data residency](https://www.docusign.com/privacy/data-residency) |
| Support cannot read eDocuments; follow-the-sun | Public claim only | eDocuments are encrypted as to Docusign and stored in the sending account's region; follow-the-sun staff may see limited Personal Information and Transaction Data, not document contents. MSA 11.2: required legal disclosure with prompt notice unless prohibited. Security Attachment: dedicated incident response team. | Is any break-glass access to Agreement Data logged to us, and will you notify us of legal process seeking our contracts? | [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services) |
| Admin, SSO and AI data controls | Public claim only | Account administrators control users and the AI data controls setting. Security Attachment includes identity and access management. SSO is a standard enterprise control on the security programme; SCIM was not confirmed in this pass. | Do you support SAML/OIDC SSO-only, MFA enforcement and SCIM on our AU IAM/CLM account? | [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services); [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html) |
| AES-256 application-level encryption | Public claim only | Product security page: application-level AES-256 encryption; ISO 27001-certified and SOC-audited geo-dispersed datacentres. AI FAQs: data encrypted in transit and at rest. eDocuments encrypted as to Docusign. CMK was not specified on the pages reviewed. | Confirm TLS 1.2+ and AES-256 for AU storage, backups and Azure OpenAI/Vertex paths, and whether CMK is available on IAM/CLM. | [Docusign product security](https://www.docusign.com/trust/security); [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| SOC, ISO 27001, PCI DSS via Security Attachment | Public claim only | Security Attachment: Docusign will make available ISO/IEC 27001, PCI DSS and SOC reports. Product security: ISO 27001-certified and SOC-audited datacentres. DPA s.9: SOC, ISO, NIST, PCI DSS or similar on request; customer audit no more than once per 12 months if reports are unsatisfactory. Reports were not downloaded. | Provide current SOC 2 Type II and ISO 27001 reports covering AU IAM/CLM and Iris/Azure OpenAI, including period and entities in scope. | [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services); [Docusign product security](https://www.docusign.com/trust/security); [Docusign Data Protection Attachment](https://www.docusign.com/legal/terms-and-conditions/data-protection-attachment-docusign-services) |
| Public MSA; NSW law for AU; 12-month cap; confidentiality carved out | Public claim only | Public MSA. AU ship-to: NSW law, non-exclusive NSW courts, two-year limitation. Aggregate liability capped at amounts paid for the Docusign Services in the 12 months before the first event, with carve-outs for third-party claims, confidentiality breach, death/bodily injury/property from negligence, gross negligence/willful misconduct, and unpaid fees. DPA and Security Attachment are incorporated. Customer must not use ML output to train other systems. | Will our Order Form lock AU residency, AI-training off, and keep the confidentiality carve-out for a data incident affecting Agreement Data? | [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign Data Protection Attachment](https://www.docusign.com/legal/terms-and-conditions/data-protection-attachment-docusign-services); [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services) |
| Region at rest; Transaction Data and Gemini global endpoints | Public claim only | Agreement Data at rest stays in the provisioned region (Australia available). Limited Transaction Data may be hashed and copied across regions; login may redirect; support is global; third-party integrations follow the third party. BCRs and SCCs are referenced. Vertex Gemini global endpoints are listed for web-form creation. Azure OpenAI location follows provisioning, including Australia. | Name every country of Iris inference and support access for our AU account, including Gemini global endpoints, in writing. | [Docusign data residency](https://www.docusign.com/privacy/data-residency); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| Without undue delay; no public hour count | Public claim only | DPA s.6 and Security Attachment: notify Customer without undue delay (and within timeframes required by law) upon becoming aware of a Data Incident/Breach, unless prohibited. Customer decides whether to notify data subjects and regulators and should coordinate public statements with Docusign. No 72-hour figure is in the public DPA text reviewed. | Within how many hours of discovering a suspected incident affecting our AU Agreement Data will you notify us, and will you support an NDB assessment? | [Docusign Data Protection Attachment](https://www.docusign.com/legal/terms-and-conditions/data-protection-attachment-docusign-services); [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services) |
| IAM rollout, Azure migration, subprocessor updates | Public claim only | IAM plans become available by region; existing eSign/CLM continue until the customer takes a new plan. eSignature traffic is migrating to Azure. Subprocessor list dated 18 September 2026. Agents and MCP are new surfaces. Region cannot be changed after provisioning except by clone. | Will you give 30-day notice before adding LLM providers, turning on MCP, or changing AU inference location? | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign data residency](https://www.docusign.com/privacy/data-residency); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list); [Docusign MCP](https://www.docusign.com/products/mcp) |
| In-product export; clone to another region; training data stays anonymised | Not confirmed | Customers can export Agreement Data in-product and clone accounts to a new region via Admin API. No public post-termination window or certified deletion of AU backups and LLM copies was found. Anonymised AI-training data from prior consent is retained. | How do we export CLM documents, playbooks, audit trails and Iris outputs on exit, and when are remaining AU and LLM copies deleted? | [Docusign data residency](https://www.docusign.com/privacy/data-residency); [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html) |
| App Center, MCP, third-party services | Not confirmed | App Center integrations and APIs can send Agreement Data outside the region as the third party determines. MSA: Third-Party Services are the customer's contract unless the Order Form says otherwise. MCP connects Docusign to external AI tools. SMS/ID-verification subprocessors apply only if those features are used. | Which App Center and MCP connectors are on by default, what they send outbound, and how do we disable them without a ticket? | [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management); [Docusign MCP](https://www.docusign.com/products/mcp); [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) |
| Iris over the agreement repository | Public claim only | Iris Q&A and Agreement Manager are described as operating on the customer's agreements. Open-web search as an Iris feature was not found. MCP would let an external assistant bring its own tools, including web search, unless blocked. | Confirm Iris does not call the open web on our contracts, and how MCP assistants are blocked from web search using our repository. | [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm); [Docusign MCP](https://www.docusign.com/products/mcp) |
| Agents and MCP orchestration | Not confirmed | Agents are marketed to draft, review and orchestrate agreements. MCP lets other applications reach Docusign workflows. Public MSA/AI FAQs do not describe a kill-switch or which agent steps can send envelopes without a named approver. | Which agent/MCP actions can send or change an agreement without a named approver, and how do we freeze them immediately? | [Docusign Agents](https://www.docusign.com/products/agents); [Docusign MCP](https://www.docusign.com/products/mcp) |
| No public clause requiring lawyer sign-off of Iris output | Not confirmed | Iris and Agents produce review comments, extractions and drafts. The MSA disclaims implied warranties and allocates professional use to the customer. No public clause requiring a qualified legal professional to approve Iris output before it is sent for signature was found. | Can we require named sign-off before an Iris redline or Agent-drafted envelope is sent, with an export of who approved which items? | [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa); [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm); [Docusign Agents](https://www.docusign.com/products/agents) |

## Notes

Could not verify: founded year; SOC/ISO reports themselves; numbered retention/deletion/incident hours; whether Gemini global endpoints apply to AU IAM. AI training of Docusign models is opt-out after MSA consent (default on). Confidentiality breach is carved out of the 12-month cap. Do not treat IDC signing-workflow leadership as an Iris accuracy study. MCP URL was scraped from the product/platform MCP page in cache — confirm live path if the site moves it.

## Sources

- [Docusign MCP](https://www.docusign.com/products/mcp) (checked 2026-09-21)
- [Docusign IAM plans and pricing](https://ecom.docusign.com/plans-and-pricing/iam) (checked 2026-09-21)
- [Security Attachment for Docusign Services](https://www.docusign.com/legal/terms-and-conditions/security-attachment-docusign-services) (checked 2026-09-21)
- [AI Data Controls Setting FAQs](https://support.docusign.com/s/document-item?language=en_US&bundleId=fzd1707173174972&topicId=dcs1708531444159.html) (checked 2026-09-21)
- [Docusign FAQs for AI](https://support.docusign.com/s/document-item?bundleId=fzd1707173174972&topicId=uss1707173279973.html) (checked 2026-09-21)
- [Docusign product security](https://www.docusign.com/trust/security) (checked 2026-09-21)
- [Docusign Data Protection Attachment](https://www.docusign.com/legal/terms-and-conditions/data-protection-attachment-docusign-services) (checked 2026-09-21)
- [Docusign IAM / CLM (Iris) hosting statement checked 2026-10-10](https://www.docusign.com/trust/privacy/data-mgmt-privacy) (checked 2026-10-10)
- [Docusign Intelligent Agreement Management](https://www.docusign.com/intelligent-agreement-management) (checked 2026-09-21)
- [Docusign Contract Lifecycle Management](https://www.docusign.com/products/clm) (checked 2026-09-21)
- [Docusign Master Services Agreement](https://www.docusign.com/legal/terms-and-conditions/msa) (checked 2026-09-21)
- [Docusign data residency](https://www.docusign.com/privacy/data-residency) (checked 2026-09-21)
- [Docusign subprocessor list](https://www.docusign.com/trust/privacy/subprocessors-list) (checked 2026-09-21)
- [Docusign Trust Centre](https://www.docusign.com/trust) (checked 2026-09-21)
- [Docusign completes acquisition of Lexion](https://www.docusign.com/company/news-center/docusign-completes-acquisition-of-lexion-to-accelerate-intelligent-agreement-management) (checked 2026-09-21)
- [Docusign Agents](https://www.docusign.com/products/agents) (checked 2026-09-21)

A product profile is research to support questions. It does not approve a product for any firm. Public product information supports questions; it does not approve a product for your firm. Verify the exact plan, settings and signed terms.