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 Heroku and AWS. See https://www.heroku.com/policy/security for more information on Heroku and the Amazon physical security infrastructure 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 Data | 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. User information is not retained or stored by eSign. |