Privacy policy
Last updated: 17 November 2026
In short: Greenrun is built on Atlassian Forge. Everything you put into Greenrun is stored by Atlassian, inside Atlassian's cloud, separately for each Jira site. Greenrun has no servers of its own, sells nothing, shares nothing and uses no tracking or analytics.
Who we are
Greenrun is made by Louis Bebb, a sole trader based in the United Kingdom ("we", "us"). Contact: support@greenrunapp.com.
For the test data your team puts into Greenrun, your organisation is the data controller and we act as a processor on its behalf. Atlassian stores and runs the app for us as our sub-processor.
What Greenrun stores
| Data | Why |
|---|---|
| Test cases, folders, shared steps, test plans, cycles, test results, notes and comments | This is what the app is for. |
| Screenshots and files you attach to test steps | So results include their evidence. |
| Jira issue IDs and keys (for example DEMO-5) that tests cover, or that were raised as bugs | To show tests and bugs together. |
| Atlassian account IDs of the people who created, changed or ran tests | To show who did what. Names are looked up from Jira when shown, not stored by Greenrun. Once a week Greenrun tells Atlassian which account IDs it holds, as Atlassian's privacy rules for apps require. If Atlassian says a person has closed their account, Greenrun removes their ID from its records (their name then shows as "Former user"), deletes any upload address given to them and switches off any API key they made. |
| If AI test writing is used: the story's summary and description, and the AI's suggested tests | To write the suggestions. Deleted 2 days after the request; only a monthly count of uses is kept. |
Greenrun does not store names, email addresses, passwords or payment details. Billing is handled entirely by Atlassian.
What Greenrun reads from Jira
Greenrun asks Jira, as the signed-in person, for the projects they can see, their project permissions, and the summary and status of issues linked to tests. When someone clicks Raise bug, Greenrun creates that Jira issue as them. When someone uses Draft tests with AI (off until a project admin turns it on), Greenrun reads that story's summary and description as them. Jira's own permissions apply to all of this. Greenrun keeps only the issue IDs and keys listed above.
Where it is kept
All Greenrun data is stored by Atlassian using Forge storage (Forge SQL and the Forge Object Store), in Atlassian's cloud and separately for each Jira site. It is not sent to any server run by us or by anyone else. AI test writing uses Atlassian's own hosted AI service for Forge apps (Forge LLMs), so the story text is processed inside Atlassian's platform too. Atlassian keeps this data in the same location as your Jira site. If your site's admin has chosen a data residency region, Greenrun's data follows that choice; if not, it is hosted within Atlassian's global cloud, where Atlassian may move it between regions. See Atlassian's Forge data residency page.
Read more about Atlassian's security and privacy at atlassian.com/trust.
Can we see your data?
Not in day-to-day running: Greenrun has no admin console or back door into customer data. If something goes wrong, Atlassian lets us see the technical logs Greenrun writes on your site, and you can download those same logs from your own site to see what we can see. They are meant to hold only technical details, such as which job failed, counts and project keys. We don't deliberately write names, email addresses or the text of your tests to them, though an error message from the database could, rarely, include a fragment of a value. If you send us screenshots or details in a support email, we use them only to help you.
Cookies and tracking
Greenrun uses no cookies, analytics or tracking. Inside Jira it keeps two things in your own browser's local storage: the last project you picked, and a copy of any test or shared steps you were editing but hadn't saved, so a reload doesn't lose your work. These stay on your computer and are never sent to us; a copy is removed once you save or discard it, and after 30 days at most. This website has no cookies or analytics either. The website is hosted by Cloudflare, which handles visitors' requests, including their IP addresses, to deliver and protect the site; we don't see or keep those.
Support emails
Emails to support@greenrunapp.com are forwarded by Cloudflare (our email forwarding service) to a Gmail account (Google) that we use only for support. We keep them as long as needed to help you, and delete them on request.
How long data is kept
Your Greenrun data stays while Greenrun is installed on your Jira site. If a licence lapses, nothing is deleted; the app becomes read-only. When Greenrun is uninstalled, Atlassian first holds its stored data for a limited period, so it can be restored if you reinstall within a short window, and then deletes it under its own data retention rules for Forge apps. Atlassian's documentation currently gives 28 days for this; see Atlassian's hosted storage data lifecycle page for the current rules.
Your rights
Because your organisation controls your test data, requests to see, correct or delete it are best made to your Jira site admin, who can edit or remove it in Greenrun or uninstall the app. You can also contact us and we'll help. If you're in the UK or EU you can complain to your data protection authority; in the UK that's the Information Commissioner's Office (ico.org.uk).
Changes
If we change how Greenrun handles data, we'll update this page and the date at the top before the change takes effect.