fabriclink

Privacy Policy

Fabric Link for Jira · Last updated: 22 August 2026

The short version

Fabric Link moves your Jira data into your own Microsoft Fabric tenant. It runs on Atlassian Forge. Haydon Group operates no servers for the app and does not receive, store, or access your Jira issue content.

What data the app processes

  • Jira work data — issues, field values, changelog history, project and field metadata, and JSM SLA/request-type/approval data, read via Atlassian APIs with read-only permissions.
  • User directory data — display names and account IDs of Jira users referenced by issues, exported so reports can attribute changes.

TODO: Legal to review final data categories before Marketplace publish.

Where data goes

Exported data is written exclusively to the Microsoft Fabric workspace you configure, using the Entra service principal you provide. Network egress is restricted to Microsoft endpoints: login.microsoftonline.com, api.fabric.microsoft.com, and onelake.dfs.fabric.microsoft.com. Data is not sent to Haydon Group.

What the app stores

Configuration and operational state — connection settings, field selections, delivery ledger, job queues — are stored in Forge storage within Atlassian's cloud, scoped to your installation. Your Entra client secret is held in Forge encrypted secret storage. Operational logs do not contain issue content or secrets.

What Haydon Group receives

Nothing automatically. If you contact support, we receive what you choose to share and use it solely to resolve your request.

Data retention and deletion

Uninstalling the app removes Forge storage per Atlassian platform policy. Data already in your Fabric workspace remains under your control — delete the mirrored database to remove it.

Contact

Questions about this policy: support@haydongroup.com

TODO: Confirm legal entity and DPO contact if required for EU customers.