Effective: 18 September 2026
Git Links ("the app") is published by Two Little Moons Consulting (ABN 49 732 400 198), based in Penrith, NSW, Australia ("we", "us"), on the Atlassian Marketplace. This policy explains exactly what the app does with data.
It is deliberately specific about one thing: unlike most of our apps, this one does send data outside Atlassian, because connecting Jira to a Git host is what it is for. What leaves, where it goes and who decides are set out below.
The app is built on Atlassian Forge and its own code runs on Atlassian's infrastructure inside your site's installation. We operate no server. There is no backend of ours for your data to reach, no analytics, no error-reporting service and no sub-processor of ours anywhere in the path.
We cannot read your Jira data. Nothing in the app sends it to us, and we have no access to your installation's storage.
The app calls the API of the Git host a Jira administrator has connected. Nothing is reachable until an administrator connects it, and nothing is sent to anyone else.
Declared hosts, named in the app's manifest: api.github.com, gitlab.com, api.bitbucket.org and dev.azure.com.
A self-managed GitHub Enterprise Server, a self-managed GitLab, an Azure DevOps Server, or an optional sync-failure alert webhook live on hostnames that cannot be known in advance. Rather than request a wildcard, the app asks for each one at the moment an administrator connects it. Atlassian shows that administrator a consent modal naming the exact domain; nothing is reachable unless they approve it, the grant is scoped to their installation, it is written to the Atlassian Guard audit log, and they can review or revoke it in Atlassian Administration → Connected Apps → Data management.
What is actually transmitted:
Nothing else. The app does not send issue descriptions, comments, attachments, custom field values or any person's details to a Git host.
Read on your behalf and with your own Jira permissions, except where noted:
A work item you cannot open in Jira can never appear in the app's panel.
git-links), a small summary — counts of commits, branches and pull requests — so that git activity is searchable in ordinary JQL.write:jira-work because Forge cannot request a scope conditionally, but every Jira write is gated server-side on a per-project toggle that defaults to off and can only be turned on by a Jira or project administrator. With it off the app writes nothing to a work item beyond its own property.All of it inside your Atlassian installation, never ours:
None. We run no analytics and receive no telemetry. We do not know who installs the app, who uses it or what they do with it. What we see is what Atlassian shows any Marketplace partner: aggregate install and licence counts for billing, and whatever you choose to tell us if you contact support.
Cached indexes and connection records live in your installation and are removed when you delete the connection or uninstall the app. Deleting a connection deletes its token and its webhook secret at the same time. Uninstalling removes the app's storage.
Tokens can be revoked by you at any time, either in the app or at the Git host. Revoking at the host takes effect immediately regardless of anything stored here.
The app stores End-User Data only within Atlassian apps and services, so it inherits your site's own data residency. The app itself offers no separate residency option.
Data sent to a Git host is governed by that host's terms and residency, not ours. If you connect a self-managed server, its location is yours to determine.
Credentials are held in Forge secret storage. Every read is performed with the permissions of the person asking, so the app cannot show anyone something Jira would not. Writes to Jira are off by default and require an administrator to enable them. Egress to anything beyond the four declared SaaS hosts requires an administrator's explicit, audit-logged, revocable consent.
Report a security issue to support@twolittlemoons.com. Our security statement is at https://ethanj2k.github.io/security.html.
Questions, or a request about data: support@twolittlemoons.com.
Two Little Moons Consulting, ABN 49 732 400 198, Penrith, NSW 2750, Australia.
Material changes will be published on this page with a new effective date, and noted in the app's release notes before they take effect.