Zenthas

Privacy Policy for Card Wall

Last updated: 2026-11-10.

1. Controller

Tien Duy Vo, Alter Schulpfad 6, 65934 Frankfurt am Main, Germany. Contact: privacy@zenthas.com.

2. What the app processes

When loading the cards, the app reads the following through the Jira APIs, with the permissions of the person using it: boards and sprints, and for each issue the key, summary, type, status, assignee (display name), story points, priority, due date, labels and parent issue.

3. What does not happen

The app does not store issue content on its own servers, does not send anything to external services and does not run usage analytics. Issues are processed in the Forge resolver (pass-through only) and in the person's browser. The PDF is created in the browser and only downloaded locally. The logo stays in the browser.

3a. What the app stores

  • Print marker on the issue: After a print, the app writes the property kartenwand.print (time, person, template name) to the issue itself in Jira. This requires permission to edit the issue; if you do not have it, the PDF is still created. The data stays in Jira, with the customer.
  • Templates: Saved templates (layout settings only, plus name, projects and the person's account ID, without display names, and visible to everyone for shared templates) are stored in Forge storage (Atlassian infrastructure, separated per installation). The account ID is personal data: the app reports it to Atlassian daily (Personal Data Reporting), and data of closed accounts is deleted.
  • Export history: The last 20 exports per person (time, source, count), without issue content, in Forge storage.
  • Live notice: When issues change, the app sends a signal without issue data through Forge Realtime so that open windows reload.

The app needs the permissions write:jira-work and storage:app for this. When you uninstall the app, Atlassian removes its Forge storage; the print markers on issues stay in Jira and can be deleted there.

4. Purpose and legal basis

Purpose: creating the cards requested by the customer. Legal basis: performance of a contract (Art. 6(1)(b) GDPR); where the provider processes data on behalf of the customer, on the customer's instructions.

5. Roles

The customer is responsible for the content in Jira. Where the provider processes data on behalf of the customer, we do so only on the customer's instructions and under the terms of use. Atlassian processes data as a platform under its own terms.

6. Keeping the cards

Generated PDF files and printouts contain personal data (e.g. names of assignees) and are the customer's responsibility.

7. Your rights

Access, rectification, erasure, restriction, objection, and the right to lodge a complaint with a supervisory authority. Send requests to privacy@zenthas.com.

Last updated: 2026-11-08.