Skip to content
LayaHelp Centre
laya.netOpen app
GuidesIntegrationsTroubleshootingContactlaya.netOpen app

Laya Board for Jira Architecture Diagram and Data Flow

How Laya Board for Jira is connected: where it runs, the data that moves, where it is kept and how it is protected, with a diagram to file with your security review.

Last updated

Print-optimised: choose “Save as PDF” in the dialogue
On this page

What this covers: Laya Board for Jira on the Atlassian Marketplace (Laya Board), as it works in its current release: where it runs, the data that moves and where it is kept. It is made by LayaNet LTD (company number 17430595), a company registered in England and Wales. On the Atlassian Marketplace it uses the vendor name Agile Pulse.

Last reviewed: 20 October 2026.

Architecture and data flow diagram

Laya Board for Jira Architecture Diagram and Data FlowHow Laya Board for Jira is connected: people use it inside their Atlassian site, where it runs on Atlassian Forge. It also uses the LayaNet service (United States). Sub-processors outside Atlassian: KLIPY. The numbered list under the diagram says what each arrow carries.Inside yourAtlassian siteLayaNetservice(UnitedStates)People youshare a boardwithSub-processorsPeople in your JirasiteSigned in with theirAtlassian accountLaya Board for JiraAn Atlassian Forge appKeeps data in ForgestorageJiraYour issueslaya.netInstall, upgrade anduninstall signals, and theboards you share or linkAmazon Web ServicesUnited StatesGuests with a guest linkIn their own browser, outsideyour Jira siteKLIPYServes the GIF images theboard showsUnited States1234567Laya Board for Jira Architecture Diagram and Data FlowHow Laya Board for Jira is connected: people use it inside their Atlassian site, where it runs on Atlassian Forge. It also uses the LayaNet service (United States). Sub-processors outside Atlassian: KLIPY. The numbered list under the diagram says what each arrow carries.Inside your Atlassian siteLayaNet service (United States)People you share a board withSub-processorsPeople in your Jira siteSigned in with their Atlassian accountLaya Board for JiraAn Atlassian Forge appKeeps data in Forge storageJiraYour issueslaya.netInstall, upgrade and uninstallsignals, and the boards you share orlinkAmazon Web ServicesUnited StatesGuests with a guest linkIn their own browser, outside yourJira siteKLIPYServes the GIF images the board showsUnited States1234567
Used whenever the app is usedDashed: only in the cases its words giveNumber: the same number in the list below says what the arrow carriesShaded area: a boundary, named on it

In words

  1. People use Laya Board for Jira inside Jira, signed in with their Atlassian account.
  2. Laya Board for Jira reads from Jira as it works. In Jira: when the site is linked to a laya.net workspace, changes made on laya.net are written back to Jira through the app. They show in Jira’s history as the Laya Board app by default; members who link their own Jira access on laya.net can choose to have their edits shown as their own.
  3. On every install, upgrade and uninstall: the app’s Forge functions tell laya.net the Jira site’s id and address, the app version and the event. No issue or personal data. Sent over HTTPS (TLS).
  4. Only when you share a board with a guest link, or link the site to a laya.net workspace: the app’s Forge functions send that board’s issues to laya.net. For a linked site, the recent comments go with each issue. Sent over HTTPS (TLS).
  5. Only when the board celebrates finished work: the browser loads GIF images from KLIPY. None of your data: the browser loads images.
  6. Only for a site linked to a laya.net workspace: changes made on laya.net come back to the app, which writes them to Jira. They show in Jira’s history as the Laya Board app by default.
  7. Only when you share a board: guests open the guest link and see the board on laya.net, with only the fields you choose. Once the site is linked to a workspace, a guest link can take a password.

What is kept, where, and how it is protected

Laya Board for Jira: the data kept, where, and how it is protected
DataWhere it is keptHow it is protected
Forge storage: the app’s settings and its link to laya.net.Inside your Atlassian site: Forge storageAtlassian’s own security controls. Atlassian describes them in its Trust Center.
Jira itself: when the site is linked to a laya.net workspace, changes made on laya.net are written back to Jira through the app. They show in Jira’s history as the Laya Board app by default; members who link their own Jira access on laya.net can choose to have their edits shown as their own.Inside your Atlassian site: JiraAtlassian’s own security controls. Atlassian describes them in its Trust Center.
A guest link with no linked workspace: a copy of the shared board’s issues, deleted when you uninstall the app. A site linked to a laya.net workspace: copies of the connected boards’ issues, and the recent comments the app sends with each issue. Every install: the Jira site’s id and address, the app version, and when it was installed, upgraded or uninstalled. No issue or personal data.laya.net, on Amazon Web Services, United StatesAll of the app’s connections to laya.net use https. On laya.net, the Security programme applies.

Never kept: Your Jira content, until you share a board or link the site to laya.net.

Retention and deletion

  • Uninstall: The app tells laya.net, turns off its guest links, removes its link to laya.net and deletes its Forge storage. A guest link’s copy of a board, with no linked workspace, is deleted.
  • Deletion: In a linked laya.net workspace, a board’s copy stays until the board is removed or the connection is disconnected: see laya.net’s data retention and deletion.
  • Atlassian’s personal data reporting: The app uses Atlassian’s personal data reporting every week, and closed accounts are erased on laya.net.
  • Logs: laya.net’s own logging applies to data on laya.net.

Sub-processors

Sub-processors that may process Laya Board for Jira data
Sub-processorPurposeLocation
AtlassianRuns the app and its storage, and Jira.Where your Atlassian site is hosted
laya.net (run by LayaNet LTD, which also makes this app)Guest links and linked workspaces. laya.net is our own service, not another company; the companies it uses for that data are in laya.net’s sub-processors.United States
KLIPYServes the GIF images the board shows.United States

About this document

  • This document is drawn from the same records as the Laya Board for Jira trust page, and changes when they change.
  • Detailed network information is not published, to protect the service.
  • Questionnaire references: CAIQ v4 DSP-05 (data flow documentation) and DSP-19 (data location). These are references for your review, not a compliance claim.
  • Security contact: support@laya.net, with "Security report" in the subject line. Please never include passwords or tokens.
Laya Board for Jira Architecture Diagram and Data Flow: change history
DateChange
20 October 2026First published.
Still stuck?

Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.

Contact support