Agile Pulse apps: trust and security compared
How the five Agile Pulse apps differ: where each holds data, its AI provider and how to turn AI off, personal data and sub-processors.
Last updated
The five Agile Pulse apps are 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. Each app is built differently: some run only on Atlassian, others also use our own servers, and their AI features use different providers. This table compares them. Each app’s own trust page has the detail and answers common security questions.
The five apps compared
| App | Where data is held | Runs on Atlassian | AI provider | Turning AI off | Personal data | Sub-processors |
|---|---|---|---|---|---|---|
| SprintPoker for Jira | Europe: stored in London (UK), processed in Stockholm (Sweden), on Amazon Web Services. Talk to us about United States hosting. | Also uses our servers. | OpenAI, called from our servers, outside Atlassian. | A Jira admin setting (AI Settings, Enable AI), enforced by our servers. | Atlassian account ids, display names and avatars, and session comments, on our servers. | Atlassian, MongoDB Atlas, Amazon Web Services, OpenAI, laya.net |
| SprintRetro | Europe: stored in London (UK), processed in Stockholm (Sweden), on Amazon Web Services. Talk to us about United States hosting. | Also uses our servers. | OpenAI, called from our servers, outside Atlassian. | A Jira admin setting (SprintRetro Dashboard, AI settings), enforced by our servers. | Atlassian account ids, and comment authors’ display names, on our servers. | Atlassian, MongoDB Atlas, Amazon Web Services, OpenAI, KLIPY |
| Laya Export Studio | Atlassian’s cloud only, following your site’s data residency. We run no servers for it. | Badge shown on its listing. | Atlassian’s Forge LLMs, inside Atlassian. | A Jira admin setting, enforced by the app. | Some Atlassian account ids, and names in copied pages, in Atlassian’s Forge storage. | Atlassian |
| Laya WorkflowOS | Atlassian’s cloud only, following your site’s data residency. We run no servers for it. | Badge shown on its listing. | Atlassian’s Forge LLMs, inside Atlassian. | A Jira admin setting, enforced by the app for every AI feature. | Rule owners’ Atlassian account ids, and names in reports, in Atlassian’s Forge storage. | Atlassian |
| Laya Board for Jira | Settings in Atlassian. Shared and linked boards on laya.net, in the United States. Install, upgrade and uninstall signals always go to laya.net. | Also sends data to laya.net. | The app has no AI features. | Nothing to turn off: the app has no AI features. | On laya.net, when you share or link a board: the issues can include people’s names, such as assignees. | Atlassian, laya.net, KLIPY |
Runs on Atlassian is a badge Atlassian shows on a Marketplace listing when the app qualifies. "Badge shown on its listing" means the app’s listing shows it.
Architecture and data flow
Each app has an architecture diagram and data flow document: where it runs, the data that moves, where it is kept and how it is protected. Each prints as a document for your records.
Contact
- Security: support@laya.net, with "Security report" in the subject line. Please never include passwords or tokens.
- Privacy and deletion requests: privacy@laya.net.
- Support: the Agile Pulse support portal, or support@agilepulse.co.
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.