Data, privacy & security
This page is for Jira admins and security teams who are evaluating Task Hub. For the formal policies, see the Privacy Policy and Security Policy.
At a glance
Section titled “At a glance”| Question | Answer |
|---|---|
| Hosting | Atlassian Forge. Runs on Atlassian, with no C4F servers |
| Data egress | None. The app makes no outbound network calls |
| Where Jira data lives | In Jira. Task Hub reads it on demand and doesn’t copy it |
| Where Task Hub settings live | Forge storage in your Atlassian site’s environment |
| Data residency | Follows your site’s Forge data residency |
| Can C4F see our data? | No |
| Authentication | Atlassian identity. There are no separate accounts, passwords or API tokens |
| Permission model | Work items are read and changed as the signed-in user, within their Jira permissions. A few read-only configuration lookups (workflow schemes, the rank field, JQL validation) use the app identity |
| Analytics or tracking in the app | None |
What Task Hub stores
Section titled “What Task Hub stores”| Data | Contents |
|---|---|
| Task Hub configuration | Name, scope/JQL, columns, swimlanes, quick filters, card layout and colors, label colors, calendar settings, access level and roles (account IDs and group names) |
| Summary layouts | Chart types and settings for each Task Hub |
| Timeline milestones | Milestone names and dates |
| Calendar events | Event title, type, dates, recurrence, description and the creator’s account ID |
Personal display preferences, such as visible List columns, column widths and the date you were viewing on the calendar, are stored in your browser and never leave your device.
Permissions
Section titled “Permissions”| Scope | Used for |
|---|---|
read:jira-work |
Reading work items, fields, statuses, versions and JQL results |
write:jira-work |
Creating, editing, transitioning, ranking, commenting on and linking work items |
write:issue:jira-software |
Ranking and agile fields |
read:jira-user |
Showing people and resolving Task Hub members |
manage:jira-configuration |
Reading workflows and statuses, and checking admin permissions. Task Hub never changes Jira configuration |
read:servicedesk-request |
Grouping and coloring JSM requests by request type |
storage:app |
Saving Task Hub settings in Forge storage |
Uninstalling
Section titled “Uninstalling”When you uninstall Task Hub, your work items are untouched, because Task Hub never stores them. Atlassian removes the app’s Forge storage according to its data retention policy.
Security questionnaire
Section titled “Security questionnaire”Our privacy and security questionnaire is published on the Marketplace listing. For anything else your security review needs, email security@c4ftech.com.