Registration / System Notifications / Life Cycle
As part of registering to use JEMHC, we When your instance installs JEMHC, or, is rebooted as part of maintenance with JEMHC installed (but unlicensed) JEMHC will create some basic record of the installation. We store Billing Contact email addresses, and enable further email addresses to defined for administration notifications (JEMHC > Licensing > System Notifications). The Company doesn't manage customer data that is stored in our system, its not The Company's data. For example, a contractor that setup a cloud instance and used her real name and email, was set as the billing contact. JEMHC notifies the billing contact about usage every month but they no longer work 'for the company', we can't fix that, we don't access or change customer data.
https://mail.google.com/ (Full access to Google Mail so JEMHC can read, send and delete processed emails)
https://www.googleapis.com/auth/userinfo.email (JEMHC can autocomplete the username in the SMTP/IMAP configuration form)https://www.googleapis.com/auth/drive.file (View and manage Google Drive files and folders for storage)
The usage of these permissions within JEMHC is as follows:
Once authorized and configured, JEMHC will be able to retrieve email from the linked account(s) and process as described below.
Once authorized and configured, JEMHC will be able to store attachments uploaded through the JEMHC External Attachment feature within Jira into Drive. The data stored in Drive are then exposed by JEMHC through that same External Attachment feature. See /wiki/spaces/JEMHC/pages/81887292 for more.
JEMHC processes email supplied by users, using connectivity mechanisms controlled by the user. By default, the action of email retrieval:
stores those complete emails in encrypted form in the JEMHC database. Customers can opt out of the short term auditing email-retention (re-enabling requires support intervention). Opting out makes diagnosing email related problems much harder to resolve, if not impossible.
stores subject, sender (from:), and recipients (to:, cc:) email address in JEMHC database, unencrypted.
As part of supporting email only users, JEMHC stores non-Jira email addresses in TEXT custom fields, unencrypted.
Email content is stored in Jira in plain text as issue summary/description/comment.
JEMHC received Regardless of whether you have a license present for JEMHC or not, if JEMHC installed, the issue https://ecosystem.atlassian.net/browse/AC-1620 means that your Jira will send us issue webhook data for every IssueEvent in Jira your instance (over SSL). JEMHC stores this event data in unencrypted form in the JEMHC database, retaining only the most recent events ( This data should ideally be encrypted, https://thepluginpeople.atlassian.net/browse/JEMHC-34 will track that).
JEMHC will by default attach files added to issues to outbound emails.
JEMHC will by default store in the JEMHC database, the full email content of recently sent mail.
After sending email, JEMHC retains a recent history of the event, this includes email addresses and subject, currently stored in clear. https://thepluginpeople.atlassian.net/browse/JEMHC-35 will track the encryption of summary.