...
Issue events are sent from Jira to the app in the form of JSON format webhooksWebhooks. If a Notification Mapping is configured in the app for the related project, the data is stored in encrypted file storage.
...
Some configuration/data that you create is expected to be used repeatedly and is therefore retained for as long as your subscription is active, that includes:
Profiles
Test Cases
Static Resources
Inbound/Outbound mail/transport configurations
Templates
Webhook Data from issue event webhooks events are retained on underlying storage for up to 7 days from receipt, at which point they are scheduled for removal as enforced by AWS bucket policy .If you have JEMHC Auditing enabled(visibility and access to that data is currently restricted to 1h)
Audit Data (where Auditing is enabled):
Inbound emails (up to 10MB) and auditing meta-data about processing is retained for 30 days from receipt, at which point they are scheduled for removal as enforced by AWS bucket policy
Outbound emails (up to 10MB) and auditing meta-data about sending is retained for 30 days from sent, at which point they are scheduled for removal as enforced by AWS bucket policy
...
We have no access to your Jira instance, issues, or your JEMHC configuration.
Backoffice Console App
We have a back office management app through which we can monitor a variety of JEMHC and instance specific data
System Notification Email Addresses
High level aggregate usage history
JEMHC License transition history, current license status, DataPack purchase history and related usage
JEMHC System Status (as linked on the JEMHC app console) showing inbound/outbound status of connections and so on. Catchemail addresses are not shown.
Logging
Our application logs are transitory and not retained and periodically destroyed.
...