Sub-processors

How this list is written

Each entry names the function performed, the data it receives, and why it receives it. Vendor identities are shared during procurement under a mutual non-disclosure agreement, and to customers with a signed data processing addendum.

The function is the commitment, and the function is stable. The vendor behind a function can change at contract renewal, so a public brand list would be wrong the day it changed — and a list that is wrong is worse than one written at the level we can keep accurate.

Sub-processor functions

Data categories below describe what the function receives, not everything held by the platform.

• Signing provider — completes signature capture on documents you send. Receives document content plus signer name and contact details for the duration of the signing session; the working copy is deleted after the signed file is captured.
• Cloud infrastructure — runs the application, database, cache, and queues. Receives all data stored by the platform.
• Document storage — holds uploaded and completed files. Receives document content. Enterprise tenants can point this at storage they already operate.
• Email delivery — sends signing invitations, reminders, and one-time passcodes. Receives recipient email address and message content.
• SMS delivery — sends one-time passcodes and reminders. Receives recipient phone number and message content.
• Messaging delivery — sends signing links and reminders over WhatsApp where a tenant enables it. Receives recipient phone number and message content.
• Payment processing — bills tenant subscriptions. Receives the billing contact and the payment method details needed to charge a subscription.
• Error monitoring — receives application error diagnostics from our own code, configured to exclude document content.

Where processing happens

Processing takes place in the European Union and the United States depending on the function. EU-only residency is available for eligible plans and regulated workflows; confirm regional requirements before rollout.

Changes to this list

Additions and replacements are published on this page. Customers with a signed data processing addendum can ask to be told before a new function is added, and to object on the terms of that addendum.