Security policy
Last updated: 11 November 2026
Scope
This policy describes how RETEK ("we") keeps Epicycle ("the app") secure: who can change the app, how changes are made, how we handle reported vulnerabilities, and what we do if a security incident happens.
It is written for a company of one. RETEK is one person, who develops, releases and supports the app. Nobody else has access to the accounts listed below. This policy describes what that person actually does; it promises nothing a one-person company cannot keep.
How the app limits what can go wrong
- No infrastructure of our own. The app runs entirely on Atlassian Forge and qualifies for the "Runs on Atlassian" programme. We operate no servers, databases or cloud accounts that hold customer data.
- No data leaves Atlassian. The app makes no outbound network calls: its manifest declares no external fetch and no remotes, and it loads nothing from outside Atlassian.
- Narrow scopes, each justified:
read:jira-work(read the epic to save and the target space's configuration),write:jira-work(create the work items of a run),read:jira-user(the template managers group),write:issue:jira-software(restore the order of work items after a resumed run) andstorage:app. - Checks on the server side. Every function checks the user's role or permission on the server before it does anything; hiding a button is never the check. Saving an epic reads it with the user's own permissions. Because work items are created by the app, the app first checks, as the user, that the user may create work items in the target space; managing templates needs a Jira administrator or the template managers group; settings need a Jira administrator. People who cannot browse a space do not see the keys of runs into it.
- No silent duplicates. Every created work item carries the app's issue property; after an interruption the app searches for it before creating anything again, and stops for a person's decision when the result is unclear.
- Data stays in Forge hosted storage of your installation; it contains no account identifiers. We have no access to it in the ordinary operation of the app.
Accounts and access
The accounts that can change the app or speak for it are:
| Account | What it controls |
|---|---|
| Atlassian | the app in the Forge developer console, deployments, the Marketplace listing and partner account |
| GitHub | the private source code repository |
| OVHcloud | the retek.app domain, its DNS and email, including security@retek.app |
| the mailboxes of retek.app, where support and security reports arrive |
For each of them:
- Two-factor authentication is required. An account without it is not used to work on the app.
- Every password is unique and kept in a password manager.
- Accounts are personal and not shared. There are no other users, and no access is given to contractors.
- API tokens are created only when a tool needs one, are never written into the source code, and are revoked when no longer needed.
Quarterly access review
Once a quarter, in January, April, July and October, we review the accounts listed above: that two-factor authentication is on, who has access (the expected answer is one person), and active sessions, connected applications and API tokens, revoking any that are not recognised or no longer needed. The date of each review and anything changed are recorded in an internal access review log.
Development and release
- The source code is kept under version control in a private repository, so every change can be traced and reverted.
- Before every deployment, the automated unit and integration tests (including tests of interrupted and duplicated runs), the linter, coverage thresholds and the build must pass. A change in behaviour and the test for it are committed together.
- A new version is deployed to a separate development site and tested there, including end-to-end tests, before it is deployed to production.
- Before every release, npm audit is run on the app's dependencies. Known vulnerabilities are fixed, or assessed and recorded as not exploitable in the app, before the release goes out.
- No secrets in code: the repository contains no passwords, API tokens or keys. The app itself needs none, because it calls no external service.
- Any change to the app's scopes is a deliberate decision. It is visible to you: Atlassian asks a site administrator to approve new scopes before an installation is upgraded.
Reporting a vulnerability
Report security vulnerabilities to security@retek.app. Please include the steps to reproduce the issue and, if you can, the affected version. Do not include personal data or exported templates from your site.
- We acknowledge a report within two business days.
- We assess its severity with CVSS and fix it within the timeframes of the Atlassian Marketplace security bug fix policy (https://developer.atlassian.com/platform/marketplace/security-bugfix-policy/) for cloud apps.
- Vulnerabilities reported to us by Atlassian, including through the Marketplace bug bounty program, are handled the same way.
- We tell the reporter when the issue is fixed. Where customers need to act or should know about a vulnerability, we notify them using Atlassian's vulnerability notification template.
Security incident response
We follow the Atlassian Marketplace app security incident management guidelines (https://developer.atlassian.com/platform/marketplace/app-security-incident-management-guidelines/). A security incident is any actual or suspected unauthorised access to, disclosure, modification or destruction of customer data, or a security compromise of the app or of the accounts that control it.
- Investigate: what happened, the root cause, how long the issue existed, whether customer data could have been affected, and which customers.
- Notify Atlassian promptly and no later than 24 hours after becoming aware of the incident, by raising a P1 security incident ticket with Atlassian's developer support, with updates at least every 6 hours while it is being remediated.
- Contain: revoke compromised credentials and tokens, deploy a fix or roll back, and, together with Atlassian, temporarily hide the app from the Marketplace if needed.
- Fix the cause with technical and organisational measures.
- Notify affected customers without undue delay, where possible within 72 hours of identifying the incident, using Atlassian's security incident communication template. Your organisation is the controller of the data the app holds in your site; we give you the information you need to meet your own notification obligations.
- Review: write down what happened and what changes, and submit the findings to Atlassian through the incident ticket.
Review of this policy
We review this policy once a year, in October, and also after a security incident or a significant change to the app. Changes are published on this page and the date above is updated.