Privacy Policy: On-Prem Git & SVN for Jira Cloud
Last updated: 27 October 2026.
This policy explains what data the Atlassian Marketplace app On-Prem Git & SVN for Jira Cloud (the “App”) processes, why, where it is kept and for how long. The App is provided by Sasso di Matera Giuseppe S.a.s. (Via Clefi 2, 20146 Milano (MI), Italy, VAT IT13043470965), “we” in this policy. Contact: sassimaterasas@gmail.com.
1. How the App works
Your GitLab self-managed instance and your Subversion (SVN) servers send events to the App when code is pushed or committed. The App turns them into development information (commits, branches, merge requests) and sends it to the Development panel of your Jira Cloud site. The App runs entirely on Atlassian’s Forge platform (“Runs on Atlassian”): it has no servers of its own, makes no calls outside Atlassian, and we have no access to the data it stores.
2. Data processed by the App
| Data | Source | Purpose |
|---|---|---|
| Commit and revision messages, branch names, merge request titles and states | GitLab, SVN | Shown in Jira issues |
| Names of commit authors; for GitLab also their e-mail addresses (Jira uses them to show the author) | GitLab | Shown in Jira issues |
| SVN user names of revision authors | SVN | Shown in Jira issues |
| GitLab user name of whoever pushed or acted on a merge request | GitLab | Activity history on the App page |
| Repository names, paths and web addresses; number of changed files | GitLab, SVN | Links in Jira; detection of missing events |
| A secret token generated by the App | the App | Authenticating your servers |
The App never receives or stores source code, diffs, file contents or file names.
3. Where the data is stored
Only in Atlassian’s cloud: Forge hosted storage and your Jira site, with the same data residency as your Jira site. The App does not transfer data to us or to any third party. Atlassian is the only sub-processor (see the Atlassian Privacy Policy).
Data residency. All the data listed in section 2 is in-scope End-User Data and is kept only in Forge hosted storage, which follows the data residency location of your Jira site (for example EU, Germany, US, Australia, Canada, India, Japan, Singapore, South Korea, Switzerland or the United Kingdom) and moves with it when an administrator changes the location. There is no out-of-scope End-User Data.
4. Retention
- Events are kept only until they are applied to Jira.
- Duplicate-delivery markers: from 1 hour to 7 days.
- Activity history: 14 days.
- Problem records (“Needs attention”): until an administrator dismisses or retries them.
- Last applied state of each branch and merge request: 90 days.
- Markers of expected pushes and revisions: 2 days; number of the last revision received from each SVN repository: 365 days.
- When the App is uninstalled, Jira deletes the development information sent by the App, and Forge deletes the App’s storage after 28 days.
5. Logs
The App’s technical logs are designed to contain only technical information (error types and statuses), not commit messages, names or e-mail addresses. Atlassian lets us see them only if an administrator of your site allows it.
6. Roles and your rights
For the data listed in section 2, your organization is the controller and we act as a processor on its behalf, under our Data Processing Addendum. Requests from people whose data appears in commits (for example, to correct or delete a name) should be addressed to your organization, which can change or remove the data at its source and in Jira; we will assist on request.
When you contact our support, we use your name, e-mail address and the content of your message only to answer you, and we keep them for up to 24 months after the last exchange. You can ask us to access, correct or delete them, or object to their use, by writing to sassimaterasas@gmail.com. You can also lodge a complaint with your data protection authority (in Italy, the Garante per la protezione dei dati personali).
7. Security
Access to the App’s settings is limited to Jira administrators and checked on every request. Your servers authenticate with the secret token, compared in constant time; the token can be regenerated at any time. Data is protected by the security of the Atlassian Forge platform.
8. Changes
We will publish any change to this policy on this page, with the date of the last update.