Volver a la app · DepMesh for Jira DepMesh for Jira · Privacidad

Privacy Policy — DepMesh for Jira

Última actualización: 2026-07-03

Este documento solo está disponible en su idioma original.

Data controller: Pinflinos

Contact: support@pinflinos.com

Last updated: 3 July 2026

The technical facts below are verified against the app's source code.

Privacy policy

What data DepMesh processes. DepMesh reads Jira issues, their "Blocks" links and their Sprint field, always on behalf of the user operating the app and respecting their Jira permissions. This data is never copied or stored: it is derived on every load.

What data DepMesh stores. Only the app's own metadata, inside Atlassian Forge storage (Atlassian boundary):

  • Per dependency: commitment state, notes, last-edit timestamp and the Atlassian accountId of the editor.
  • Per user: their board project selection (view preference).

The accountId is an Atlassian account identifier and may be considered personal data. DepMesh stores no names, emails or issue content.

What DepMesh does NOT do. It sends no data outside Atlassian's infrastructure (zero egress: no external APIs, no third-party analytics, no own cookies). It does not sell or share data. It does not store issue content.

Retention and deletion. A dependency's metadata is automatically removed once its link is deleted in Jira (cleanup on the next load, verified against Jira). On app uninstall, the associated Forge storage is subject to the Atlassian platform deletion policy. For access or deletion requests, contact support@pinflinos.com.