Linkwright

Privacy Policy — Linkwright for Jira

Effective date: 6 November 2026

Saad Lagzouli, sole proprietor (entrepreneur individuel) trading as Linkwright (SIREN 130 855 364, France) (“we”) publishes Linkwright for Jira (the “App”), an Atlassian Forge app that shows GitHub activity — commits, branches, pull requests, reviews and deployments — on Jira issues.

1. Where the App runs and where data is stored

The App is built on Atlassian Forge. Its code runs on Atlassian’s infrastructure and all data it stores is kept in Forge storage (Forge SQL and Forge key-value storage) belonging to your Jira site, isolated from every other customer. We operate no server of our own and do not copy your data to any system we control.

2. Data the App processes

2.1 From GitHub, for repositories you attach to a Jira project

This activity is only read from repositories that (a) the GitHub App has been granted access to by the GitHub account owner, (b) belong to a GitHub installation associated with your Jira site, and © are attached to a Jira project by an administrator.

2.1 bis From the other repositories of an associated installation

For every repository the GitHub App can access in an installation associated with your Jira site, attached or not, the App stores its name. Once a day it also reads its 50 most recent commits, to suggest attaching it to the Jira projects they cite. It keeps only how many commits cite each project key and when they were read, not the commits.

2.2 When a Jira administrator associates a GitHub installation

The administrator authorizes the App on GitHub once. Through that authorization the App reads the administrator’s GitHub user, the installations of the App they can access, and their role in the corresponding organizations, to verify they control the installation. The App stores the installation identifier, the account name and type, and the administrator’s GitHub login. The OAuth token is stored and refreshed by Atlassian Forge, not by our code. The App does not store Atlassian account identifiers.

The same applies when an administrator invites a GitHub owner to make that association instead: the owner’s GitHub login is what is stored, once they connect. The invitation itself holds the GitHub organization or account name the administrator typed, its creation and expiry dates, and a hash of its link, not the link itself. That name can be a person’s GitHub login, for a personal account. An invitation stays in your site’s Forge storage under the rules of section 6 after it expires or is used.

2.3 Operational data

Synchronization state per repository (timestamps, error kinds), identifiers of the commits already sent to Jira’s Development panel (so none is sent twice), the latest commit identifiers read on the default branch, GitHub API quota counters and cache tags, webhook delivery identifiers (kept 24 hours to discard duplicates), and a per-site webhook secret and GitHub installation token held in Forge encrypted storage. For each project where an administrator chooses one, the App also stores the format of the branch name it proposes, as that administrator typed it (for example feature/{key}-{description}), and the date it was saved.

3. How the data is used

Solely to provide the App’s features on your Jira site: linking GitHub activity to issues, displaying it in the App’s issue panel and in Jira’s native Development panel, and reporting how up to date it is. We do not sell data, use it for advertising, profile individuals, or train models on it. The App displays no advertising.

4. Where data is sent

5. Logs

Forge function logs, visible to us for support and debugging, contain repository names, GitHub account names, issue keys, branch names and environment names (with any email address removed), counters, identifiers and error messages. The App does not write commit messages, author names, reviewer logins, tokens or secrets to them. When Jira refuses data, up to 500 characters of its answer are logged with any email address removed; that answer could quote what it refuses. Repository and account names can contain a personal GitHub login (see §2.1). Logs are retained according to Atlassian Forge’s log retention.

6. Retention and deletion

7. Security

Webhook deliveries are verified with an HMAC signature using a per-site secret and rejected otherwise; secrets are held in Forge encrypted storage; database queries are parameterized. Vulnerabilities are handled under the Atlassian Marketplace security bug fix policy.

8. Your rights

Where data protection law such as the GDPR applies, the customer operating the Jira site is the controller of the data processed by the App and we act as a processor. Individuals may exercise their rights through that customer or by contacting support@linkwright.io.

8 bis. Visits to our Marketplace listing

This section is not about the App. Since 2 November 2026, our listing page on the Atlassian Marketplace sends visit statistics to our Google Analytics 4 property, through the Analytics setting that Atlassian offers to app vendors. We use them only to count visits to the listing and see where they come from; we have turned off every option that shares this data with Google for its own purposes. Cookie consent on the Marketplace is handled by Atlassian. The App itself contains no analytics and sends nothing to Google.

9. Changes

We will update this policy when the App’s data processing changes and change the effective date above.

10. Contact

Saad Lagzouli, sole proprietor (entrepreneur individuel) trading as Linkwright (SIREN 130 855 364, France) — support@linkwright.io