Privacy policy for our apps
Last updated 6 October 2026
This policy covers the Relay Studio apps for Jira and Confluence sold on the Atlassian Marketplace. It explains what the apps keep, what we receive from Atlassian when you install or buy an app, and your rights. The data protection notice for this website is in the Impressum.
Who we are
Relay Studio is run by Mathias Gort, MSc, sole proprietor, Badidastraße 81, 6811 Göfis, Austria. Contact for anything in this policy: support@relaystudio.org.
The short version
- The apps run entirely on Atlassian’s Forge platform and cannot send data to any server outside Atlassian.
- We cannot see your pages, issues, files or comments.
- Most apps keep nothing at all; the ones that keep data store it in Forge hosted storage inside Atlassian.
- The apps contain no tracking, analytics or advertising.
What each app keeps
| App | Stored | Personal data |
|---|---|---|
| OpenAPI Viewer for Confluence | Pasted spec text, with the id of the page it was pasted on and the save time, and a per-page count of saves in the current hour. Attached specs are not copied. | None. No names, e-mail addresses or account ids are stored. |
| Release Notes Builder for Jira | Per project: section names, issue type mapping, labels to leave out and the chosen release note field. | None. |
| Read Confirmations for Confluence | Per confirmation: Atlassian account id, page id, page version and time. Per page: the version from which confirmations are requested again. | Atlassian account ids. No names or e-mail addresses are stored; names are read live from Confluence when an editor opens the report. |
| Comments Overview for Confluence | Nothing. | None stored. Author names are shown on screen and in the CSV you download. |
| Attachment Housekeeping for Confluence | Nothing. | None stored. File names and page titles are shown on screen and in the CSV you download. |
| Task Overview for Confluence | Nothing. The macro settings are saved in the page, like those of any macro. | None stored. Assignee names are shown on screen and in the CSV you download. |
| Last Comment for Jira | Which comments count, the id of the field, and the progress of the current fill. The newest comment itself is in the Jira field, inside Jira. | None in the app’s storage. The field holds the comment author’s account id, as Jira’s own comments do; Jira shows the name. |
| Portal Details for Jira Service Management | Which items each portal shows, with their labels. Nothing about requests or customers. | None stored. Names such as the assignee are read when a customer opens a request and shown, not kept. |
| Space Templates & Copy for Confluence | Nothing. | None stored. |
Data in Forge hosted storage stays in the same data residency location as your Atlassian site and moves with it. When you uninstall an app, Atlassian deletes its storage under Atlassian’s data retention policy; we keep no copy. Apps that read Jira or Confluence do so as the person using them, so the products’ own permissions always apply.
What we receive from Atlassian
When you install or buy one of our apps, Atlassian shares licence information with us through the Marketplace: the organisation and site the licence belongs to, the licence type, tier and dates, and the names and e-mail addresses of the technical and billing contacts. We use it to provide the licence, answer support requests and send messages about the app that you need, such as security notices. We do not use it for unrelated marketing and do not sell or share it.
Legal bases: performance of the contract (Art. 6(1)(b) GDPR) for licensing and support, our legitimate interest in operating and securing the apps (Art. 6(1)(f) GDPR), and legal obligations for accounting records (Art. 6(1)(c) GDPR).
Support requests
When you write to us, we keep your e-mail and our reply to answer the request and to recognise follow-ups. Support correspondence is deleted two years after the last contact, unless it is part of the accounting records, which Austrian law requires us to keep for seven years.
Service providers
- Atlassian: hosting and running the apps on Forge, Marketplace licensing and billing.
- Our e-mail provider: delivering and storing support e-mail.
Where data leaves the EU or EEA, the transfer is covered by the European Commission’s standard contractual clauses; for Forge, they are part of Atlassian’s Forge Data Processing Addendum.
Your rights
You can ask what we hold about you and have it corrected, deleted, restricted or handed over, and you can object to processing based on legitimate interest. Write to support@relaystudio.org. You also have the right to complain to a supervisory authority; in Austria that is the Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb.gv.at.
Data that an app keeps inside your Atlassian site belongs to your organisation, which decides about it. Requests from people in your organisation about that data go to your site administrator first; we help them as described below.
Data processing addendum
This addendum applies to apps that store personal data in Forge hosted storage (currently: Read Confirmations for Confluence). It forms part of the agreement under which your organisation uses the app. Your organisation is the controller; Relay Studio is the processor (Art. 28 GDPR).
- Subject, nature and purpose.Storing the data each app needs to work, as described in the table above and in the app’s documentation, for as long as the app is installed.
- Types of data and data subjects. Atlassian account ids and the related records listed for the app (for example page id, page version and time of a read confirmation), of the users of your Atlassian site.
- Instructions. We process the data only to provide the app as documented, and otherwise only on your documented instructions, unless the law requires otherwise.
- Confidentiality. Only Relay Studio works on the apps, under a duty of confidentiality. We have no access to the stored data in normal operation.
- Security. The data is kept in Forge hosted storage, encrypted and separated per site by Atlassian, and is never transferred outside Atlassian. See the security policy.
- Sub-processor.You authorise Atlassian Pty Ltd and its affiliates as sub-processor for running the apps on Forge, under Atlassian’s Forge Data Processing Addendum. We will tell you before adding or replacing a sub-processor, so that you can object.
- Data subject rights.The apps follow Atlassian’s personal data reporting: data of closed Atlassian accounts is erased automatically. We help you answer other requests as far as the app allows.
- Breaches. We inform you without undue delay after becoming aware of a personal data breach affecting your data, with the information you need for your own notifications.
- Assistance. We support you with security, impact assessments and consultations with authorities as far as they concern the app.
- End of processing.When the app is uninstalled, Atlassian deletes its storage under Atlassian’s data retention policy. We keep no copies.
- Information and audits.We provide the information needed to show compliance with this addendum. Audits are carried out by reviewing documentation, including Atlassian’s reports for the Forge platform, unless a supervisory authority requires more.
- Transfers.Transfers outside the EU or EEA by Atlassian are covered by the standard contractual clauses in Atlassian’s Forge Data Processing Addendum.
Need this addendum signed for your records? Write to support@relaystudio.org.