...
Personal data stored / processed by TFS4JIRA components
| Component | Data processed/stored | Remarks |
|---|---|---|
| Jira plugin | Change set metadata : author, comment etc. | Just processed, nothing is stored. No source code is processed. |
| Synchronizer | TFS/VSTS username | For synchronisation profiles and checkins scanning connection configurations. |
| Jira username | For synchronisation profiles. | |
| Mapping configurations provided by TFS4JIRA user. | Any mappings configuration, that can contain private data (e.g. users mappings) | |
| Data synchronised by TFS4JIRA | Any private data that is configured, by TFS4JIRA user, to be synchronised between TFS/VSTS and Jira. | |
| Change set metadata : author, comment etc. |
TFS4JIRA CloudÂ
| Gliffy | ||||
|---|---|---|---|---|
|
| Additional info for TFS4JIRA cloud users: | ||
|---|---|---|
| TFS4JIRA cloud backend | Change set metadata : author, comment etc. | No data is stored, it is just passed (proxied) from the Synchronizer to Jira Cloud user browser. |
| Logs | Our logs are kept for a maximum 14 days. | |
| Info | ||
|---|---|---|
| ||
Our product analytics does not contain ANY private personal data. |