| Checklist Free for Jira |
U → IP address(S)¹,
User Content entered into the App(S)²,
name (A+)³ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³Display name of the User is fetched from Jira in the User’s browser and displayed (as long as Jira permissions allow the User to see the display name); |
| Checklist Pro for Jira |
U → IP address (S)¹, User Content entered into the App(S)², name (A+)³
C → name(S)⁴, email address(S)⁴, phone number(S)⁴, address(S)⁴ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³Display name of the User is fetched from Jira in the User’s browser and displayed (as long as Jira permissions allow the User to see the display name);
⁴Applies to the people introduced by a Customer as contact persons (technical or billing). This data is stored in our CRM system, is not mandatory and depends on its provision by the Customer; |
| Checklist Enterprise for Jira |
U → IP address (S)¹, User Content entered into the App(S)², name (A+)³
O → name(S)⁴, email address(S)⁴, User Content entered into the in-app dialogue⁴
C → name(S)⁵, email address(S)⁵, phone number(S)⁵, address(S)⁵ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³Display name of the User is fetched from Jira in the User’s browser and displayed (as long as Jira permissions allow the User to see the display name);
⁴Applies only to the User who contacts our customer support through the in-app dialogue and leaves additional optional data;
⁵Applies to the people introduced by a Customer as contact persons (technical or billing). This data is stored in our CRM system, is not mandatory and depends on its provision by the Customer; |
| Checklist for MS Teams |
U → IP address(S)¹, User Content entered into the App(S)², name (A+)³, username (A+)⁴, email address (A)⁵
|
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³We use this access to display the last User who has toggled a checklist item;
⁴We have access to the User’s username. This is the username they use to log into their Microsoft Teams account;
⁵We have access to the User's email address but are not using it. The access is needed to enable single sign-on with Microsoft Teams. The benefit for the User is that they don't need to enter another username and password to log into the App; |
| Checklist for Jira (Server) |
C → name(S)¹, email address(S)¹, phone number(S)¹, address(S)¹ |
¹Applies to the people introduced by a Customer as contact persons (technical or billing). This data is stored in our CRM system, is not mandatory and depends on its provision by the Customer; |
| Checklist for Jira (Data Center) |
C → name(S)¹, email address(S)¹, phone number(S)¹, address(S)¹ |
¹Applies to the people introduced by a Customer as contact persons (technical or billing). This data is stored in our CRM system, is not mandatory and depends on its provision by the Customer; |
| Clockwork Free for Jira |
U → IP address (S)¹, User Content entered into the App(S)², name (A)³;
O → User Content entered into the in-app dialogue(S)⁴, name(S)⁴ ⁵ ⁶, email address(S)⁴ ⁵ ⁶ ⁷ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³We have access to the name of all Users of the App;
⁴Applies only to the User who contacts our customer support through the in-app dialogue and leaves additional optional data;
⁵Applies only to the User selected by their Manager to notify to log work;
⁶Applies only to the User who optionally provides this information in our surveys;
⁷We save User’s email address for sending optional onboarding emails; |
| Clockwork Pro for Jira |
U → IP address (S)¹, User Content entered into the App(S)², name (A)³;
O → User Content entered into the in-app dialogue(S)⁴, name(S)⁴ ⁵ ⁶, email address(S)⁴ ⁵ ⁶ ⁷
C → name(S)⁸, email address(S)⁸, phone number(S)⁸, address(S)⁸ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³We have access to the name of all Users of the App;
⁴Applies only to the User who contacts our customer support through the in-app dialogue and leaves additional optional data;
⁵Applies only to the User selected by their Manager to notify to log work;
⁶Applies only to the User who optionally provides this information in our surveys;
⁷We save User’s email address for sending optional onboarding emails;
⁸Applies to the people introduced by a Customer as contact persons (technical or billing). This data is stored in our CRM system, is not mandatory and depends on its provision by the Customer; |
| Clockwork for monday.com |
U → IP address(S)¹, User Content entered into the App(S)², name(A+)³, email address(A)⁴ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³We have access to the name of all Users of the App;
⁴We have access to the email addresses of all Users of the App, but are not using it; |
| Acceptance Criteria for Jira |
U → IP address(S)¹, User Content entered into the App(S)², name(A+)³ |
¹IP of the HTTP requests are stored in our logs;
²User Content entered into the App is stored in our data storage and backups;
³Display name of the User is fetched from Jira in the User’s browser and displayed (as long as Jira permissions allow the User to see the display name); |
| Epics Map for Jira |
U → IP address (S)¹ |
¹IP of the HTTP requests are stored in our logs. |
