FAQ / Security & data

What sub-processors do you use?

Microsoft (M365 as the primary substrate, covered by your existing relationship with Microsoft) and DocuSign when customers enable the integration. We maintain the current list as part of our DPA.

The short list

The sub-processor list is deliberately short because the architecture is built on your existing M365 tenant rather than on a stack of additional cloud services:

  • Microsoft — as the underlying platform (SharePoint, Entra, Purview). Already part of your M365 relationship with Microsoft; we don’t introduce Microsoft as a new sub-processor.
  • DocuSign — only when customers enable the DocuSign PAdES integration. DocuSign’s role is signing-ceremony-only; documents return to SharePoint as the authoritative version.

What’s not on the list

  • We don’t use analytics sub-processors on your document content.
  • We don’t use hosting sub-processors beyond Microsoft’s M365.
  • We don’t use external AI/ML training providers.

GDPR Article 28 scope

For customers running GDPR programs, the Article 28 sub-processor review for our product is simple: the only net-new entity beyond your existing Microsoft relationship is DocuSign (and only if enabled). For customers not using DocuSign, our product adds zero sub-processors to your existing DPA scope.

This is a meaningful difference from platforms that come with a dozen sub-processors (analytics, hosting, CDN, monitoring, ML providers), each of which expands Article 28 scope and requires periodic review.

Current DPA

Our data-processing addendum is available to customers during contracting. The sub-processor list is part of that document; any changes are notified in advance per Article 28(2) requirements.

Question not on this list?

A 30-minute assessment is usually the fastest way to get a specific answer to a specific question about your organization's profile.