All persistent eSign data (e.g. Documents and Signatures) resides ONLY within each Customer’s Atlassian Cloud environment (e.g. https://<customername>.atlassian.net). See the following Atlassian support article on data residency for hosted environments (https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency-and-realms/).

In operation, eSign retrieves document, page and user data via the Atlassian API to capture and apply document data and signatures. The data is persisted only within the Atlassian cloud environment; it is not permanently stored by eSign.

The eSign processing servers are hosted securely by http://Heroku.com (US) and http://Render.com (EU). See Heroku Security | Heroku and Security and Trust | Render for more information.

The following table identifies the Jira data that is accessed temporarily by the eSign services and why each is necessary.

Data Processing Locations

eSign Document Management and Training is hosted in multiple data processing locations. Customers have the option to “Pin” their eSign app location to one of the following locations via Atlassian Security administration. Once pinned, the eSign server(s) in that location will perform all signature processing for that cloud site.

Note that eSign does not permanently store any end-user data outside of the Atlassian cloud. Processing “closer” to the cloud site can provide the following benefits.

1. For customers with regional compliance requirements, pinning the location to within a specific region ensures that signature data processing occurs within that region.

2. Customers with Atlassian cloud sites located closer to the EU will notice faster response time when working with eSign as compared to the US hosted location.

See this Atlassian article for more information on Data Residency. Data Residency: Manage Where Your Data is Hosted | Atlassian. Pinning apps is available within admin.atlassian.com