Privacy Policy: Component Tree for Jira
Version 21 October 2026.
Effective date: to be set on publication
1. Who we are
Component Tree for Jira is provided by Zenthas, Tien Duy Vo, Alter Schulpfad 6, 65934 Frankfurt am Main, Germany, e-mail for privacy requests: privacy@zenthas.com ("we").
2. What the app does
The app is for Atlassian Jira Cloud. It lets a project administrator arrange the components of a project in a tree, adds the JQL function subcomponentsOf() to search a whole branch, and keeps a history of changes made through the app.
3. Roles
The organisation that installs the app (the "customer") decides which projects and people use it. For personal data of the customer's staff, the customer is the controller. We process data only to run the app for the customer.
4. Where data lies
The app runs entirely on Atlassian Forge. All app data is stored in the Forge storage of the customer's own Jira site, on Atlassian infrastructure. We run no server and no database of our own and do not receive a copy of the data. We have no access to the stored data of a customer.
5. Data the app processes
| Data | Purpose | Storage |
|---|---|---|
| Hierarchy of a project: for each component its parent component, by component ID | Show the tree and answer subcomponentsOf() | Forge storage of the customer, key per project |
| Change history of a project (up to 500 entries): type of change, component IDs and names, old and new values, account ID and display name of the person who made the change, time, batch ID for Undo | Traceability and Undo | Forge storage of the customer, key per project |
| Selection of the Subcomponent field on an issue (component IDs) | Show and search the chosen entries | In Jira, as the value of the field on the issue |
| Option "set parent path" per project | Configuration | Forge storage of the customer, key per project |
| Component data (name, description, lead, issue counts) | Show the tree | Read from Jira when needed, not stored by the app |
| Display names and profile picture paths of lead candidates | Show and pick a component lead | Read from Jira when needed, not stored by the app |
The app does not store e-mail addresses, issue content or IP addresses. It reads components, issue counts per component and users that can be assigned from Jira. It writes to Jira when an administrator saves a change in the tree, and when a user sets the Subcomponent field on an issue (the app then also adds or removes the matching Jira components on that issue). For tree changes: it creates, renames, describes or deletes a component, or sets the component lead. These writes run as the signed-in user, so Jira applies its own permission check and records the change under that user. After a change the app also refreshes the stored results of its JQL function inside Jira.
Jira has no audit log for components. The app history therefore only covers changes made through the app.
6. Outside connections
The app makes no calls to servers other than the customer's Jira site. In the app we use no analytics, no tracking, no advertising, no AI services and no other third parties.
7. Logs
Atlassian keeps technical function logs for Forge apps. Our code writes error messages to them and does not write names or content on purpose. Error messages from Jira calls can contain technical identifiers. The logs are on Atlassian's platform and are used by us for troubleshooting only.
8. How long data is kept
The history keeps the last 500 entries per project, older entries are dropped. The hierarchy of a deleted component is removed when the next change is saved. What Atlassian does with app data after uninstallation is described in Atlassian's Forge documentation. On request, we confirm deletion of anything we could hold.
9. Rights of individuals
People whose data is processed can ask the customer (their employer or organisation) for access, correction, erasure, restriction, objection and portability, and can complain to a supervisory authority. Because we hold no data of the customer, we forward requests to the customer or support the customer on request. Contact: privacy@zenthas.com.
10. Legal bases
For the customer's staff: the customer's own basis. For our handling of contact requests and support: performance of a contract and legitimate interest.
11. Security
We rely on Atlassian's platform for sign-in, hosting and encryption. The app checks permissions in its backend for every change (project administrator or Jira administrator), limits itself to the Jira scopes it needs and validates input. No system is free of risk.
12. International transfers
The app itself transfers no data. Transfers by Atlassian follow Atlassian's terms and the customer's Atlassian agreement.
13. Changes
We may update this policy. The current version is at https://zenthas.com/component-tree/privacy/. Material changes are announced there and in the Marketplace listing.
14. Contact
Zenthas, Tien Duy Vo, Alter Schulpfad 6, 65934 Frankfurt am Main, Germany, privacy@zenthas.com, security reports: security@zenthas.com.
15. Website
The website pages of this app load no analytics or tracking scripts and set no cookies. The app inside Jira stays free of analytics.