Skip to content
Vouchline for Assets by RETEK

Privacy policy

Last updated: 30 October 2026

Who we are

Vouchline for Assets (“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 asset data from Assets and account states from Jira. It changes nothing.
  • It stores identifiers and hashes, not names of people or assets.

Roles

For the data the app processes inside your Atlassian site, your organisation is the controller. The data is stored on Atlassian's infrastructure under your agreement with Atlassian. We have no access to it. We are a controller only for data you give us directly, for example in a support request.

What the app reads

  • Assets schemas, object types, attribute definitions and the objects in the configured scope, including their owner and user fields.
  • For accounts named in those fields: the account identifier, whether it is active, and the display name (shown on screen and in downloaded files, not stored).
  • Whether the person opening the admin page is a Jira administrator.

What the app stores

DataPersonal data?
Snapshots of the scopeAccount identifiers of owners and users; object identifiers and keys; a hash of each asset name.
Campaigns, leaver settlements and the decision logAccount identifiers of owners, of the person who decided and of leavers; dates; decisions; reasons written by people.
Settings and scheduleNo.

Reasons are free text and are kept word for word, because they are part of the evidence and of the hash chain. The screens ask for a factual reason; if someone writes a name in it, that name is stored.

Names in downloaded files

The PDF, CSV and JSON files an administrator downloads contain display names of people and names of assets, read at the moment of download so that an auditor can read them. Once downloaded, these files are under your control.

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.

How long data is kept

  • Snapshots, campaigns, settlements and the decision log are kept as long as the app is installed. A closed campaign or settlement cannot be edited or deleted from inside the app.
  • 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 holds the data. A closed decision log is immutable by design; removing an entry would invalidate it.

Changes to this policy

We will publish changes on this page and update the date at the top.