Skip to content

Data Processing Agreement, Schedule A: Agile Pulse apps

How the Data Processing Agreement applies to the Agile Pulse apps sold on the Atlassian Marketplace, with each app’s details on its own trust page.

Last updated

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

This Schedule A forms part of the Data Processing Agreement (the "DPA"). It applies the DPA to the personal data that LayaNet LTD ("Laya") processes on your behalf when you use the Agile Pulse apps below. LayaNet LTD, a company registered in England and Wales (company number 17430595) with its registered office at 29 Riverside Walk, Wickford, England, SS12 0DU, sells these apps on the Atlassian Marketplace under the vendor name Agile Pulse, under the Agile Pulse apps EULA.

1. The apps

This Schedule covers these apps, each named by its title on the Atlassian Marketplace. Each app’s trust page sets out the details of its processing, and this Schedule refers to it rather than repeating it.

The apps this Schedule covers
AppAtlassian Marketplace listingsIts details
SprintPoker for JiraSprintPoker - Planning Poker & Async Estimation; SprintPoker - Free Planning Poker & Async EstimationTrust and security · Architecture and data flow
SprintRetroSprintRetro - Free Retrospective & Metrics Suite; SprintRetro Pro - Retrospective & Metrics SuiteTrust and security · Architecture and data flow
Laya Export StudioLaya Export Studio for Jira and ConfluenceTrust and security · Architecture and data flow
Laya WorkflowOSLaya WorkflowOS - AI Automation for JiraTrust and security · Architecture and data flow
Laya Board for JiraLaya Board: Custom Boards & External Share for JiraTrust and security · Architecture and data flow
Planning Poker AgilityPlanning Poker Agility - Free Estimation & Sizing for JiraTrust and security · Architecture and data flow

2. How the DPA applies to the apps

For the apps, the DPA’s references to the Laya service mean the apps, and its references to the terms of service mean the Agile Pulse apps EULA. Where this Schedule differs from the DPA, this Schedule prevails for the apps.

Each clause of the DPA, for the apps
Clause of the DPAFor the apps
1. DefinitionsApplies. "Customer content" means the data your users put into an app, and the data an app reads from your Atlassian site to do its work.
2. Roles and scopeApplies. For a site that is evaluating an app, the site’s number of active users, which identifies no person, may also go to Laya’s own sales records; the trust page of each app that sends it says so.
3. Subject matter of the processingReplaced by section 3 of this Schedule.
4. ConfidentialityApplies.
5. SecurityApplies, with section 6 of this Schedule.
6. Sub-processorsApplies, with section 4 of this Schedule.
7. Assistance to youApplies, with its first item read this way for the apps: your users can see, change and delete an app’s data as far as its features allow, and where that is not enough to meet a request, contact privacy@laya.net.
8. Personal data breachApplies.
9. Return and deletionReplaced by section 7 of this Schedule.
10. Information and auditsApplies.
11. International transfersApplies, with section 5 of this Schedule.

3. Details of the processing

Details of processing for the apps, as required by Article 28(3)
ItemDetail
Subject matterProvision of the apps listed in section 1
DurationWhile you use an app, and then as its trust page says under "Retention and deletion"
Nature and purposeRunning each app’s features for you, as its trust page and guides describe
Types of personal dataAs each app’s trust page says under "What we store"
Categories of data subjectYour users of the apps, and any individual referenced in the data an app handles
Special category dataNot requested and not required by the apps. If you place it in an app, you remain responsible for the lawfulness of doing so

4. Sub-processors

  • You give general authorisation for Laya to engage the sub-processors each app’s trust page lists under "Sub-processors", with what each receives and where.
  • Laya gives at least 30 days’ notice before a new sub-processor begins processing an app’s data, by updating that app’s list. You may object as clause 6 of the DPA sets out.
  • Where an app’s list names laya.net, laya.net is Laya’s own service, and the companies it uses are on laya.net’s sub-processor list.

5. Where data is held and processed

Clause 11 of the DPA applies to the apps, except its first sentence: where each app’s data is held and processed is on its trust page, under "Where data is held" and "Sub-processors". Where an app’s personal data leaves the UK or the EEA, the transfer mechanisms in clause 11 and in International data transfers apply.

6. Security

Laya’s technical and organisational measures for each app are those its trust page describes under "Security practices", with its answer on encryption. For data an app sends to laya.net, laya.net’s security programme applies.

7. Return and deletion

  • What happens to an app’s data when it is uninstalled, and what you can delete yourself, is on its trust page under "Retention and deletion".
  • To have the personal data an app keeps deleted, email privacy@laya.net.

8. Earlier terms

This Schedule replaces any earlier Agile Pulse data processing agreement or addendum.

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