...
Ref | Business Function | Purpose of Processing | Categories of Data Subjects | Personal Data | Data Accessed By | 3rd Country / International Organisation Transfer | Safeguards | Retention | Technical and Organisational Security Measures | Lawful Basis |
|---|---|---|---|---|---|---|---|---|---|---|
1.0 | App | Reading Email Content and converting to Issues in your Jira | Your customers | Full Email Data | Jira Admins, Participants | NA | 2FA | 30 days | Transport Encryption (first hop), Encryption at rest | Article 6(1)(b) Contract |
1.1 | App | Sending Email Content from your Jira to your Customers | Your customers | Jira Issue Content | Jira Admins, Participants | NA | 2FA | 30days | Transport Encryption (first hop), Encryption at rest | Article 6(1)(b) Contract |
1.2 | App | Sending IM system status Messages to your IM Rooms | JEMHC System | n/a | IM Users | NA | NA | NA | Transport Encryption (first hop) | Article 6(1)(b) Contract |
1.3 | App | Sending IM telemetry to your IM Rooms | Your customers | Email Addresses | IM Users | NA | NA | NA | Transport Encryption (first hop) | Article 6(1)(b) Contract |
1.4 | App | Sending IM system status Messages to our Rooms | JEMHC System | Email Addresses | The Plugin People | NA | NA | 90days | Transport Encryption (first hop), 2FA to access Our Slack Message retention is 90days. | Article 6(1)(b) Contract |
1.5 | App | Auditing of Inbound/Outbound Mail Processing | Your customer Email data | Full Email Data | Jira Admins, Jira Project Admins | NA | NA | 30days | Transport encryption Email content has encryption at rest You can opt out of this retention | Article 6(1)(b) Contract |
1.6 | App | Processing Webhooks from Jira to generate emails | Issue data, Your customers Email data | Jira Issue Content, Email Addresses | Jira Admins, Jira Project Admins | NA | NA100 | 1 hour | Transport encryption Email content has encryption at rest | Article 6(1)(b) Contract |
1.7 | App | Storing/reusing historic Webhooks for use in custom Template Preview | Issue data, Your customers Email data | Jira Issue Content, Email Addresses | Jira Admins, Jira Project Admins | NA | NA | indefinite | Transport encryption Email content has encryption at rest | Article 6(1)(b) Contract |
1.8 | App | Storing/reusing historic Emails as Test Cases | Your customer Email data | Full Email Data | Jira Admins, Jira Project Admins | NA | NA | indefinite | Transport encryption Email content has encryption at rest | Article 6(1)(b) Contract |
1.9 | App | Exporting Auditing Email / Report | Issue data, Your customers Email data | Jira Issue Content, Email Addresses | Jira Admins, Jira Project Admins | NA | NA | NA | Transport encryption Report content has encryption at rest | Article 6(1)(b) Contract |
2.0 | Support | Retrieving data supplied by you to help with your request | Your customers | Full Email Data, JEMHC Configuration | The Plugin People, Participants | hostingRegion (eg USA) to the UK (where we are based) | NA | Support Issue Close Out for ‘flagged’ emails | Transport Encryption, Encryption at rest, 2FA to access. Email content stays within JEMHC system/db after being flagged, separate 2FA system access required to be able to download. | Article 6(1)(b) Contract |
2.1 | Support | Using data supplied by you to help with your request | Your customers | Full Email Data, JEMHC Configuration | The Plugin People | The UK (where we are based) to our dev site (USA). | NA | Support Issue Close Out for ‘flagged’ emails | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(b) Contract |
2.2 | Support | Sending email derived from your email content to a dead end mailbox (Mailtrap) to help with your request | Your customers | Full Email Data | The Plugin People | NA | NA | Support Issue Close Out for ‘flagged’ emails | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(b) Contract |
2.3 | Support | Excerpts of data supplied may be re-added to the support case for context | Your customers | Full Email Data, Logs, Screenshots | The Plugin People, Participants | The UK (where we are based) to our Jira site (USA). | NA | 3 years | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(b) Contract |
3.0 | Sales | Providing Quotes & Invoices for DataPack/Plan Upgrades through Email (sales@) | Your Company Details, Your Name/Email | Personal Name, Full Email | The ordering party | We send email from the UK to wherever you are. | NA | 7 years | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(c) |
3.1 | Sales | Providing Quotes & Invoices for DataPack/Plan Upgrades through our Jira | Your Company Details, Your Name/Email | Personal Name, Full Email | The ordering party | The UK (where we are based) to our Jira site (USA). | NA | 3 years (Jira) | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(c) |
3.2 | Sales | Quotes and Invoices tracked and docs archived | Your Company Details, Your Name/Email | Company Address, Personal Name, Full Email | The Plugin People | The UK (where we are based) to our Cloud storage site (USA). | NA | 7 Years | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(c) |
3.3 | Sales | Customer online payments | Your Name/Email | Personal Name, Full Email | The Plugin People | We are notified by email in the UK (where we are based) of your purchase where you are based. | NA | 7 Years | Transport Encryption, Encryption at rest, 2FA to access. | Article 6(1)(c) |