| Issue Checklist for Jira Free |
U → IP address(S)¹, Name (A+)² |
¹ IP of the HTTP requests are stored in our logs.
² Display name of the mentioned person is fetched from Jira in the user browser and displayed (as long as Jira permissions allow the user to see the display name) |
| Issue Checklist for Jira Pro |
U → IP address (S)¹, Name (A+)³
C → Name(S)², Email Address(S)², Phone Number(S)², Address(S)² |
¹ IP of the HTTP requests are stored in our logs.
² For the people introduced by a customer as contact persons (technical or billing), this data is stored in our CRM system.
³ Display name of the mentioned person is fetched from Jira in the user browser and displayed (as long as Jira permissions allow the user to see the display name) |
| Acceptance Criteria |
U → IP address(S)², Cookie Identifier(P)¹, Gender(P)¹, Name (A+)³ |
¹ We use Google Analytics for collecting usage data.
² IP of the HTTP requests are stored in our logs.
³ Display name of the mentioned person is fetched from Jira in the user browser and displayed (as long as Jira permissions allow the user to see the display name) |
| Checklist for Jira Cloud |
U → IP address (S)¹, cookie identifier (P)³
C → Name(S)², Email Address(S)², Phone Number(S)², Address(S)² |
¹ IP of the HTTP requests are stored in our logs.
² For the people introduced by a customer as contact persons (technical or billing) this data is stored in our CRM system.
³ Cookie is used for authentication. |
| Checklist for Jira Server |
C → Name(S)¹, Email Address(S)¹, Phone Number(S)¹, Address(S)¹ |
The application runs on the customer's machine.
We only process data related to licenses or when someone from a company contacts us for support.
¹ For the people introduced by a customer as contact persons (technical or billing) this data is stored in our CRM system. |
| Checklist for Jira Data Center |
C → Name(S)¹, Email Address(S)¹, Phone Number(S)¹, Address(S)¹ |
The application runs on the customer's machine.
We only process data related to licenses or when someone from a company contacts us for support.
¹ For the people introduced by a customer as contact persons (technical or billing) this data is stored in our CRM system. |
| Clockwork Timesheets for Jira Free |
U → IP address(S)¹, Name(A)², Email Address(S)³
O → Name(S)⁴, Email Address(S)⁴
O → Name(S)⁵, Email Address(S)⁵
|
¹ IP of the HTTP requests are stored in our logs.
² We have access to the name of all users of the app.
³ We save users' email addresses for sending them onboarding emails.
⁴ for users selected by Manager to notify to log work.
⁵ for users who optionally provide this information in our surveys.
|
| Clockwork Timesheets for Jira Pro |
U → IP address(S)¹, Name(A)³, Email Address(S)⁴
C → Name(S)², Email Address(S)², Phone Number(S)², Address(S)²
O → Name(S)⁵, Email Address(S)⁵
O → Name(S)⁶, Email Address(S)⁶
|
¹ IP of the HTTP requests are stored in our logs.
² For the people introduced by a customer as contact persons (technical or billing), this data is stored in our CRM system.
³ We have access to the name of all users of the app.
⁴ We save users' email addresses for sending them onboarding emails.
⁵ for users selected by Manager to notify to log work.
⁶ for users who optionally provide this information in our surveys.
|
| Clockwork Time Tracking & Timesheets for monday.com |
U → IP address(S)¹, Name(A+)², Email Address(A)³ |
¹ IP of the HTTP requests are stored in our logs.
² We have access to the name of all users of the app. We are not using the access to email address.
³ We have access to the email address of all users of the app. We are not using the access to email address. |
| Epics Map for Jira |
U → IP address (S)¹ |
The applications store no data. It runs entirely on the user's browsers.
¹ IP of the HTTP requests are stored in our logs. |
| To-do Checklist for Team |
U → Name (A+)¹, email address (A)², Username (P)³, Social Media Profile (P)³, IP address (S)⁴ |
¹ We use this access to display the last user who has toggled a checklist item.
² We have access to users' emails but are not using this access. 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 our app.
³ We have access to the username of the users. This is the username they use to log into their Microsoft Teams account.
⁴ IP of the HTTP requests are stored in our logs. |
