Dropbox Sign data residency

Updated Nov 11, 2026

In this article

person icon

Data residency is available to customers on Dropbox Sign UI Premium and API Premium.

Dropbox Sign offers the following options for you to control where your documents and templates are stored:

Regional document storage within Dropbox Sign

Dropbox Sign has data infrastructure for document storage in the US, Australia, the EU, Japan, Canada, and the UK. The default region for all plans is the US. Customers on Premium plans can choose to store their documents in an alternative region.

If you choose to store your documents in an alternative region, all of your organization's at rest documents are stored in our AWS data infrastructures in the selected region. For example, documents can be stored in Frankfurt, Germany with a backup in Paris, France.

Organizational admins can let team admins manage data residency settings for their team. Team admins can then choose a different document storage region for their teams.

For example, documents stored at the organization level can be stored in the US, while documents stored by a team can be stored in the EU.

If the team admin has turned on the option, sub-team admins can also manage data residency settings for their sub-teams.

How to set the document storage location

Organization admins can update the storage location setting from the admin console.

To set the document storage location:

  1. Log in to your Dropbox Sign admin account.
  2. Click your initials.
  3. Click Admin console.
  4. Click Settings.
  5. Click Documents and templates.
  6. Go to Document controls.
  7. Select a region from the dropdown next to Data residency.
  8. If you’re an organization admin on an API plan, you can decide who can update these settings by choosing one of the following options from the dropdown under Who can change this setting?
    • Org admins/managers only
    • Team admins/managers
highlighter icon

Note: Data residency for API-created signature requests is determined by the API configuration used to create the request.

FAQs about data residency

Will documents be stored permanently in the selected region and removed from US servers?

If you choose a regional data residency option and a document is at rest, it’s stored only in that selected region. If a document is being processed (for example, when someone edits, sends, or signs it), a temporary copy of the document is moved to our US servers where processing is performed. After a document is completed (either signed or declined), no more processing is required and it'll only be stored in the preferred regions without any remaining copies in the US.

Will the signer version of a document be stored permanently in the selected region and removed from US servers?

The storage location for a signature request depends on how the request was created.

Requests sent through the Dropbox Sign app
For signature requests sent through the Dropbox Sign app, documents are stored according to the data residency setting configured for the sender’s organization or team.

Requests sent through the Dropbox Sign API
For signature requests sent through the Dropbox Sign API, documents are stored according to the data residency setting associated with the API credentials and application used to create the request. The sending user doesn’t determine the document storage location for API-created signature requests.

For example, a signature request may be sent on behalf of a user in the EU, but if the API credentials used to create the request are associated with a US-based configuration, the document may be stored in the US. 

The signer’s location also doesn’t determine where the documents are stored. If a signer in the EU signs a request stored in the US, the completed document remains stored in the US.

What determines the storage location for API requests?

For API-created signature requests, Dropbox Sign determines document storage based on the API configuration used to create the request.

The following factors don’t determine the storage location on their own:

  • The sending user’s location
  • The sending user’s data residency setting
  • The email address specified as the requester
  • The signer’s location

For signature requests sent directly through the API, the storage location is based on the account that owns the API key or API app used to create the request.

For unclaimed drafts, the storage location may change after the draft is claimed and sent. In that case, Dropbox Sign determines the storage location based on the account that sends the completed signature request.

Was this article helpful?

Let us know how why it didn't help:

Thanks for letting us know!

Thanks for your feedback!

Footer-Help