Privacy Policy
What GitHub Actions for Jira stores, where it lives, how long it is kept, and who else sees it. The short version: the App runs entirely on Atlassian Forge, we operate no server of our own, and the only external service it talks to is GitHub.
Last updated 25 July 2026
Who we are
GitHub Actions for Jira (the App) is provided by We The Folks. You can reach us at dominik.szymanski@wethefolks.eu.
What this policy covers
This policy covers two things: the App, installed into an Atlassian Jira site from the Atlassian Marketplace, and this website.
It does not cover Jira itself, the Atlassian Marketplace, or GitHub. Those are run by Atlassian and GitHub under their own privacy policies.
Our role: processor, not controller
For the data the App handles inside your Jira site, you are the controller and we are a processor acting on your instructions. Your instructions are the configuration your administrators enter and the deployments your users launch. Terms for that relationship are in our Data Processing Addendum.
We are a controller for a small amount of data of our own: the contact details of people who email us for support or a legal request, and the server logs of this website.
What the App stores
The App writes two kinds of record into Forge storage. Nothing else is persisted.
Project configuration
| Stored | Detail |
|---|---|
| Jira project | The project ID the configuration belongs to. |
| GitHub connection | The GitHub App installation ID, the login of the GitHub account or organization it belongs to, and the repositories that installation exposes (name, ID, and whether the repository is private). |
| Actions groups | Group names, the Jira labels that preselect them, the execution mode, and the failure policy. |
| Actions | Repository, workflow file, ref, timeout, and the input definitions with their default templates and choice options. |
| Who changed it | The Atlassian account ID of the administrator who last saved the connection. |
Deployment records
| Stored | Detail |
|---|---|
| The issue | Jira project ID, issue ID, issue key, and issue summary, so the panel can show what was deployed. |
| Who launched it | The Atlassian account ID and display name of the user who pressed Launch. This is the audit trail: it answers who deployed this ticket. |
| Input values | The values submitted for the workflow inputs, including anything a default template filled in from the issue, such as {{issue.key}}. |
| Run state | Per-action GitHub workflow run IDs and URLs, statuses, conclusions, error messages returned by GitHub, and timestamps. |
The App also keeps two small pointers: from a Jira issue to its most recent deployment, and from a GitHub workflow run to the deployment that owns it.
Personal data in these records is limited to Atlassian account IDs, the display name of the person who launched a deployment, the login of the connected GitHub account, and whatever your own users type into an issue summary or a workflow input.
Credentials and tokens
The App stores no GitHub token. There is no personal access token anywhere in it, and no shared secret in an environment variable that deployments run through.
- The administrator's GitHub OAuth token is held by Atlassian's Forge External Authentication service, not by us. The App asks Forge to make an authorized request; it never reads the token. That connection is used for one thing only: discovering which GitHub App installations that administrator may choose from.
- Installation tokens are minted for each operation from a JWT signed with the GitHub App's private key, used, and discarded. They are never written to storage.
- The GitHub App private key is ours, not yours. It is held as an encrypted Forge environment variable and is never exposed to the App's interface.
Where the data is stored
Everything the App stores lives in Forge storage, hosted by Atlassian and tied to your Atlassian site. There is no vendor-operated server, no database of ours, and no copy of your data on our infrastructure.
That is a deliberate consequence of building the App entirely on Forge: for data residency and security, the posture is Atlassian's rather than ours. Where your Atlassian site's data is hosted is determined by your Atlassian settings.
How long it is kept
- Deployment records are deleted automatically thirty days after a deployment reaches a final state. A scheduled job in the App does this; it is not a manual process.
- Project configuration is kept until you change it, disconnect the project, or uninstall the App.
- Uninstalling the App removes its storage from your Atlassian site, under Atlassian's own deletion process for Forge apps.
- Support correspondence is kept for as long as needed to handle the request and to meet our legal obligations, and no longer than three years after the last message.
What is sent to GitHub
When a user launches a deployment, the App sends GitHub the repository and workflow it is dispatching, the ref, and the input values submitted. When rendering a form or tracking a run, it reads branches, environments, workflow definitions, and run status back.
The App communicates with github.com and api.github.com and with no other external host. There is no dynamic egress to environment URLs, no telemetry endpoint, and no third-party service in the path.
Workflow inputs are not secret. They are visible operational data by design, recorded against the GitHub workflow run and visible to anyone who can read that run. Never pass passwords, tokens, or credentials through them.
Sub-processors
| Party | Role |
|---|---|
| Atlassian | Hosts the App, its storage, and its logs, and provides the external authentication that holds the GitHub OAuth connection. |
| GitHub | Receives what the App sends at your direction, and returns run state. Your own relationship with GitHub is separate from ours. |
We use no analytics provider, no error-tracking provider, no advertising network, and no customer data platform. If we ever add a sub-processor, we will update this list and give notice as described in the Data Processing Addendum.
Logs and our access to your data
The App writes application logs, which Atlassian retains and makes available to us for a limited period. Those logs record identifiers and error messages: a project or installation ID, a deployment ID, the status GitHub returned. They are not written to carry issue summaries or workflow input values.
We have no routine access to your Jira data, your repositories, or the contents of your Forge storage. If we need information to diagnose a problem, we ask you for it.
What we do not do
- We do not sell or share personal data.
- We do not use your data to train machine learning models.
- We do not profile your users or advertise to them.
- The App sends no telemetry and no usage analytics.
- The App and this website set no advertising or tracking cookies.
This website
This website is a static page. It sets no cookies, runs no analytics, and makes no third-party requests: the fonts are served from this domain rather than from a font CDN, and the only script on the page animates the demonstration panel.
Our hosting provider records standard server logs, including IP addresses, for security and abuse prevention. The legal basis is our legitimate interest in keeping the site available and secure.
Security
- No long-lived credentials. Short-lived installation tokens, minted per operation and never stored.
- Least privilege on GitHub. The GitHub App requests Actions (read and write), Contents (read), Environments (read), and Metadata (read), on the repositories you select and no others.
- Permission checks on the server. Launching requires the Jira
EDIT_ISSUESpermission and changing configuration requires project administrator rights. Both are re-validated on the server on every save and every launch. The browser is never trusted. - Project isolation. A deployment belongs to the project that launched it, and requests for it from another project are refused.
- Platform security. Encryption in transit and at rest, tenancy isolation, and infrastructure controls are Atlassian's, as part of the Forge platform.
Your rights and requests
Under the GDPR and similar laws, individuals have rights of access, rectification, erasure, restriction, portability, and objection.
For data inside your Jira site, the controller is your organization, so the first place to send a request is your own administrator. They can remove configuration and deployment records directly through the App, and uninstalling it removes them all. We will support an administrator handling such a request, as set out in the Data Processing Addendum.
For data where we are the controller, such as support correspondence, write to dominik.szymanski@wethefolks.eu. You also have the right to complain to your local data protection authority.
International transfers
We do not export your data out of the Atlassian platform. Any transfer of personal data outside the European Economic Area that arises from hosting is carried out by Atlassian under its own transfer mechanisms, and any transfer to GitHub arises from your own use of GitHub. Where we act as a processor, the transfer terms in the Data Processing Addendum apply.
Changes to this policy
We may update this policy. The version published at this address is the version in force, and the date at the top of this page shows when it last changed. Where a change materially affects how personal data is handled, we will give notice through the Marketplace listing or the App before it takes effect.
Contact
Questions about this policy, or a privacy request: dominik.szymanski@wethefolks.eu.