Subprocessor List — Alert Relay for Jira Service Management
Last updated: 20 October 2026
This list identifies providers appointed by Darkwood Apps to process personal data for Alert Relay. Atlassian maintains a separate list for the providers it appoints to support Forge.
| Provider | Service and role | Data and purpose | Location information |
|---|---|---|---|
| Atlassian Pty Ltd / Atlassian Forge | App runtime, Forge events, installation-scoped KVS, queues, and encrypted secret storage. | Configured app data, allow-listed alert fields, delivery state, and the customer's webhook credentials needed to host and operate the app. | Forge data residency follows the applicable setting of the customer's Atlassian site; runtime processing and onward providers follow Atlassian terms. See the official Atlassian subprocessor list. |
Customer-selected destination
Google Chat receives notification content because the customer selects and controls that destination. Google is not appointed by Darkwood Apps as a subprocessor for this service; Google processes messages under the customer's Workspace agreement and settings.
Darkwood Apps does not operate a remote application server or external log-export provider for Alert Relay event data. The public documentation website does not receive JSM alert payloads.
Changes and notices
For a new or changed subprocessor appointed by Darkwood Apps, this page will be updated at least 30 days before that provider begins processing customer personal data. Customers may request a notice through support@darkwoodapps.com.
Atlassian maintains its own onward-subprocessor list and notice process under its terms. That official list is authoritative for Atlassian providers.
See the Alert Relay Data Processing Addendum, Privacy Policy, and Support.