Privacy policy
Last updated: 11 November 2026
Who we are
Epicycle ("the app") is published by RETEK ("we").
Legal entity: RETEK Kamil Gromadzki, Administracyjna 2B, 11-710 Piecki, Poland, VAT ID PL7422153037.
Contact for privacy matters: privacy@retek.app. General support: support@retek.app.
The short version
- The app runs entirely on Atlassian Forge, inside your Atlassian site.
- We have no servers and receive none of your data. The app makes no network connection to us or to any third party.
- It reads the epic you save as a template and stores a copy of its work items as the template. It creates new work items when a person runs a template.
- It stores no Atlassian account identifiers.
Roles
For the personal data the app processes inside your Atlassian site, your organisation is the controller and RETEK is the processor, under the Data Processing Addendum (https://retek.app/epicycle/dpa/). Atlassian hosts and processes the data as our sub-processor under its Forge terms and data processing addendum. In the ordinary operation of the app we have no access to this data.
We are a controller only for data you give us directly, for example in a support request.
What the app reads
All reads are made with the permissions of the person using the app, except where noted.
- When a person saves an epic as a template: the epic, its child work items and their subtasks: summary, description, work type, priority, labels, due date and the epic's start date. The app does not read comments, attachments, assignees or worklogs.
- Before a run: the target space, its work types and the fields its create screen requires, and whether the person may create work items there.
- During a run (as the app): the work items of that run, found by the app's own issue property, so an interrupted run never creates them twice.
- For the person using the app: whether they are a Jira administrator, the groups they belong to (to check the template managers group) and whether they may browse the space of a run.
- On the settings page: Jira groups matching the search, for choosing the template managers group.
What the app stores
All of it in Forge hosted storage belonging to your installation:
| Data | Personal data |
|---|---|
| Templates: name, version, and for each work item its summary, description, work type, priority, labels and due-date offset; variables; holiday calendar; times of creation and change | No account identifiers. The text comes from your work items, so it may contain names your users wrote. Attachments and images are removed. Mentions of people (@) are replaced by the neutral text "@user"; the person's name and account identifier are not saved. |
| Runs (the last 50, plus runs waiting for a person's decision): template, version, target space, the keys of the work items created, the reason for each item that failed, notes, and the planned fields of each work item including the values typed for variables and required fields | No account identifiers. Values typed when the template was run are stored as typed. |
| Settings: the template managers group (identifier and name), the time zone and the default holiday calendar | No |
The person who starts a run becomes the reporter of the work items it creates. Their account identifier is passed to the app's background job for that purpose and is not stored by the app.
Work items the app creates
Runs create work items in the space a person chooses, as the app, with that person as the reporter where the space allows it. Each work item carries an issue property epicycle.origin with the run and template item identifiers, which contain no personal data. The app does not change, move or delete existing work items.
Exported files
Template managers can download a template as a JSON file. It contains the template as described above. Once downloaded, the file is under your control and outside the app.
Logs
Application logs contain technical identifiers (such as run identifiers), HTTP status codes, field names and counters. They contain no account identifiers and no texts of your work items. They are stored by Atlassian as part of the Forge platform.
Where the data is
In Atlassian's Forge hosted storage, following the data residency location of your Atlassian site.
Data we do not collect
No analytics, no telemetry, no error-reporting service, no cookies of our own, no advertising identifiers. The app loads no resources from outside Atlassian.
This applies to the app. The retek.app website, where this policy is published, sets analytics cookies only with the visitor's consent; see the website privacy and cookie policy (https://retek.app/privacy/).
How long data is kept
- Templates and settings are kept as long as the app is installed, until a template manager deletes them.
- Runs are kept until they fall out of the last 50; a run waiting for a person's decision is kept, and an unfinished run with no progress for 30 days is removed.
- Work items created by the app are ordinary Jira work items and follow your site's retention.
- On uninstall, Atlassian keeps the app's Forge storage for 28 days, during which neither the app nor RETEK can access it, and then deletes it according to its Forge data lifecycle.
Requests from individuals
Requests from your users about their data should go to your organisation, which is the controller. Template managers can edit or delete a template, which removes its text from the app; we will help your organisation answer requests as described in the Data Processing Addendum.
For the data we hold as a controller (support correspondence) you can ask us for access, correction, erasure or restriction, and you can object to the processing. Write to privacy@retek.app. You also have the right to lodge a complaint with a supervisory authority; ours is the President of the Personal Data Protection Office (UODO) in Poland.
Changes to this policy
We will publish changes on this page and update the date at the top.