What is it?

As per google:

On 25 May 2018, the most significant piece of European data protection legislation to be introduced in 20 years will come into force. The EU General Data Protection Regulation (GDPR) replaces the 1995 EU Data Protection Directive. The GDPR strengthens the rights that individuals have regarding personal data relating to them and seeks to unify data protection laws across Europe, regardless of where that data is processed.

Data Protection after 31 DEC 2020

...

For purposes of simplicity, references to GDPR will, after 31 DEC 2020 mean UK GDPR.

Definitions

GDPR terms : https://gdpr-info.eu/art-4-gdpr/

The Plugin People Ltd :"We", "Us", "The Company"

Enterprise Mail Handler for Jira (Server) : JEMH

Enterprise Mail Handler for Jira (Cloud) : JEMHC

Personally Identifying Information : PII

Introduction

What follows is a variation on the topics covered in the Atlassian Privacy & GDPR section on their licensing page.  Related to this is our Data security & privacy statement, GDPR affects Us in the following main areas:

Billing

PII data obtained through billing would only be used by us, in relation to the service(s) the customer has purchased from us.  We track and record name/email address of all customers making purchases with us directly, as part of the transaction.  We are legally required to retain history of such transactions for 7years, that includes email traffic, quotes, invoices, purchase orders, in addition to order-related spread sheets.  Where 3rd parties require details of our activities relating to sales (accounting) , personal details are removed.

Cloud

This is the largest area.  We have a cloud version of the Enterprise Mail Handler for Jira Cloud (JEMHC) that processes email from customer mailboxes and drives issue creation/update in customer Jira instances.

About JEMHC

JEMHC on installation gets the billing contact user email address, we use this to populate the JEMHC > Licensing > System Notifications > Email Addresses field.  This field is CSV, and is maintained by the Jira instance administrator not us.  We do not have functional access to your data to make changes.  We have a back office system that exposes basic system contact details to us.  JEMHC mails out to this list every month a status email summarizing JEMHC usage, if there is any.

...

• As part of support we encounter customer data regularly in the form of Email content that has processing problems.  Such information is shared by the JEMHC customer in confidence, on behalf of the sender for the sole purpose of diagnosing processing problems and improving JEMHC's ability to handle such messages.  That information is not shared with 3rd parties, and not retained by us for any reason.  We will manufacture test data as needed to replicate customer problem scenarios for internal testing purposes.

• External Storage:  As part of support ticket lifecycle, we automatically purge all issue-files when an issue is resolved.  We are considering extending this to include actual issue attachments as well, such that all JEMHC customers can do the same, if desired.

• Jira attachments: TODO, as part of our support ticket lifecycle, we will be implementing features within JEMHC to enable attachment data to be expired after a certain amount of time, ie, giving such data a guaranteed lifespan in our system.  We won't delete comments or issues as this is needed to trace recurring customer problems.

Do We use sub-processors to further process customer data?

...

Sub-Processors

How You want to change and remove your information or to ask for it not to be used

...

Who can I contact with questions regarding GDPR?

Queries about GDPR should be directed to the Plugin People Ltd Data Protection Officer at data-protection-officer@thepluginpeople.com

Data Protection Officer
The Plugin People Ltd
Pure Offices
Cheltenham Office Park
Hatherley Lane
Cheltenham
GL51 6SH
UK

...