Skip to content
Vouchline Incident Clock by RETEK

Privacy policy

Last updated: 8 November 2026

Who we are

Vouchline Incident Clock ("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 incident issues in the projects you choose and records the decisions your team makes about them. It changes no issue.
  • Escalation e-mails are sent by Jira's own notification service. They contain only the issue key, the stage, the deadline and a link to the issue.

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/vouchline-incident-clock/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

  • Incident issues in the configured projects and issue types: identifier, key, project, issue type, creation time and resolution time. It does not read descriptions, comments or attachments.
  • Jira Service Management projects, their issue types and Jira groups, for the settings page.
  • For the person using the app: their account identifier, the groups they belong to, whether they are a Jira administrator and whether they may see a given issue.
  • Display names of the people named in an incident, read from Jira at the moment an evidence package is downloaded (see below).

What the app stores

All of it in Forge hosted storage belonging to your installation:

DataPersonal data
Settings: scope, roles, criteria services, escalation settingsAccount identifiers of the process owner, the deputy, escalation recipients and data protection officers; group identifiers and names.
Entity cardNames, phone numbers and e-mail addresses of the person reporting, the contact person and deputies, as entered by your administrator.
Incident record (hash chain)Account identifiers of the people who acted; times; detection time and source; assessments with answers to the criteria; the data protection officer's assessment; free-text justifications and notes.
Notifications marked as sentThe text as sent to S46, frozen with its hash. It includes the entity card contact data at that moment and whatever the team wrote. The recipient, the S46 number, and for the data protection authority the authority's name and reference number.
Notification draftsText the team is preparing before sending.
Escalation logWhich escalation was sent for which issue and stage, when, and to which account identifiers and groups.

Justifications and notes are free text and are kept word for word, because they are part of the evidence and of the hash chain. The app asks people to describe others by role, not by name; if someone writes a name, that name is stored.

Names on screen and in downloaded files

Screens show people through Jira's own user component, which reads the name at that moment; the app does not store names. The PDF and JSON evidence package and the notification PDF contain display names, read from Jira when they are downloaded, and the contact data in the notifications as sent. Once downloaded, these files are under your control and outside the app.

Escalation e-mails

When escalations are turned on, the app asks Jira to send an issue notification to the configured people and groups. The e-mail contains the issue key, the stage, the deadline and how to take over, and Jira adds a link to the issue. It contains no incident description and no contact data. Delivery is handled by Atlassian and your e-mail systems.

Logs

Application logs contain technical identifiers, counters and error messages. 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

  • Settings, incident records, notifications, drafts and the escalation log are kept as long as the app is installed. A recorded decision cannot be edited or deleted from inside the app; a correction is recorded as a new entry.
  • Closed Atlassian accounts: once a week the app reports the account identifiers it stores to Atlassian's personal data reporting API. For an account Atlassian reports as closed, the app removes the identifier from its settings (escalation recipients, data protection officers), drafts and the test notification, and stops reporting it. Identifiers already recorded in incident records stay, because the record of who decided what in an incident is evidence your organisation may need to keep under the national cybersecurity legislation and to establish or defend legal claims (Article 17(3)(b) and (e) GDPR); the evidence package shows them as "Closed account".
  • 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 or from the contact persons about their data should go to your organisation, which is the controller. We will help your organisation answer them as described in the Data Processing Addendum. Removing a single entry from an incident record would invalidate the hash chain; removing all of the app's data means uninstalling the app after downloading the evidence you are required to keep. 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.