See https://support.esign-app.com for eSign Documentation and Support
Data Residency and Access Transparency Policy
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 AWS. See https://aws.amazon.com/compliance/iso-certified/ for more information on AWS security compliance and accreditation.
The following table identifies the Jira data that is accessed temporarily by the eSign services and why each is necessary.
Atlassian API | Fields Accessed (Not Stored) | Purpose |
|---|---|---|
System | System and Space settings | Settings for the Confluence environment and spaces (e.g. default locale and timezones are accessed) by eSign. Locale and timezone are required to format and display dates/times for the users. |
Content/Pages | Page metadata | Information about Confluence pages, versions and attachments is fetched to enable document management |
User Information | Display Name, Time zone and Locale, E-mail Address | The user name, time zone and locale are retrieved to populate the signee name and local date/time for the electronic signature. E-mail address is used to send transactional notification email (e.g. Reviews Assigned, and Pin Resets). User information is not permanently stored by eSign. |
Data Processing Locations
eSign for Confluence has 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.
For customers with regional compliance requirements, pinning the location to within a specific region ensures that signature data processing occurs within that region.
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
Location | eSign Hosted Region (AWS) |
|---|---|
Default | US East region |
European Union | Europe (Frankfurt) region |
Germany | Europe (Frankfurt) region |
USA | US East region |