Annex — Self-Managed GitLab Connector for Jira

Forms part of the RDIT Products Privacy Statement and Data Processing Addendum.

What this app processes, and why

Commit author name and email (Jira displays commit authorship), commit messages/hashes/URLs (linking commits to issues), branch names and authors, merge request titles/authors/states/URLs, and repository/project names and URLs. No special categories of data under GDPR Article 9 are requested or required by the app's design — commit messages are free text the app cannot filter, and the customer's own developers are responsible for what they write there.

Permissions requested

Read, write and delete on Jira development information only, plus the app's own private storage. Notably absent: read:jira-work, which would grant read access to every issue on the site. It was deliberately not requested — an earlier design would have used it to detect new issues instantly; instead a five-minute polling cycle is used, and the delay is the price paid for not asking for that access.

Storage and retention

All within Atlassian's infrastructure: configuration (shared secret, project keys) until changed or uninstalled; a deduplication cache for about 48 hours; a retry queue for commits referencing not-yet-existing issues, held until linked or for 14 days, whichever comes first.

On uninstall

App storage is deleted through the Forge platform. Note that anything still waiting in the retry queue at that point is lost along with it. Development data already written to Jira remains there, under the customer's control.

Security specific to this app

The web trigger is authenticated by a customer-generated shared secret and rejects unauthenticated requests. The app is inbound-only — it never initiates a connection into the customer's network. Credentials are never logged.