Data Processing Agreement
Last updated: 18 November 2026
In short: when your organisation uses Greenrun, it decides what goes into it, and we only handle that data to run the app for you. Greenrun has no servers of its own: everything is stored and processed inside Atlassian's cloud. This page sets out the promises a processor must make under data protection law.
1. Who this agreement is between
This Data Processing Agreement ("DPA") is between the customer that uses Greenrun ("you", the controller) and Bebb Ventures, the trading name of Louis Bebb, a sole trader in the United Kingdom ("we", the processor). Contact: support@greenrunapp.com.
It forms part of the agreement under which you use Greenrun through the Atlassian Marketplace (the Bonterms Standard End User Agreement and our Provider-Specific Terms). It applies automatically when that agreement applies; nothing needs to be signed. If this DPA and that agreement disagree about personal data, this DPA wins.
2. What we process, and why
| Item | Details |
|---|---|
| Purpose | Providing Greenrun, its support and its optional features to you, as described in the Greenrun documentation, and nothing else. |
| Kinds of personal data | Atlassian account IDs of people who create, change, run or are assigned tests; any personal data your users choose to put into tests, results, notes, comments, screenshots or files; if you turn on AI test writing, the text of the Jira story it is used on; any personal data you include in a support email. |
| People the data is about | Your Jira users, and anyone your users mention in what they put into Greenrun. |
| Sensitive data | Greenrun is not designed for special category data (such as health data). Please don't put it in. |
| How long | For as long as Greenrun is installed on your Jira site, then as set out in section 9. |
Our privacy policy describes the data in more detail.
3. Your instructions
We process personal data only on your documented instructions. Your use and configuration of Greenrun, this agreement and your support requests are those instructions. If the law requires us to do something else, we will tell you first unless the law forbids it. If we believe an instruction breaks data protection law, we will tell you.
4. Confidentiality
Only Louis Bebb has access to Greenrun's systems, and only to the extent needed to run and support it. Anyone we ever authorise to process your data will be bound by a duty of confidentiality.
5. Security
We use appropriate technical and organisational measures to protect personal data, including:
- Greenrun runs entirely on Atlassian Forge. Data is stored in Atlassian-managed storage, kept separate for each Jira site, and is never sent to servers run by us or anyone else.
- Every action checks the person's own Jira permissions, so people only see and change what Jira allows them to.
- Greenrun asks for the fewest Atlassian permissions it needs.
- Logs are meant to hold technical details only, not names, email addresses or the text of your tests.
- Credentials are kept in a password manager, never in code or in files.
- Atlassian's own security programme and certifications cover the platform Greenrun runs on: see atlassian.com/trust.
6. Sub-processors
You give us general permission to use these sub-processors:
| Sub-processor | What for |
|---|---|
| Atlassian (Forge platform, Forge storage and Forge LLMs) | Hosting and running Greenrun, storing its data, and the optional AI test writing. |
| Cloudflare | Forwarding emails sent to support@greenrunapp.com. |
| Google (Gmail) | Receiving and answering support emails. |
We will tell you at least 30 days before adding or replacing a sub-processor, by updating this page and its date, so you can object. If you object on reasonable data protection grounds and we can't resolve it, you may stop using Greenrun. We remain responsible for our sub-processors and rely on their own data protection terms, which give protections at least as strong as this DPA.
7. International transfers
Where your Jira site's data residency is set, Atlassian keeps Greenrun's stored data in that region. Our sub-processors may process data outside the UK or EEA. Where they do, we rely on the transfer safeguards they provide, such as the UK International Data Transfer Addendum or the EU Standard Contractual Clauses, or another lawful basis for the transfer.
8. Helping you
- People's requests: most requests to see, correct or delete data can be handled by your Jira admin inside Greenrun. If you need our help, email us and we will help within a reasonable time. If a person contacts us directly about your data, we will pass the request to you.
- Closed Atlassian accounts: Greenrun reports the account IDs it holds to Atlassian every week and removes the IDs of people whose accounts have been closed.
- Assessments: we will give you reasonable help with security, data protection impact assessments and consultations with regulators, taking into account the information available to us.
9. Breaches
If we become aware of a personal data breach affecting your data, we will tell you without undue delay, with the information we have about what happened, what it affects and what we are doing about it, and keep you updated.
10. When you stop using Greenrun
When Greenrun is uninstalled, its stored data is deleted by Atlassian under its data retention rules for Forge apps (currently 28 days after uninstalling; see Atlassian's page). Before uninstalling, you can export your tests to Excel or CSV from Greenrun. We delete support emails about your data on request, unless the law requires us to keep them.
11. Information and audits
We will make available the information you reasonably need to show that we meet this DPA, and answer reasonable written questions. You may audit our compliance, or have an independent auditor bound by confidentiality do so, once a year on 30 days' written notice, at your own cost. Because Greenrun holds no data outside Atlassian's platform, audits of the hosting infrastructure are covered by Atlassian's own audit reports.
12. United States privacy laws
Where US state privacy laws apply (such as California's CCPA), we act as your service provider. We do not sell or share personal information, and we do not use it for any purpose other than providing Greenrun to you.
13. Law and changes
This DPA is governed by the same law as the agreement it forms part of. We may update it to reflect changes in the law or in how Greenrun works; we will update the date at the top and will not reduce your protections during a paid subscription period without telling you.